Xref: utzoo comp.arch:12270 comp.sys.intel:997 comp.sys.ibm.pc:37773
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!unmvax!bbx!bbxsda!scott
From: scott@bbxsda.UUCP (Scott Amspoker)
Newsgroups: comp.arch,comp.sys.intel,comp.sys.ibm.pc
Subject: Re: Compaq find problem with chip
Message-ID: <326@bbxsda.UUCP>
Date: 7 Nov 89 16:15:24 GMT
References: <2719@ganymede.inmos.co.uk> <2725@ganymede.inmos.co.uk> <2800@ganymede.inmos.co.uk> <63979@psuecl.bitnet>
Reply-To: scott@bbxsda.UUCP (Scott Amspoker)
Organization: Basis International,  Albuquerque, NM
Lines: 19

In article <63979@psuecl.bitnet> c9h@psuecl.bitnet writes:
>In article <2800@ganymede.inmos.co.uk>, conor@inmos.co.uk (Conor O'Neill) writes:
>> [Intel announces that mysterious 486 bug has been fixed]
>>
>> As usual, not enough information for anyone to use.
>
>Not enough information?  What the Hell do you want?  They offered to replace
>the chips, for Christ's sake!  Jesus!  Some people are never satisfied!

I agree with Conor.  I want to know exactly what the problem was.  It
is not enough that Intel will ship new 486 chips.  When I have a customer
on the phone complaining about a bug in our software I want to recognize
the symptoms of an early 486 that somehow did not get updated.

-- 
Scott Amspoker
Basis International, Albuquerque, NM
(505) 345-5232
unmvax.cs.unm.edu!bbx!bbxsda!scott