Wrong system emulated!

Wulmund

@Efriim ah no ok I will check them. I just presumed they were ok as work from amiberry but will run the program and check the values

Efriim

@Wulmund It is a really useful program for a lot of this rom stuff uses crc to check for the correct rom copies.
Also if you ever use http://romhacking.net/, patching roms with translations, or fixes. It is helpful to know that you have the right file or else the patch will break.

to use the program, it integrates with properties tab of windows. Right-click on a file and open properties and click on file hashes tab.

Wulmund

@Efriim Sorry I can’t find what the hash value should be for the roms?
I have done a fresh basic install with just one game - again can run from amiberry gui, but from the games list currently showing a 3.1 floppy boot screen

Efriim

@Wulmund
The hash for the working kickstart roms:

Kickstart v3.1 rev 40.60 (1993)(Commodore)(CD32).rom
CRC32=1E62D4A5

CD32 Extended-ROM rev 40.60 (1993)(Commodore)(CD32).rom
CRC32=87746BE2

The reason it is showing a 3.1 floppy boot screen is because it is loading a different kickstart as default. The default configuration will need to be changed in the gui or somehow saved so that it will be loaded with the adf/cue. Possibly the only way would be to create the correct .conf for the game in the \roms\amiga directory.

Wulmund

@Efriim ok, my confusion is that I have only loaded cd32 roms into the system. And not for any other Amigas. And default conf and cd32 conf point to the roms I loaded, hence it loads from the actual amiberry gui.

Efriim

@Wulmund
I can't answer, I no longer have amiga installed and didn't work it out enough to understand what configuration it loads when a .cue file or .adf or .lha is selected from emulationstation.

Though are you able to load the game with the correct KS through the Amiberry GUI?

Wulmund

@Efriim Yes, I started again so the pi literally contains only amiberry, 1 CD32 game and the 2 cd32 roms.
Somehow from somewhere, it loads a 3.1 floppy screen (I reckon a500 but not familiar with other Amigas). But only from the games list in retropie, runs ok from the aniberry gui.

Efriim

@Wulmund
You can count me as an Amiga noob. There must be another way.

What you can do, is move the cd32 disc to another directory like \roms\amiga2\ then set it up in the GUI so that it will boot the disc, save this config. Then copy this config from the /opt/retropie/emulators/amiberry/ folder (the configs folder might be linked to this if you check \configs\amiga) to the \roms\amiga\ folder and the .conf can be loaded this way. Then you could make a duplicate of this config and make the changes to it for a different cd32 game.

The amiberry emulator installs two KSs with it, I think one of them is A500 and the other is AROS amiga os.

.LHA or WHDload games will work with cd32. It looks like it uses a database that can be updated from the gui, for booting these archives. This might be the way to go, https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie-(Step-3)#running--testing-games

Wulmund

@Efriim I’ve bought an Amiga retropie image that includes CD32. I will see if I can work out from it where I was going wrong

Wulmund

@Efriim other than they use .lha files and not .iso (which apparently will work anyway) it’s totally unclear!

Wulmund

@Efriim It turns out that I hadn’t got the files in the right directories. It’s now working, except the NVRAM saves which don’t work

Efriim

@Wulmund
That is probably because the default directory that it wants to save to has no write permissions.

I don't remember what the default folder was, but you could try giving it permissions
chmod +w /opt/retropie/emulators/amiberry/nvram
note that is probably the wrong folder

or you could change the directory string in the roms, config file.
flash_file=/home/pi/RetroPie/roms/amiga/tc-po.nvr

Wulmund

@Efriim you are right, I had to do a chown for the pi user on the nvram file itself which was I think in /opt/retropie/configs/amiga/amiberry. It now saves there.