Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!eik.ii.uib.no!alf.uib.no!livid.uib.no!PPSTL
From: PPSTL@livid.uib.no
Newsgroups: comp.sys.next
Subject: Re: Shouldn't 70 ns SIMMs work with '040?? (they don't for me, anyway)
Message-ID: <1991Jun1.143627.15471@alf.uib.no>
Date: 1 Jun 91 15:45:06 GMT
Sender: usenet@alf.uib.no (Bergen University Newsaccount)
Organization: University of Bergen
Lines: 58

------------------------- Original Article -------------------------
Path: alf.uib.no!ugle.unit.no!sunic!hagbard!eru!bloom-beacon!ora!camb.com!spdcc!
From: federico@actisb.UUCP (Federico Heinz)
Newsgroups: comp.sys.next
Subject: Shouldn't 70 ns SIMMs work with '040?? (they don't for me, anyway)
Keywords: SIMM 70 ns 68040
Message-ID: <1429@actisb.UUCP>
Date: 31 May 91 21:26:11 GMT
Organization: Actis in Berlin GmbH, W. Germany
Lines: 29

Well, I guess that after over a month of flawless operation and
constant admiration for the machine, reality struck me for the first
time. Today I upgraded my '030 Cube to the '040 board, and therefore
transplanted all my SIMMs from the old to the new CPU board.

Expecting the machine to FLY, I turned it on, and it flew allright...
into the following error message:

Exception #2 (0x8) at 0x100416e

and there was no way of getting it to boot. I then removed half of the
SIMMs (the ones I bought to upgrade to 16MB), it worked fine. When I
left only the new SIMMs in, the machine crashed in almost exactly the
same way (different number after 'at'). The amazing thing about all
this is that the ROM monitor's 'm'-command correctly recognized the
SIMMs, but the machine wouldn't boot. Not only did the SIMMs pass the
power-on memory test, they work perfectly with the '030 board too (I
tried it with them as the only memory). I suspected this to be a
parity-no parity thing, but parity checking was disabled. Of course, I
had written the 2.0 boot block to the disk, but the thing wouldn't
even boot out of the optical.

The SIMMs that don't work are 1MBx9, 70 ns, and I'm attempting to use
them together wih the original 1MBx8 SIMMs that came with the Cube.
I'm puzzled. Furthermore, I'm scared I just threw the money for these
8MB out of the window. Any ideas about what may be going wrong here?

--
               Federico Heinz (federico@actisb.uucp)

I have also posted regarding this, when I first received my 040 upgrade.
Using the ROM monitor, turn off memory check on power on and turn off
parity use if present.  Power off on on again - it should work.  I have
8MB 100ns 1x8 (NeXT orig.), 4MB 80ns 1x9, and 4MB 70ns 1x9 in my cube
and it works like a charm (for those of you following my hard disk soap
opera oddessy, The Formatter saved the disk - and the eight day final I
am in the middle of when the disk crashed...Many,manymany thanks to Ronald
Antony and Charles Purcell for their patience)

Of course, the machine operates at the speed of the _slowest_ memory
in the machine, thus I get a message "100ns" memory on boot - not 80 or 70.

Hope this helps.
Thor Legvold
University of Bergen
Norway
me@fiol.uib.no <- NeXTmail, er du snill.