home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!nap42487
- From: nap42487@uxa.cso.uiuc.edu (Nishith A. Patel)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Mix of 3-chip and 9-chip simms with OS/2
- Message-ID: <BzDMF3.4F9@news.cso.uiuc.edu>
- Date: 16 Dec 92 23:54:36 GMT
- References: <1gm6deINNjqd@agate.berkeley.edu> <1gmc2lINN5ai@tamsun.tamu.edu> <BzCAMs.Knn@news.cso.uiuc.edu> <1992Dec16.163047.6231@wam.umd.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Lines: 15
-
- 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.
-