Re: kickstart rom files

[ernsteiswuerfel]

I must say this works like a charm now! 

I added and tried:
A500.34.5.rom (OS 1.3, autoselected by 'Model A500')
A500.37.175.rom (OS 2.0.5, autoselected by 'Model A500P')
A1200.40.68.rom (OS 3.1, autoselected by 'Model A1200')
A1200.46.143.rom (OS 3.1.4, autoselected by 'Model A1200')
A1200.47.111.rom (OS 3.2.2, autoselected by 'Model A1200')
CD32.40.060.rom (OS 3.1, autoselected by 'Model CD32')
CD32.40.060_ext.rom (OS 3.1, autoselected by 'Model CD32')

This satisfies all my ROM needs and for the A1200 either of 40.68, 46.143 and 47.111 worked.

[ernsteiswuerfel]

A bit of nitpicking - but would i be possible to briefly display the ROM-file used when the system starts one of the installed Applications or Games?

Probably this would help some users to realize faster why a game or an app may not work. E.g. I installed Abbey(s) of the dead as adf and when I started it, it didn't work, dropping me in the AROS shell. If you realize it's an AROS shell this gives you a hint that you probably need to install an appropriate .rom file first. Another example is the CD32 or the A1200 model try to use any Commodore ROM if one is installed, even if it's not the correct one. So the A1200/CD32 fails using Kickstart 1.3 but depending on the game you may not get dropped in the shell where you would realize the mismatch but instead you just get a Guru or a red screen.

I know there is a notice about compatibility issues due to missing ROMs in the First Time Wizards' ROM management screen but hasty or unexperienced users may overlook this.

A brief message like "ROM file mismatch for selected Model A1200. Please install appropriate ROM via ROM management." would give a proper hint to new or unexperienced users to get things going more easily.

[ernsteiswuerfel]

Just load an empty adf/ISO that ist Not bootable in that cobfig and you get to the Kickstart Screen to look what ist beeing used

Trve. That would work of course. 

But I was talking about new or unexperienced users.