Crash on IIgs boot on macOS

[nriley]

I attempted to open an 800K disk image I expected to launch with an emulated //e, but instead it started as a IIgs.

The first ROM request was for ROM 01 + the ROM 03 ADB controller ROM, which (after a bunch of part number searching) I was able to supply. However, immediately after providing these (one at a time), Clock Signal crashed and then crashed immediately open reopening, apparently while attempting to restore the previous state. I was able to get it to start by telling macOS not to restore its state, but it still crashed when opening the same image.

There appeared to be no symbols in the distributed version of Clock Signal so I built it from source, but of course I couldn't get my self-built version to crash. (It did additionally ask for a //e character set ROM when I reopened the same image). I read the IIgs emulation is not complete but in case this helps, here's a screenshot after successfully booting.

Crash logs are below.

crash.txt

crash1.txt

(Also if there's any way to force an image to boot with a //e, that would be good too!)

[TomHarte]

At present the emulator usually selects the IIgs only if it has a disk image it doesn't know how to open with a regular II, primarily because they don't currently support larger disk images than those of the Disk II. Though that isn't universally true.

... and regardless of anything else, the IIgs shouldn't crash. That's embarrassing. I'll look into it. Is the triggering disk image one of those that can be redistributed?

[nriley]

Thanks! Makes sense if you haven't implemented SmartPort/3.5ʺ support as most of the stuff you'd want to play on a //e is on 5.25ʺ disk.

Please see attached disk image.

Copy II Plus 9.1 : ProDOS 8 1.8 (1990, req’s enhanced IIe).2MG.zip

[murphytex]

Hello,
I ve got the same issue with the IIgs. The latest version which does not crash is the Clock.Signal.2023-09-10. All version after that crash when I try to add the roms.