Xref: utzoo comp.sys.ibm.pc.misc:4996 comp.misc:11022
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!wuarchive!uunet!sceard!mrm
From: mrm@sceard.Sceard.COM (M.R.Murphy)
Newsgroups: comp.sys.ibm.pc.misc,comp.misc
Subject: Re: Help! Memory Parity Problem!!
Message-ID: <1990Dec24.183030.26148@sceard.Sceard.COM>
Date: 24 Dec 90 18:30:30 GMT
References: <1990Dec20.185019.29981@portia.Stanford.EDU> <6ePNu1w163w@pain>
Reply-To: mrm@Sceard.COM (M.R.Murphy)
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 17

In article <6ePNu1w163w@pain> qaz_wsx@pain (Scott Kelley) writes:
>shedevil@portia.Stanford.EDU (Annie) writes:
[Scott says he has memory errors, Annie says replace it all]

Now this is about to be a really heretical suggestion, so hold on...

Run memory diagnostics from a good diagnostic package. (IBM(tm) as a minimum).

Replace what it says to replace, or, swap out a chip or pack at a time until
the diagnostic runs clean.

This may take longer than just replacing the whole shebang, but it ends up by
giving the person doing the fixing a warm and fuzzy feeling that they know what
is going on. Whether they do or not :-)

-- 
Mike Murphy  mrm@Sceard.COM  ucsd!sceard!mrm  +1 619 598 5874