|Usually I can guess what kind of file it is by the file |
name and adding the extension to the Unix file once it
is on the Mac will open it - but what do I do about
fonts or files I cannot guess? We have a huge Quark
catalog that was collected and stored on the network
and now all those fonts have turned into Unix
Ok, does the files being made executable stop your software from opening them?
If the only problem is that they're all being made executable, it's easy enough to change that. Open a terminal window on your Mac, navigate (in the terminal window) to the folder the files are stored in and remove the "x" from them as follows:
chmod -x *
The issue is likely a result of confusion between the Unix based OS X and windows. Windows depends on the file extensions to decide on what type of file a file is. If it's a .exe then it's executable. If it's .doc it's a document. If it's .txt it's an ASCII text file.
Could it be the file extensions causing your issue? I'm not very familiar with OS X and Mac's. But I do know UNIX and Linux as well as Windows. What file extensions are being put on the files created?
All I know for sure is, most of our servers are Linux or UNIX based and I save files on them all day long from Windows based PC's using XP and I've yet to have a similar problem. In fact, I frequently move files between Windows, UNIX and Linux....the same file....and perm's don't change.
The only thing I see different from my situation and yours is the Mac OS. So perhaps it's the Mac's themselves, or the software you're running on them to work on the files.