Unix Executable File

To Everyone,
It seems that no one has actually asked the question why these Unix Executable Files occur. I understand that it is a 'resource fork' / NTFS issue, but why is it that it happens from time to time? Is it happening to random files on the server or is there a method to the madness? I would like to know for my own sake as I do see this happen in my network. PS, Ido know of the 'work-around' of adding extensions.
 
I received a firewire HD from our prepress house that contains 93GB worth of files. All these files were created using OS 9 and OS X. All files were transferred from a MAC server to this HD and it is formatted and journaled as an OS 10 HFS. All Photoshop files are reading as Unix Executable FIles. I know the workaround for renaming the extensions, etc. but am in need of anyone who knows any other solutions. There are too many files to rename each one of them and the changes.
Any help will be appreciated!
EJ
 
You must log in or register to reply here.
Back
Top