Non-relative rom-path bug.

hceline · 20 January 2019, 13:00

There is an error with parsing of non relative paths. Stepst to reproduse:
-Turn off relative paths in config and set "System ROMs" to: C:\Users\Public\Documents\Amiga Files\WinUAE\Kickstarts\
-Select a rom that is not detected by rom-scanner(example filename ks31edited.rom).
-Save config and quit WinUAE
-Start WinUAE and load the config from previous step

result:
The path to ROM reads: C:\Users\Public\Documents\Amiga Files\WinUAE\$(FILE_PATH)\ks31edited.rom

expected result:
Path to ROM should read: C:\Users\Public\Documents\Amiga Files\WinUAE\Kickstarts\ks31edited.rom

hceline · 20 January 2019, 22:20

Well, the problem apparently goes away if I name the directory something other than Kickstarts, so no big deal.

Toni Wilen · 21 January 2019, 17:29

There is some really old (most likely added before I even knew what UAE is) FILE_PATH path logic which I am not sure what it is supposed to do. I guess it was some feature only meant for unix ports. Or something.

Perhaps it should be removed.

hceline · 21 January 2019, 19:45

Additional info: It actually occurs when the path to rom file is identical to the path set in option win32.rom_path=

20 January 2019, 13:00	#1
hceline Registered User Join Date: Nov 2009 Location: Top of the world Posts: 161	Non-relative rom-path bug. There is an error with parsing of non relative paths. Stepst to reproduse: -Turn off relative paths in config and set "System ROMs" to: C:\Users\Public\Documents\Amiga Files\WinUAE\Kickstarts\ -Select a rom that is not detected by rom-scanner(example filename ks31edited.rom). -Save config and quit WinUAE -Start WinUAE and load the config from previous step result: The path to ROM reads: C:\Users\Public\Documents\Amiga Files\WinUAE\$(FILE_PATH)\ks31edited.rom expected result: Path to ROM should read: C:\Users\Public\Documents\Amiga Files\WinUAE\Kickstarts\ks31edited.rom Last edited by hceline; 20 January 2019 at 13:01. Reason: Spelling

21 January 2019, 19:45	#4
hceline Registered User Join Date: Nov 2009 Location: Top of the world Posts: 161	Additional info: It actually occurs when the path to rom file is identical to the path set in option win32.rom_path= Last edited by hceline; 21 January 2019 at 19:46. Reason: Spelling, I cant type

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
BPPC Rom path+filename	cloverskull	support.FS-UAE	0	03 October 2018 22:16
Picasso iV ROM file path	PeterK	support.WinUAE	11	01 April 2018 02:00
Relative path in portable mode:	bladecgn	request.UAE Wishlist	2	01 October 2017 18:54
Bug in x64 file requester and bug in Blizzard PPC ROM filesize	headkase	support.WinUAE	5	26 June 2016 14:17
Trying to have portable configuration, relative paths relative to C:\Public\... ?	Turrican	support.WinUAE	3	24 June 2011 16:33

20 January 2019, 22:20	#2
hceline Registered User Join Date: Nov 2009 Location: Top of the world Posts: 161	Well, the problem apparently goes away if I name the directory something other than Kickstarts, so no big deal.

21 January 2019, 17:29	#3
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,518	There is some really old (most likely added before I even knew what UAE is) FILE_PATH path logic which I am not sure what it is supposed to do. I guess it was some feature only meant for unix ports. Or something. Perhaps it should be removed.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)