OS3.2 image prepared in WinUAE crashes on real A1200....unless Echo is on

[AndyFC]

I've created a new OS 3.2.2.1 image in WinUAE and just moved it to a real A1200 with Blizzard 1230 mkIV. I transferred it from WinUAE by creating an LHA file withing the emulated Amiga, copying to the real Amiga CF card, which is connected via CF-IDE adapter, then unpacking it on the existing FFS partition.

The main difference is I use Blizkick in the real Amiga to use the 3.2 ROM. The real ROM is 3.0.

When it boots...
1) Loads new Kickstart and reboots
2) Runs loadmodule and reboots
3) starts to boot, crashes with flashing power light then a Software Failure red box.

I started debugging using hints found online and one step I tried was to add 'Set ECHO ON' as the first line in the startup-sequence to see what causes the crash but...

...with this line there, the Amiga boots to WB. Without the line, or it's commented out, I get the same crash every time. So it seems the issue isn't anything the SS is trying to run, but trying to run without output to screen.

Any ideas why this is happening please? Thank you.

[F0LLETT]

I've created a new OS 3.2.2.1 image in WinUAE and just moved it to a real A1200 with Blizzard 1230 mkIV. I transferred it from WinUAE by creating an LHA file withing the emulated Amiga, copying to the real Amiga CF card, which is connected via CF-IDE adapter, then unpacking it on the existing FFS partition.

The main difference is I use Blizkick in the real Amiga to use the 3.2 ROM. The real ROM is 3.0.

When it boots...
1) Loads new Kickstart and reboots
2) Runs loadmodule and reboots
3) starts to boot, crashes with flashing power light then a Software Failure red box.

I started debugging using hints found online and one step I tried was to add 'Set ECHO ON' as the first line in the startup-sequence to see what causes the crash but...

...with this line there, the Amiga boots to WB. Without the line, or it's commented out, I get the same crash every time. So it seems the issue isn't anything the SS is trying to run, but trying to run without output to screen.

Any ideas why this is happening please? Thank you.

Early startup menu and select trace boot, if I recall. It then boots giving you option to load each line of startup-sequence. As soon as you get to line that crashes it you will know. You can also tell it to log.
I bet its Loadwb.

[AndyFC]

Thank you, the early startup was the option I'd read something about but couldn't remember precisely what it was. The odd things are using either this, or Set Echo on,

1) using the Set Echo on option, after the Amiga has finished booting once it will boot after every soft reset, even if I've removed the line from the SS

2) using the trace startup option the startup Gurus after the second bootup reset (after Loadmodule) before it even displays any choices for me as if it doesnt get as far as the SS. Similarly to 1, if I successfully boot, then remove the Set Echo On line, soft reset and use the Trace option in a subsequent reboot, it all loads without issue.

[Thomas]

The main difference

You should configure WinUAE so that there is no difference. I see nothing in your description which cannot be emulated.

Unfortunately the 3.2 installer makes different installs depending on various hardware.

One indication is that you say LoadModule resets the computer. If you use Blizkick to load the latest ROM, then there should not be a second reset by LoadModule.

[F0LLETT]

One indication is that you say LoadModule resets the computer. If you use Blizkick to load the latest ROM, then there should not be a second reset by LoadModule.

Good point, forgot about that, as he is using updated rom.
However, shouldnt loadmodule check modules before loading, just incase they are already updated, then ignore loading them. If that makes sense.
Means you would not have to worry about commenting / removing suff from startup.

[AndyFC]

Unfortunately the 3.2 installer makes different installs depending on various hardware.

One indication is that you say LoadModule resets the computer. If you use Blizkick to load the latest ROM, then there should not be a second reset by LoadModule.

Thank you; I began to suspect this. I was hoping to do one image that could be added to different machines. A positive is that I've done all the discovery in UAE, recorded the steps of what I added/configured, and so it will be easy to install exactly from scratch on real hardware. It'll be a cathartic exercise one autumn weekend.

[Thomas]

I could reproduce your issue in WinUAE. Using the original 47.96 ROM during installation did not install LoadModule, but the update to 3.2.2.1 did. In this constallation (ROM 3.2.0 with WB 3.2.2) it crashes after LoadModule. The upgrade to ROM 47.111 fixes it. So just use the 47.111 ROM file with Blizkick.

[AndyFC]

Thank you Thomas for looking at this. I copied the ROM from the 3.2.2.1 update and it fixed it. I thought this was the one I was already soft kicking to, but I checked and it was 47.96. A silly mistake at the end of a fun project to create a clean image with all the features I wanted.