wrong custom columns with cm_switchLongNames

[gwwurth]

High,
suppose you have two files with following Names:
LongName File_Test.TXT with DOS-Name FILE_T~1.TXT and
LongName File_T~1.TXT with DOS-Name FILE_T~2.TXT

(This can easyly been created manually. But it happend to me by accident as well).

Now configure a custom colums view
starting with default:
Name Ext,
continuing with: dosname fullname.
and now use it and switch cm_switchLongNames.
you will see columns starting with:
file_t~1.txt and then
file_t~2.txt
but you will not be able to open the first file but get the second.one.
And in the column with DOS-Name and fullname is garbage, is it?
hopefully, Gerhard

[petermad]

I can not reproduce this - simply because I have not yet been able to create a file with the LongName: File_T~1.TXT and the DOS-Name: FILE_T~2.TXT

[roentgen]

I can not reproduce this - simply because I have not yet been able to create a file with the LongName: File_T~1.TXT and the DOS-Name: FILE_T~2.TXT

try this in command prompt

Code: Select all

fsutil file setshortname "File_T~1.TXT" "File_T~2.TXT"

assuming there is no other file with the given shortname

[petermad]

fsutil file setshortname "File_T~1.TXT" "File_T~2.TXT"

OK - that works (on a NTFS partition), but then comes my next problem: if I try to run:

Code: Select all

fsutil file setshortname "File_Test.TXT" "File_T~1.TXT"

to make the other file in the same directory, then I get a message that says:

A file that already exists can not be created

(translated from Danish)

[roentgen]

Error: Cannot create a file when that file already exists.

Same here... altough there's no file with the shortname File_T~1.TXT Windows cannot create it as there already is a file with that longname . Maybe that's the obvious result of mixing NT with DOS features

[Jungle]

...
and now use it and switch cm_switchLongNames.
you will see columns starting with:
file_t~1.txt and then
file_t~2.txt
but you will not be able to open the first file but get the second.one.
And in the column with DOS-Name and fullname is garbage, is it?
hopefully, Gerhard

Not confirmed on Win2003 Standard Edition, TC 6.53. Files are accessed correctly, no garbage in columns

[gwwurth]

I confirmed: takes place only on Novell-drives.
on local drives it seems not to happen.
Yet it is happening:
copy file with longname file_Test.TXT to local drive results in
file_T~1.TXT als DOS-name
then copy file with longname "file_T~1.TXT" to local drive will rename the DOS-name of the previous File to *~2.TXT and occupies the *~1.TXT then.

On Novell-drives you do not need any utility to force DOS-names.
Just copy first file as above to Novell-drive and so on.
The second file get's DOS-name *~2.TXT not *~1.TXT after manipulating DOS-name of previously copied file.