cd32 game addition fails.

[SkulleateR]

Did you install the CD32 roms (kick + extended) ?

[SkulleateR]

Just tested with my old install and also the new update 46.1.916 from today and everything works fine, maybe just delete and re-install the cd32 roms ?

Had the same issue some time ago with my kick3.1 and the A1200 config, after kick reinstall all started working again 

[SkulleateR]

I've had that same problem, except when I go to the edit screen, the GS resets.  When I run the disc image, I get the AROS screen, and it hangs there, saying "waiting for a bootable image."  I haven't installed any CD32 ROMs yet.

As expected since the AROS Rom isn´t very CD32 friendly 

[SkulleateR]

Hi,

the game is dungeonette, on seleting add game. you pick the iso and the screen blacks out for a few seconds. when trying to play the game (that is showing installed). it goes to the aros awaiting bootable media screen. if you try to click edit on this game the system resets. so theres corrupted games on the system i cant remove because i cant edit them...and yes i am on the latest update.

Hope that helps.

Yes, can confirm that behaviour

Steps :

- +ADD
- Choose ISO
- Screen goes blank / A600GS resets (without the possibility to choose the settings)
- back in Menu there is the Menu item for the game
- click on EDIT and the A600GS resets again

So there is no chance to edit the entry or delete it, if you start it the AROS Kickstart comes up.

BUT it´s not with all CD32 ISOs ... just tried Beneath a Steel Sky CD32 ISO and that works as expected 

[SkulleateR]

Found the culprit (I guess)

If you buy the digital version of Dungeonette, the file is named : Dungeonette-CD32.ISO

Seems that the A600GS doesn´t handle capital letters in the extension of the files very well, so if you rename .ISO to .iso it will work and also let you edit and delete the entry. Can be reproduced easily, just rename any CD32 iso to XYZ.ISO, then ADD it and you will see it will crash ... now we only need a solution to delete the broken menu items since we cannot de-protect them 

[SkulleateR]

This is why developers shouldn't test their own software :-)

Call me