English Amiga Board - View Single Post - LFN support, relative paths in .UAE files

16 August 2009, 13:42

How about adding LFN support to WinUAE's command line options?

Consider the following:

Code:

winuae -f a500.uae -0 adfs\sensible soccer.adf

Obviously fails. The following should work:

Code:

winuae -f a500.uae -0 "adfs\sensible soccer.adf"

But sadly, does not work at all, whereas technically, it should.

This command:

Code:

winuae -f a500.uae -0 adfs\sensib~1.adf

Works, but impractical if several similar-named files exist... you should not need to keep track of which file is represented by ~1 or ~2 etc.

Also, how about making paths contained in .UAE files relative? Some seem to be, but others do not. For example, the line containing the path to the ROM file is not relative... making configuration files useless on systems where ROM's are located someplace else, or on portable media, such as a CD-ROM, or USB drive, where drive letters may change.

16 August 2009, 13:42	#1
didomusicuk Posts: n/a	LFN support, relative paths in .UAE files How about adding LFN support to WinUAE's command line options? Consider the following: Code: winuae -f a500.uae -0 adfs\sensible soccer.adf Obviously fails. The following should work: Code: winuae -f a500.uae -0 "adfs\sensible soccer.adf" But sadly, does not work at all, whereas technically, it should. This command: Code: winuae -f a500.uae -0 adfs\sensib~1.adf Works, but impractical if several similar-named files exist... you should not need to keep track of which file is represented by ~1 or ~2 etc. Also, how about making paths contained in .UAE files relative? Some seem to be, but others do not. For example, the line containing the path to the ROM file is not relative... making configuration files useless on systems where ROM's are located someplace else, or on portable media, such as a CD-ROM, or USB drive, where drive letters may change.