> I remember running into this problem a while back with a Win2K server
> running SFM. The problem was that resource forks were stored differently by
> OS9 and OS X. In OS9, the resource forks for the files in a directory were
> stored in a hidden directory called ".AppleDouble". Each resource fork was
> contained in a file with the same name as the data fork's file name.
> With OS X, the resource forks were stored in the same folder with the same
> filename as the data fork, but preceeded by "._".
> So, OS X would store a file name "blah" in a folder on the Win2K server as
> "blah" and "._blah". OS 9 would store "blah" as "blah" and
> ".AppleDouble/blah". The problem that you have occurs because OS X won't
> use OS 9-style resource forks, and vice versa.
> Any dotfiles will be invisible to the OS X Finder, although you can access
> them with Terminal. The .AppleDouble directories are invisible to the OS 9
> Finder, but the ._ files are visible. If you attempt to select one of
> these, the Finder may freak out, for lack of a better term.
> I think that NTFS manages the OS 9-style forks, but that OS X is detecting
> a non-HFS+ filesystem and managing its own forks, leading to "issues".
> I'm not sure why the file disappears - I suspect it's an issue with SFM
> trying to associate the resource fork when OS X requests a file, and OS X
> trying to use the resource fork file it stored. That's sheer conjecture
> with potentially no basis in reality, however.