lr-puae: Kickstarts are not being copied to the WHDLoad helper disk image

DavidGA

According to https://retropie.org.uk/docs/Amiga/#whdload-disc-images - when launching a WHDLoad LHA image in lr-puae, kickstarts should automatically copied into the disk image. (Presumably, into devs:kickstarts)

This doesn't seem to be happening. Some WHDLoad images don't need a copy of the kickstart, and they work fine, but the ones that do don't currently work, throwing an error about the missing kickstart.

As an example, trying to launch "Off Shore Warrior" - my image is called "OffShoreWarrior_v1.0.lha", complains about not being able to find "devs:kickstarts/kick34005.a500".

My copy of that file matches the required checksum in the documentation, so I'm sure it's the right version:

$ md5 RetroPie/BIOS/kick34005.A500
MD5 (RetroPie/BIOS/kick34005.A500) = 82a21c1890cae844b3df741f2762d48d

I'm running RetroPie 4.7.9 manually installed on the aarch64 version of Raspberry Pi OS Lite on a Pi 4, and lr-puae 2.6.1 built from source.

DavidGA

I'm linking the verbose runcommand log, though it does not seem to contain anything useful.

https://pastebin.com/40sJPEQa

DavidGA

Well I solved my own problem.

The helper disk image is created in roms/amiga/WHDLoad, but it is only created once and not updated again. Because the first time I attempted to launch an LHA I did not have the kickstarts in the BIOS folder, it did not copy them and then never tried again.

To fix it, I just had to delete the aforementioned WHDLoad directory to force it to make it again.

(This is similar to a problem with the Atari 800/5200 emulator, if you run it once without the correct BIOS roms, you have to delete the config file after acquiring the correct roms to make it work.)

I don't think this is documented anywhere, perhaps it should be.

mitu

Thanks for troubleshooting this

I don't think this is documented anywhere, perhaps it should be.

I think that's what's implied by

To update WHDLoad: simply delete the directory or the HDF file

but I agree is not that intuitive and most of the time users will start the emulator without the BIOS files, so the document may need some details.