I recently bought a Gigabyte 686DX system with dual PPro 200's and
2 * 32Mb parity memory in hopes of getting ECC memory implemented.
The systems runs "fine" with parity disabled, which was the way
the system was delivered.
With either parity enabled or ECC enabled, the system traps out with
a "parity error" any where from 5 minutes to several hours of run time.
1) Can I assume that the parity system is "working" and that it is
probably a bad SIMM ? If not, how can I tell what the problem is ?
It is scarey to think that with parity disabled, I could not tell
if there was any problem and went about installing lots of software. It would
seem that potentially bits could be wrong here and there, everywhere.
2) Under Windows 95, what is the practical difference between ECC and
parity ? How can I tell if the ECC circuitry has successfully corrected a
single bit error ? Does the BIOS/OS trap out with an ECC correction or just
with a greater than single bit error detection ?
Obviously if Windows 95/BIOS is going to trap out even with an ECC
single bit detect->correct, then it is pointless to have ECC over parity.
3) What is the situation wrt ECC handling in other OS's: NT, FreeBSD,
Dan Ts'o 212-327-7671
Dept. of Neurobiology FAX: 212-327-7671
The Rockefeller University