Amiberry not remembering ROM files

[jameswhit82]

Hi,

I’ve got a a strange issue where Amiberry is not remembering my Amiga ROM files. These are ones that I took from Amiga Forever and include a Rom.key file.

Every time I reload I have to re select the appropriate ROM.

Any advice would be much appreciated!

Thanks you!

[midwan]

What do you mean by "not remembering"?
Are they not listed in the dropdown?
Are you loading a config with a specific ROM, and that doesn't work?
Please provide more details on what you're trying to do exactly, including the version of Amiberry you're testing with.

[jameswhit82]

Hi. Apologies, I should have mentioned that in my previous post. This is Amiberry v5.7.4 running on Mac OS 15.0.1.

I get nothing listed under ‘Main ROM file’ other than the AROS built in ROM.

Although I have all of the below from Amiga Forever:

It seems to run happily, it’s just annoying every time I load my configuration I have to manually re-select the correct ROM every time. It’s like it doesn’t recognise the files as proper Amiga ROMs as such.

Thank you.

[midwan]

OK, then I suspect I know what might be going on.
First of all, you really should be using the newer versions with MacOS, since it has no problem running the more demanding full CPU emulation (vs the 5.x versions, which have a trimmed down CPU emulation core, meant for slower boards).

There was a bug that I recently fixed, which is probably related to this. If you had selected a custom ROM filename, instead of one from the dropdown after a Rescan, that would be "lost" when you reloaded the config. The fix is in the upcoming new version (which will be v7.x), soon to be released.

[jameswhit82]

Thats brilliant thank you, I will have a go with the preview 6.3.4 version then and let you know what happens. That definitely does sound like the issue I am experiencing though with the ROMs.

[jameswhit82]

v6.3.4 does seem to run very smoothly but I am am getting the issue with the ROM being lost when reloading the configuration, so hopefully v7.x will resolve this for me then.

I’m guessing just renaming the ROM names to a standard format wouldn’t help at all for this issue currently?

Thank you for your help!

[midwan]

The filenames don't really matter, as it will check for the checksum values of the ROMs. If it recognizes them, it will show them with their standard names in the dropdown (you can trigger a Rescan from the GUI, by going to the Paths panel, and clicking on the relevant button there). It should show you a list of ROMs after that (more than just the AROS ones).

The bug I mentioned, is triggered when you manually select a filename to a ROM (by clicking on the button to load one up manually). That gets saved normally in the config, but it doesn't show up in the GUI when you re-load the config. That bug is fixed in v7 already, but the new release is not ready yet.

[jameswhit82]

Ok, that makes sense. Would you expect normally that the Amiga Forever ROMs wouldn’t be recognised? The ones I got were from the Amiga Forever Essentials package from Google Play, so not sure if that makes a difference at all?

No probs, that’s good news about the fix though, so will make sure I upgrade when that becomes available. Thank you.