home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!inmos!fulcrum!bham!warwick!pavo.csi.cam.ac.uk!rm113
- From: rm113@cus.cam.ac.uk (R. Moss-Eccardt)
- Subject: Re: HELP! OS/2 no-go after board upgrade
- Message-ID: <1993Jan28.110852.27661@infodev.cam.ac.uk>
- Sender: news@infodev.cam.ac.uk (USENET news)
- Nntp-Posting-Host: bootes.cus.cam.ac.uk
- Organization: U of Cambridge, England
- References: <1993Jan26.170130.25555@midway.uchicago.edu> <1993Jan27.140243.900@infodev.cam.ac.uk> <jcmorris.728152342@mwunix>
- Date: Thu, 28 Jan 1993 11:08:52 GMT
- Lines: 26
-
- In article <jcmorris.728152342@mwunix> jcmorris@mwunix.mitre.org (Joe Morris) writes:
- >rm113@cus.cam.ac.uk (R. Moss-Eccardt) writes:
- >
- >>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
-
- I can't quite lay my hand on the bit of paper I got from the Support Centre.
- It was part of an IBM internal document that is a complete 'how to diagnose
- TRAP errors' guide. It lists all sorts of part numbers that can cause
- problems, not just 70s, but 55s and others. It also refers to a program you
- can run to isolate bad SIMMs.
- However, the particular EC fixes TRAPs at cold-start. If your machine boots
- cleanly, then you don't have the problem.
-
-