Annoying resource forks.
When I switched to HFS+ on my external HD and copied over my audio collection using linux, it seems that resource forks for every single audio file have been created. This is very annoying when copying over directories to my mp3-player (actually, it’s a multi-codec jukebox 
) for it takes some time until the forks are skipped and the music starts playing.
FinderCleaner lets you easily remove resource forks and the like by selecting the appropriate device or folder. Dead simple. Very handy.
On the developer’s site is also an announcement for MusicSync which will enable iTunes to handle non-iPodish audio players. For I can address my iriver as a storage device and therefore load it with everything capable of copying/moving files it’s not really a must-have, but promising none the less. I mean, I’m not exactly a fanboy of iTunes but getting used to it, it’s a nice app. And if I can use it as a single point of music management, so be it. A long way to go, though..
May 17th, 2005 at 12:28
OS X’s dirty secret.
“Resource forks would be fine if everyone recognised them, but that’s the catch: no one else does. Moreover, OS X is supposed to be POSIX compliant, and you can’t have a file system that’s not in line with Unix standards. Unix does not admit of forks, so Apple cannot officially recognise them either.”
http://rixstep.com/2/20040802,00.html
May 17th, 2005 at 18:25
Thank you, interesting read. I just wonder why Apple is relying on resource forks or file extensions. Doesn’t Konqueror & Co (I’m actually not sure on which level file-type recognition takes place) determine the type of a file by it’s header/content? I don’t wonder that Microsoft still does so, for well, you know, but I don’t get it that OS X uses the same or comparable mechanisms. Strange indeed.