🚀 go-pugleaf

Mohan Matthen writes
> For a couple of days now I have been having problems running NB under Windows,
> with MX=10 enabled. At least five times in three days, the whole system is
> shut down with a full screen message that says: "Memory parity error detected.
> System halted." And then there is no choice except to switch the computer off.
> Even a warm boot is not possible. I have only just disabled MX=10; so I can't
> say with complete confidence that that's the problem, but in the meanwhile,
> can I ask whether anybody else has had this problem, in this or any other
> context. Incidentally, I don't even know which system is issuing this message:
> Windows, EMM, DOS?
It's Windows detecting the error.
I subscribe to another list devoted to Windows and that has had discussions
about parity errors with Windows 3.1.
Apparently the official Microsoft line is that 3.1 detects memory parity
errors that most hardware diagnostic programs fail to find !  Version 3.0
did not cause this problem because there was (is) a bug in the parity checking
handler in 3.0.  I suspect that 3.1 is detecting spurious errors.  Some users
have avoided the problems by moving their RAM around.  There might also be
a connection with mixing different speed/size RAM chips.
--
Neil Brooks, University of Exeter Computer Unit
Electronic mail: Brooks@uk.ac.exeter
Phone: (+44) 392 263946
Postal Address: Laver Building, North Park Road, Exeter EX4 4QE, Devon, U.K.