Workbench 1.3.2 and  3.2 aren't compatible. And which kickstart do you have - it defines the Workbench version to be used.

First, thank for your reply. Overall, my experience with the 3000 has not been great, kind of a poor introduction to the Amiga world. Some of this is a matter of circumstance rather than any technical problems. In particular, AmigaKit have yet to ship my October 19th order of a Gotek and battery holder, so that's helped little. The A3000 is complicated, which is not unjustified, but it's not quite the tone I'm after in retro hardware.

On a more practical note, I've since obtained an excellent condition A1000 with apparently all its original material (and a boat load of floppies). After some frustration with floppy swapping, and a talk with Mr Dunklee last week and various promises on YouTube and elsewhere of being "transformative", my Parceiro II is already in the mail, and this is much more likely the machine I will keep long term.

Anyway, for the 3000, I ended up getting a null modem cable, and after quite a bit of pain, able to boot strap the 3000 from 1.3 workbench into 3.2 and get some other tools onto floppies.

I have not exhaustively been through the test tools, but to date, I have spotted anything at all of note - everything seems to be working fine, apart from the SCSI (possibly the floppy could use some maintenance).

In fact, the instability in the system appears to be 100% attributed to when the SCSI drive is connected. I see this is a fair bit of grief for 3000 owners, but I have not been able to find my exact problems:

Workbench 1.3.2 boots fine. I can run HDToolbox (I tried a few versions, including the one from the Workbench 3.2 install disk. It will find the drive, and validate blocks OK, but there do not seem to be any partitions. Attempts to partition result in a crash.

Workbench 3.2 will not boot with the drive connected (sorry, not sure about images and attachments here), result in the red crash screen - "Software failure".

If I try to run from Workbench 1.3.2 the 3.2 install program, then it'll crash as well - "Program Failed (error #80000004)".

So, is this a termination problem? As I think I mentioned, the drive was loose when I got it, so perhaps there was some previous attempt to replace it.  I know that messing with old SCSI drives might in the end be futile, but I'd still like to see if I can get it working.  Are there any other tools worth trying here, or diagnostics I can provide?

Thanks again.

I released the v1.501 as web update.

Just use the Help/ Check for updates function to get it.

New modules since v1.50:
Lumo *.MESH Load

I've written a thousand times that it doesn't work and what the problem is with the Sk A1200.

 I repeat:
I was doing some tests by restarting the A1200 several times, and at a certain point, while it was restarting (I was busy with something else), I noticed a faint burning smell with no smoke and a black screen....
I quickly turned it off.
Once restarted, the A1200 displays a yellow screen and the power LED flashes 9 times, then a black screen and restarts.

Suspected so. Thanks.
Might have a go at cleaning it up if I get time otherwise will sell for spares.