--- One reason is that AFP and SMB are not the same. Try this
interesting experiment. On an OSX client, mount the same Windows/SFM
based share twice. Once with AFP and once with SMB. Compare all the
file and folder names and you'll see many are different. Lots of
truncated names on the SMB share because of character set differences.
Then look at the icons and associated application that will run when
double-clicked. A great many are incorrect on the SMB share.
Well yes, that's due to the crappiness of SFM and the way the OS deals
with forks when transferring files. There is a big difference between
"using SMB" and "using SMB and AFP". It is very important that you only
use one connection type or the other.
FWIW, it's easier to fix files going from SMB to AFP because you can
simply recombine the data (foo) and metadata (._foo) forks. AFP to SMB
is hard because SFM has stashed the fork away in a NTFS stream.
Josh
--
Josh Wisenbaker, ACSA
http://www.afp548.com
Breaking my server to save yours.
