[SunRescue] SS2 RAM parity error weirdness

[Gregory Leblanc]

So I'm generating a lot of questions lately, sue me.  :-)  Anyway, I've got
this SS2 here, and I had a bunch of 1MB simms lying around that I wanted to
use.  So, I grabbed 4 sets of 4, for a total of 16MB.  I stuck them in the
SS2 in order from "back" to front (not the order in the SHR), one bank at a
time.  After inserting a bank, I'd connect the machine to my monitor and
type5 keyboard, boot, and do a ram test.  Every test came back happy.  When
finished, I had 16MB of ram in this machine (it's going to be a router,
doesn't need much).  Just a moment ago, I connected up my keyboard/monitor
to my SS20, and got the output from the serial console on the SS2.  It says
"
FAILURE: Incorrect Parity Error, MER (1fb40000) Exp = 000000dfCan't open
input device."
I believe it, since I don't think that I had 16 true parity simms, some of
them were probably logic chip parity.  
My questions are, 1) how can I tell which ram it's talking about? and 2) why
didn't it gripe on the memory test when booting from the real console?  
Thanks,
	Greg

|---------------------------------------------------|
| Windows NT has detected that there were no errors |
| for the past 10 minutes. The system will now try  |
| to restart or crash. Click the OK button to       |
| continue.                                         |
|                      < Ok >                       |
|---------------------------------------------------|
(sigline nicked from Jayan M on comp.os.linux.misc)