Long Filenames on Samba Shares:
When XP PCs create files with long filenames on my Samba Server (OS X 10.2.4), and they exceeed the Mac OS 9 character limit of 32 chars, it causes a problem.
When a Mac OS 9 client mounts the Samba share and sees the files, the names are truncated and a hex value is appended to the name like so:
(Example PC Word file with long name
reallyreallyreally_long_file_name.doc
(looks something like this on the OS 9 Mac
reallyreallyreally_long_file_n#FF2B.doc
Thats OK, I can deal with this until I migrate to OS X (Quark!). I can also tell my PC users to 'make shorter names'. BUT:
If I try and open a Word file which has a long filename (and a hex# appended), both Word 98 and Word 2001 freeze the entire Mac and forces me to reboot.
If I remove the hex# and rename the file, then it seems like the Word file opens in OS 9 just fine.
Have you seen this?
Can I fix it?
Thanks!
When a Mac OS 9 client mounts the Samba share and sees the files, the names are truncated and a hex value is appended to the name like so:
(Example PC Word file with long name
reallyreallyreally_long_file_name.doc
(looks something like this on the OS 9 Mac
reallyreallyreally_long_file_n#FF2B.doc
Thats OK, I can deal with this until I migrate to OS X (Quark!). I can also tell my PC users to 'make shorter names'. BUT:
If I try and open a Word file which has a long filename (and a hex# appended), both Word 98 and Word 2001 freeze the entire Mac and forces me to reboot.
If I remove the hex# and rename the file, then it seems like the Word file opens in OS 9 just fine.
Have you seen this?
Can I fix it?
Thanks!