Re: kickstart rom files

[amyren]

Is there a particular naming scheme for these roms if you want to have all flavours available?
And can I have 3.1, 3.1.4 and 3.
2 A1200 roms instalked at the same time.

[F0LLETT]

Is there a particular naming scheme for these roms if you want to have all flavours available?
And can I have 3.1, 3.1.4 and 3.
2 A1200 roms instalked at the same time.

Only kick 1.3 A500/CDTV/A2000 and kick 3.1 A1200 are supported at the moment.
Adding more and custom, will be ignored.

[amyren]

ok. But what rom does the A500p and A4000 setups use then?

[F0LLETT]

ok. But what rom does the A500p and A4000 setups use then?

Update, all roms are accepted now.
If you have correctly hash'ed commodore / cloanto roms, it will auto select correct one, when you select model.
i.e. A500+ will set V2.04
      A4000 will set V40.68

[notel98]

It would be good if you could choose the rom when you add an hdf. i.e I might want to have 2 a1200 but using different OS - and roms

[F0LLETT]

It would be good if you could choose the rom when you add an hdf. i.e I might want to have 2 a1200 but using different OS - and roms

Your talking about custom roms. Which are rejected due to hash checks.

In PSPUAE, I just dumped the code that checked roms, so any could be used.
Would have to check on what could be done to allow this.

[amyren]

I think he means official roms, like having both kickstart 3.1 and 3.2 ROMS in the system.
OS3.2 should work with 3.1 ROM, but will need to load the 3.2 ROM into memory. But the loss is less available RAM and longer boot time.

[notel98]

I am talking about official roms.
Let’s say I have 3.1 and 3.2 roms but wish to have 2 x a1200 setups.
I select 1200 when I upload hdf but I cannot select the specific Rom
I have found that OS would load but then I could not use “execute command” to open newshell etc so then forced to delete 3.1 rom but keep 3.2 if that makes sense.

[amyren]

I am talking about official roms.
Let’s say I have 3.1 and 3.2 roms but wish to have 2 x a1200 setups.
I select 1200 when I upload hdf but I cannot select the specific Rom
I have found that OS would load but then I could not use “execute command” to open newshell etc so then forced to delete 3.1 rom but keep 3.2 if that makes sense.

Just tested to create a OS3.2 install in WinUAE by emulating a A1200 with kickstart 3.1.
Then the loadmodules was installed automaticly. Next installing it in a A1200 setup in A600GS with the 3.1 rom worked fine.
Next I did another test by creating the hdf while having a 040 cpu. It then warns about this, and instruct to reboot and install the mmu libraries. Strangely they didnt have an installscript on the mmulibs disk, or any instructions, but I just copied everything on the disk straight into the hdd. Then using that hdf with the A4000 setup in A600GS and it booted without issues.

[F0LLETT]

Just tested to create a OS3.2 install in WinUAE by emulating a A1200 with kickstart 3.1.
Then the loadmodules was installed automaticly. Next installing it in a A1200 setup in A600GS with the 3.1 rom worked fine.
Next I did another test by creating the hdf while having a 040 cpu. It then warns about this, and instruct to reboot and install the mmu libraries. Strangely they didnt have an installscript on the mmulibs disk, or any instructions, but I just copied everything on the disk straight into the hdd. Then using that hdf with the A4000 setup in A600GS and it booted without issues.

Why use a 4000 config, when you set it up for 1200?

[amyren]

Why use a 4000 config, when you set it up for 1200?

You get 8 MB more ram when choosing the A4000 setup.
Also I was curious about how OS3.2 would work in AmiBerry with those needing to install those mmulibs.
Now that this OS3.2 setup is prepared with the mmulibs it will run on both A1200 and A4000 setup.

[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.

[SkulleateR]

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

[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.