home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!pan.mc.ti.com!rgam.sc.ti.com!rgammon
- From: 5692330@mcimail.com (Robert Gammon)
- Subject: Re: Mix of 3-chip and 9-chip simms with OS/2
- Message-ID: <921218162741@rgam.sc.ti.com>
- Nntp-Software: PC/TCP NNTP
- Lines: 29
- Sender: usenet@pan.mc.ti.com (USENET News System)
- Organization: Texas Instruments Materials and Controls Group
- References: <1gm6deINNjqd@agate.berkeley.edu> <1gmc2lINN5ai@tamsun.tamu.edu> <BzCAMs.Knn@news.cso.uiuc.edu> <1992Dec16.163047.6231@wam.umd.edu> <BzDMF3.4F9@news.cso.uiuc.edu>
- Date: Fri, 18 Dec 1992 21:27:41 GMT
-
- In article <BzDMF3.4F9@news.cso.uiuc.edu> nap42487@uxa.cso.uiuc.edu (Nishith A. Patel) writes:
-
- >> adhir@wam.umd.edu (Al Dhir) writes:
- >>
- >> >I hate to be the one to tell you this, but a Trap 002 DEFINITELY means a
- >> >problem with memory. I say this from experience. In all cases I've ever
- >> >seen (and I see alot, I am a PC Tech consultant), Memory Parity errors
- >> >have ALWAYS been bad memory (in one case the guy had his Memory Speed set
- >> >too fast in his AMI Bios...). If I were you, I'd stop blaming OS/2 and
- >> >take a close look at my hardware.
- >>
- >> In this case, it is a bug. My memory is fine, this is a case you probably have
- >> not seen. I have taken a look at the hardware, and everything is fine.
- >> And no, I haven't mixed 70 and 80 ns SIMMS, or 3 chip and 9 chip SIMMS.
- >> When every singel indication you have says the memory is not a problem, and
- >> you get a program that all of a sudden chokes and dies, guess what, it is a
- >> a problem with the program.
- >>
- >>
-
- You still may have a memory problem. I have seen this kind of problem solved
- by swapping out old SIMMs for new ones. Looks like borderline failures (slow
- access, resulting in intermittent parity errors)
-
- --
- Regards,
- Robert Gammon
- (713)-274-3299 (voice)
- (713)-274-2324 (fax)
-
-