Strange problem with WB 3.1 on A3000Tower

[x56h34]

@don27dog:

The A3000T and A3000D use exactly the same roms.

The original poster should verify that the WB3.1 disks do not have anything on them that would be specific to his "previous setup", in terms of cpu libraries and such. If he could try a set of new WB3.1 installation disks, that would be a good initial troubleshooting step.

[x56h34]

@zimgr5:

If you can see the Kickstart 3.1 insert floppy screen, then your jumper config is ok. At this point try and insert a floppy disk of let's say a game or some known to work (a3000 compatible) auto-booting piece of software and that way you will immediately prove or disprove proper functionality of your Amiga, should that game/software load and work ok. A set of fresh WB3.1 installation disks would be ideal.

Have you also tried booting from your WB3.1 Workbench disk?
Have you tried booting from the Workbench disk or the install disk with your hard drive disconnected from the scsi chain?
How much fast ram and how much chip ram does your A3000 have?
Have you tried removing all the fast memory and booting only with chip?

[x56h34]

SOFTWARE FAILURE CODE : 8000 0003 0700DEBQ Press left mouse button to continue

Perhaps your A3000's NVRAM is corrupted and it needs a reset? It is the only "cache-type" memory that will survive a complete shutdown. A3000 has it, unlike other Amigas.

You can use SetBatt to reset it or tweak its settings (search for SetBatt on Aminet). It is specifically used to keep settings for the on-board SCSI controller.

If an Amiga virus could hide somewhere, it would be there or on the floppy disk itself. Also, NVRAM in A3000 is known to get into a state of "amnesia" and needs a reset through SetBatt, so it could be another thing to check.

8MB chip & 16MB RAM.

You can only have up to 2MB of chip ram with any Amiga.
It is possible that your memory is faulty too, and as soon as a particular part of the memory banks gets accessed by data you get an error or a crash.
As a last resort type solution, try and pull all of the fast memory out and see if with only 2MB of chip ram you don't get that error message anymore.

Try inspecting those Workbench disks on another amiga (if possible) and see if they carry any library files or similar, that would load on boot and cause this error/crash. Like I mentioned, they could have some needed files for an expansion that is no longer there (e.g. WarpEngine or a GFX card, etc.)

Also keep in mind that I am giving you some ideas as how to troubleshoot this issue and while I may not necessarily be right with any of my suggestions it's just means of isolating some of many possible causes for this error message that you are getting.

I'll let you know if something else comes to mind.