home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!concert!gatech!usenet.ins.cwru.edu!agate!linus!linus.mitre.org!jcmorris
- From: jcmorris@mwunix.mitre.org (Joe Morris)
- Subject: Re: HELP! OS/2 no-go after board upgrade
- Message-ID: <jcmorris.728152342@mwunix>
- Sender: news@linus.mitre.org (News Service)
- Nntp-Posting-Host: mwunix.mitre.org
- Organization: The MITRE Corporation
- References: <1993Jan25.193345.1@vax1.umkc.edu> <1993Jan26.170130.25555@midway.uchicago.edu> <1993Jan27.140243.900@infodev.cam.ac.uk>
- Date: Wed, 27 Jan 1993 16:32:22 GMT
- Lines: 23
-
- rm113@cus.cam.ac.uk (R. Moss-Eccardt) writes:
-
- >In article <1993Jan26.170130.25555@midway.uchicago.edu> sip1@midway.uchicago.edu writes:
-
- >>It's in the FAQ List (of course). :-) "TRAP 0002" means bad RAM --
- >>the RAM is probably too slow for your system. Increase the wait
- >>states in the setup, precharge cycles, etc., and see if that clears up
- >>the problem.
-
- >To be rather pedantic, it doesn't just mean 'bad RAM'. We get TRAP 0002s
- >on PS/2 70-121s because they have a slightly older processor module. IBM
- >have an Engineering Change available for such machines.
-
- Can you tell us how to identify the 70-121 units which are in need of the
- EC? I'm running an evaluation of OS/2 using a -121, although most of its
- use is under DOS (via dual boot). I haven't run into a 0002 and would
- prefer to avoid it if possible.
-
- (I don't even know the vintage of the motherboard. The box got a new
- (or more properly, refurbished) system board a few years ago after
- the onboard async adapter died.)
-
- Joe Morris
-