Cloanto Amiga Forever 7 roms not working in PUAE #686
Comments
|
I have never tested that key thing, but only made the filenames acceptable, and it is working fine here. Maybe the log tells the reason. The RA core info page is only looking for the first file in the info row, so it does not matter if |
|
Ah that makes sense. I can run whdload games fine with cloanto roms, but I thought it was using some "backup" method (aros?) as the info was stating they were missing. I can run a CDTV game if I force the system to CDTV (file is under a CDTV folder, I thought "automatic would detect this and adjust accordingly?) I cannot run CD32 games though (Banshee for example), even if I set the system to CD32 rather than automatic. I just get the amiga 3.1 ROM 40.060 insert disk animation. (This is what lead me to believe the roms were not recognised.) If I try to force the kickstart rom I also see no option: This is the log after setting the system to CD32 and relaunching the cd image: |
|
Use triple backticks since nobody can read that mess. |
|
apologies, fixed |
|
There is no mention of the CD32 extended ROM, so there is no way it can work. Also how come the log stops like that as if it crashes.. |
|
not sure, I just moved out of retroarch's focus and copied the content of the log here. I did some more experimenting, and I got it to work if I use the cloanto here are some logs...
Could be an issue with the 'amiga-os-310-cd32.rom'? Strange that in the first example the log mentions this rom, but not the extended one that I know works. Perhaps the cloanto 'amiga-os-310-cd32.rom' causes some sort of crash and the core doesn't bother checking for the extended as well? (just an uneducated wild guess) |
|
Works fine here. |
|
are these the MD5 for your files? (from amiga forever 7) EDIT: adding the key rom MD5 as well: |
|
My MD5s are the as in the ReadMe and in the info, so not either of those: https://github.com/libretro/libretro-uae?tab=readme-ov-file#kickstart-roms Still your logs say: |
|
Yeah that's pretty confusing. Not sure what else to try, I know these are legit as I purchased them myself, and I have been using them in FS-UAE for quite a few years (played CD32 games as well) It's not the end of the world to me as I sourced other roms, so I can use PUAE fine, but I wanted to flag this for others that have the same set of roms. If this is something you think it's worth investigating further I am happy to provide you my set and test potential fixes, but I imagine you already have a lot going on, and this would be pretty low priority |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, apologies I am aware there is a closed thread with the same issue (#625)
I tried to use the kickstart roms from cloanto 7 that I bought a few years ago but these were not recognised by PUAE. When I checked the info in retroarch, it said that the roms were missing.
They are indeed a different checksum than the ones on the PUAE readme, but I thought support was added according to issue #625.
The md5 of my roms are identical to the ones that were reported in the above issue as they are from the same cloanto version.
In the end resorted to find suitable roms online (which work and have the expected MD5 values), but it seems silly to resort to download roms elsewhere if I purchased them legally :) - I also didn't feel like re-buying them and hoping they are the correct MD5 value
These are kickstart roms with the key, and I included the key in the retroarch system folder together with the roms
Was support actually added for these roms and maybe I am doing something wrong?
Thanks!
The text was updated successfully, but these errors were encountered: