Discussion Locked

Problem with long filenames and paths

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I suppose I have a problem with long paths which includes intervals in names. In some cases programs which r trying to save files in that kind of directories provide unexpected errors with error codes -1 or -3.
In other cases Im trying to start installation program from where they r and recieve message that the file couldnt be found. If I move same program to the root everything seems to be ok.
How can I solve this problem.
Ty in advance

13 replies

by hutch

Ok ... first of all ..what OS are you using. What is the scenario in detail...
I would imagine that if your program is trying to save files in certain name format that your OS does not support you will end up with 'filenames' being saved as 'filesna~1'. I would reccomend you change the disk to NTFS and hopefully this would rectify your long filename support issues.

Without more info it's difficult to pinpoint exactly where you problem may be..
Miles

by Member 30356696

Without more details it's hard to say.
Remember the 8.3 format of DOS and that filenames containg various non-alpha numeric characters must be enclosed in quotation marks !
This can be a problem with the 'Progam Files' directory in NT !
Also, if a file can be called from Root but not a particular sub-directory you should check your path statement !

by alex_fischuk

For Win95 it is common,,, If you using batch file or file associations try to put command arguments in quotes
For example:
"c:\Program Files\Microsoft Office\Office\Excel.exe" "%1"

by gicu artistu'

If your server is NT then even though you have FAT partitions it's still supports long file name properly if your partition is not bigger the 2GB. If it's bigger then some clients will have problems accessing it (it's all about numbers like the biggest integer...). If you need partitions bigger than 2Gb (probably you do..) try to transform it into an NTFS partition and format it with 512b (so your DOS and good old Windows 3.1 will not have problems accessing it if you maintain the 8.3 rule fromthe directory you first share to the name of the share).
The second issue is Windows 95 which says that support long filenames. But as a free information, the longest path that Windows 95 supports is 64 bytes (characters) from the root to the leaf. Issues will arise when several Windows version clients will try to access a file on this kind of path on a FAT partition.
So as a resolution for this I got rid of FAT partions for USER Data and I tried to keep a short path to the file (with multiple share names when

by guildt

I am assuming NT. There are some third party disk utilities that directly manipulate the FAT file system and can destroy Long File Names, or even the file itself. Long file names on a fat partition create many Directory Entries. The first is for the alias and the next 1-3 are for the LFN. Some utilities will ignore the secondary entries when you "defrag" and treat them as blank spots. Therefor now your file system doesn't know what the alias is for and you would get file not found. Safe utilities are the ones provided with MS-DOS 6.x. Another problem you could have is some 16-bit applications save data to a temporary file, delete the original file, and rename the temporary file to the original file name. In some cases this deletes the long file name. Hope this is helpful.

by ustutz

Any 16 bit ("DOS") application will not resolve long filenames correctly. While it can convert "My Long Filename" to something like "mylong~1" on a read, when it tries to write back to that location, it tries to write literally to "mylong~1". Also, be advised of false advertising: Not all apps claiming to be "32 bit", "Windows 95", or "Windows NT", in fact are.

The solution: Those apps that you have problems with need to reside in "DOS" file systems (i.e., follow the 8.3 convention, regardless of underlying NTFS/FAT file system).

This discussion is closed to new replies.