#SetPatch Crash/A3000 3.1
29-Sep-94 10:03:29
Sb: #42801-#SetPatch Crash/A3000 3.1
Fm: Dave Arre 70337,1642
To: Richard Beausang 74130,3663
Richard:
Thanks for your help…
We might be on to something. Here is what I found when I replaced the
ROMS:
The ROMs originally in the machine… Labeled "390629-02 ROM0v5 C1990
Commodore-Amiga 9042D" Were sitting in sockets near the mouse port.
Adjacent to them were two "pads" labeled ROM0 and ROM1, with no sockets.
The original ROMs were in sockets labeled U180 and U181, also ROM0 and
ROM1 while the pads are U182 and U183. I pulled the old ROMs and installed
the new ones per instructions in the sockets.
There is a jumper near them, but the schematic says it is an "A2000 ROM
compatibility jumper" so I left it alone.
The odd thing is that about a year ago (with softkick WB 2.04) I
downloaded SetPatch v37.38 from CIS, and tried to replace my v37.10, and
the same thing happened (the system would not boot). I stored the old
setpatch away, only to dust it off and try it again now… SAME result as
v40.16.
I think there might be something else going on here besides ROM chips /
softkick. There might be a memory select problem, or a CPU thing.
What would you think about running the system with NO setpatch at all? It
seems to work great without it! <g>
— Dave