This is a Micros~1 problem... although it did originate in Unix, the
14-character filename limit.
I'll discuss it from a linux perspective, and then you'll have to
convert it to solstice...
The standard dos directory structure can only handle 8.3 filenames. With
9x, Microsoft added a "compatible extension" whereby the long name is
stored in specially marked directory entry blocks. So any MS long name
has an 8.3 equivalent visible to old programs.
In linux, if you mount a dos filesystem as FAT, then it can only see the
standard directory entries and will only use the 8.3 name. And if it
moves the file, the long name will be lost. If you mount the filesystem
as VFAT, linux uses a different driver which is aware of the extension.
Note with CDs the same problem applies - ISO-9660 only knows about 8.3,
but Joliet and/or RockRidge define long-name extensions.
So I am guessing you are mounting a dos filesystem on solstice using a
driver that is only aware of 8.3 names.
Posted At: 08 November 2000 18:13
Posted To: admin
Conversation: long file names - solstice 3.1
Subject: long file names - solstice 3.1
When transferring files between a PC and a E450 running
2.6 the filenames come across as filename~1.dat. And the
user loses authority to edit the file. Can someone tell
me why this translation occurs and what the fix is. I've
seen nothing either on Sunsolve or here in this newsgroup
regarding this problem, although there was a rather long and
informative discussion as to why this happens when the
files are transferred via CD.
Any information will be greatly appreciated.
Sent via Deja.com http://www.deja.com/
Before you buy.