UNIX Executable File not opening

[himeshRES]

From time to time when I receive files from customers or clients, my Mac calls them a kind of file called a Unix Executable File. While I find at the type of file in Finder or in Get Info, it says it is a Unix Executable file. Most of the time I know accurately what type of file it is, a font file or psd or avi, even a jpeg so I can go to the program and select File - Open. From time-to-time I am uncertain what format the file is, so I can not essentially go to the program and do a File - Open. I noise incompetent while I go back to a customer and inquired them what format the file is in. I included a picture of my latest problem. I received a Quark file from a customer and the Quark file as well as the packaged fonts and a number of photos are coming back as Unix Executable Files. I really don’t know what to do. So please help.

[Devasis]

What is occurrence is that Mac OS X cannot read the file's resource fork, and so does not know what the file is. This does not take place with files with extensions the majority of the time, because even if a Word document misplaced its resource fork information, it could still make use of the “.doc” extension to connect the file with Word. One of two things occurred:

1. The files invented from a Windows machine and no extension was put on the file. Windows machines know not anything of reading or writing Mac-compatible resource forks.
2. The files created on a Mac, but were either moved with a protocol or compressed with a program which ignores or strips files of that resource for information.

[Solomon]

Yes Devasis you are completely right. There is not much you can do to get around the trouble with no teaching the customers or clients novel tricks. They should use a compression that is “.zip” that conserve resource fork information, or store the files on a file system which keeps this information. Just tell me how did these files specially come to you? How were they moved? They had been compressed? If you can explain in detail the route they took from hard drive to hard drive, CD to CD, network to network, we may be able to identify where, accurately, the resource fork information was misplaced and come across a workaround.

[MrChris-]

I also have the same issue. And as you say these exacting files came to me through email, in a zipped folder and I downloaded them to my desktop, then extracted them. They typically come from the sender, to my associate’s inbox, or my web browser mail. There is not precisely a lot of point concerned that I can provide you. And they are not forever zipped files. If it is a .jpeg, and I know it is a .jpeg, but it does not have a file extension built-in, I can insert the .jpeg extension and it will open up well while double-clicked on. At least I have an idea of what’s occurrence, this time is a little more exasperating than most since they are font files and I can't install them to view the customers file correctly.