4.10.1 ROM bug?

[Yoji]

Hi,

May be someone else can confirm... may be "pilot error".
But just updated my 3.2.1 Amiga install to 3.2.2 and I cant for the life of me get WinUAE to recognise the new ROM.
I put the new 47.111 rom in the path location, but it would not show up for selection..
I checked the path was correct and in the "path" config area... I clicked the "scan for ROM" button, but it did not become avail in the drop down box for ROMs.
I was able to manually navigate to the ROM and select it.. and it works (as in WinUAE is using it ok).. but its just that it will not show in the drop down list as expected..
im using the A4000 version of Rom in case thats significant.

Just ignore me if its just me/pilot error..
But wanted to feed back in case it is an actual issue.

Best regards.

[r.cade]

It's normal for that not to be in the list of known ROMs that WinUAE recognizes yet.

[thomas]

Originally Posted by Yoji

I cant for the life of me get WinUAE to recognise the new ROM.

Check file dates. WinUAE was made January 23rd, the ROM was built 1st of March. There is no magic which could make this work.

[Yoji]

Originally Posted by thomas

Check file dates. WinUAE was made January 23rd, the ROM was built 1st of March. There is no magic which could make this work.

Originally Posted by r.cade

It's normal for that not to be in the list of known ROMs that WinUAE recognizes yet.

AAhhhh... OK, so thats how it works.. I did wonder why the description in the drop down was different to the file name of the ROM's... but assumed it had picked up the description from interrogating the ROM file.

I assumed it would check all files in the nominated ROM directory and include them if it passed basic validity checks... I didnt realise it would only look for ROM files it specifically knows about. Oh well, learn something every day