nglevin
Well-known member
Did you try using one of the apps suggested to re-apply creator and type codes so that you can open them in Finder?
I'll reiterate that no version of the Mac OS X Finder or its supported file systems tamper with resource forks. Leopard doesn't do anything special there that Tiger doesn't, Mojave doesn't either. That's a myth that I've tried to dispel.
If you are continuing to use FTP to transfer files instead of AppleTalk, then you will lose the resource forks because there's no standardized way of preserving that data via FTP.
EDIT: I'll add that NetPresentz could be adding the creator + type code information for WAV files as it's receiving them, like PC Exchange does when transferring files and opening them on IBM-compatible formatted media, and not doing that for AIF/AIFF.
I haven't used NetPresentz in more than 12 years now? It's decent to get file transfers going if you don't have anything else, but it's worse than AppleTalk in just about every way besides handling network transfers from your Mac to Windows where you'll lose resource forks anyway. Linux has Netatalk that can handle a good emulation of AppleTalk that's also resource fork aware as far as I can recall.
I won't knock it if you're liking your set up so far. Just, be aware that it's probably the root cause of your resource fork issues.
I'll reiterate that no version of the Mac OS X Finder or its supported file systems tamper with resource forks. Leopard doesn't do anything special there that Tiger doesn't, Mojave doesn't either. That's a myth that I've tried to dispel.
If you are continuing to use FTP to transfer files instead of AppleTalk, then you will lose the resource forks because there's no standardized way of preserving that data via FTP.
EDIT: I'll add that NetPresentz could be adding the creator + type code information for WAV files as it's receiving them, like PC Exchange does when transferring files and opening them on IBM-compatible formatted media, and not doing that for AIF/AIFF.
I haven't used NetPresentz in more than 12 years now? It's decent to get file transfers going if you don't have anything else, but it's worse than AppleTalk in just about every way besides handling network transfers from your Mac to Windows where you'll lose resource forks anyway. Linux has Netatalk that can handle a good emulation of AppleTalk that's also resource fork aware as far as I can recall.
I won't knock it if you're liking your set up so far. Just, be aware that it's probably the root cause of your resource fork issues.
Last edited by a moderator:
