In article <BzCAMs.Knn@news.cso.uiuc.edu> nap42487@uxa.cso.uiuc.edu (Nishith A. Patel) writes:
>There are still some problems with OS/2 as far as traps go. I get a lot of trap 0002's, and my memory is fine. I also got a trap 000e a couple times, and hear
>that this is also a bug in OS/2.
>
>I am hoping they fix these problems in a future update, as well as make it more
>stable (I crash it a lot). I never had any problems with win 3.0, and don't
>see why OS/2 has all these problems. Maybe when they get the bugs out, it will
>be a stable environment that I was hoping for.
>
>
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