Xref: utzoo comp.sys.ibm.pc.misc:5052 comp.misc:11030
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!news.larc.nasa.gov!ipsun.larc.nasa.gov!jcburt
From: jcburt@ipsun.larc.nasa.gov (John Burton)
Newsgroups: comp.sys.ibm.pc.misc,comp.misc
Subject: Re: Help! Memory Parity Problem!!
Message-ID: <1990Dec28.011316.6747@news.larc.nasa.gov>
Date: 28 Dec 90 01:13:16 GMT
References: <1990Dec20.185019.29981@portia.Stanford.EDU> <1990Dec21.014724.6974@javelin.es.com> <90355.083729RFM@psuvm.psu.edu>
Sender: news@news.larc.nasa.gov (USENET Network News)
Organization: NASA Langley Research Center, Hampton, VA  USA
Lines: 10

Another thing you might want to look for is dust on the chips/boards
etc... get a can of "dust-off" from a camera store or computer supply
store...

dust partially shorting contacts can cause flakey errors such as
you mention. also its amazing how much dust can accumulate in a *very*
short time...

John Burton
(jcburt@cs.wm.edu)