[cygsid]

why is it that Jaguar won't let me copy files with characters like ',;&[]' to a Windows share, even though I can create files/folders with those supposedly forbidden characters perfectly fine on my (Windows 2000) PC? (error -43)
Is it that some older version of Windows did not support those characters and so OS X only accepts the least common denominator?
This is very annoying when copying mp3 files over (for backup purposes).
I am also getting error -120. Any idea about that one? Thanks.

[Emotionally Fragile Luke]

Does Windows allow those messed up characters if you try to open them?

[Millennium]

Originally posted by cygsid:
why is it that Jaguar won't let me copy files with characters like ',;&[]' to a Windows share, even though I can create files/folders with those supposedly forbidden characters perfectly fine on my (Windows 2000) PC? (error -43)
Is it that some older version of Windows did not support those characters and so OS X only accepts the least common denominator?
This is very annoying when copying mp3 files over (for backup purposes).
I am also getting error -120. Any idea about that one? Thanks.

Are you using NTFS on your Windows 2000 box?

Those characters, along with a few others, are forbidden on FAT and FAT32. Samba (which provides OSX's Windows filesharing capability) has no way of knowing this, however, and so it goes with the least common denominator. You should be able to see the same effect if you connect to that machine using another Windows box.