Passing LFN to Win98 batch file?

Solution
NO. Win98 is 16Bit OS and was limited to 8.3 for file names. It couldn't understand LFN, and only way you could 'pass a file' to Win98 was to use the truncation. Somefilename.TXT would be changed to Somefi$1.TXT . This became a problem if for example you had multiple file names similar and you would get many numbered ones that you didn't know whcih one was Somefilename.txt and which was Somefilenumber.txt because all you would see is Somefi$7.txt and Somef$43.txt.
NO. Win98 is 16Bit OS and was limited to 8.3 for file names. It couldn't understand LFN, and only way you could 'pass a file' to Win98 was to use the truncation. Somefilename.TXT would be changed to Somefi$1.TXT . This became a problem if for example you had multiple file names similar and you would get many numbered ones that you didn't know whcih one was Somefilename.txt and which was Somefilenumber.txt because all you would see is Somefi$7.txt and Somef$43.txt.
 
Solution

Incorrect Tom. Windows 98 supported FAT32, which allowed long file names to be used just fine. To pass long file names in/out of batch files you should enclose the entire string in quotes [ " ]
 


http://en.wikipedia.org/wiki/8.3_filename

Yeah Mod is right I was think back in DOS / Win3 days, not 9x forward. No idea WHY you want to use a dead OS that is incapable of any hardware / drivers / etc. has been used for what 15 years now (32 bit and now 64bit) ?
 

Harry Potter

Honorable
Jun 26, 2012
105
0
10,680


I thought I did. I'm going to try that the next time I gain access to my Win98 computer. I also had problems with two Win98 programs processing LFNs in their command line. I believe I used quotes for both of them. Any idea what could cause this?