Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!davidsen
From: davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Program To Find Bug In 80386...
Message-ID: <7955@steinmetz.steinmetz.UUCP>
Date: Tue, 24-Nov-87 08:49:56 EST
Article-I.D.: steinmet.7955
Posted: Tue Nov 24 08:49:56 1987
Date-Received: Sat, 28-Nov-87 01:09:20 EST
References: <263@grinch.grinch.UUCP> <1871@celtics.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 23
Keywords: 80386, Intel

In article <1871@celtics.UUCP> roger@celtics.UUCP (Roger B.A. Klorese) writes:
|In article <263@grinch.grinch.UUCP> luis@grinch.UUCP (luis) writes:
|>     One user requested that I not post the program because of possibilites
|>that the bug/problem of the 386 is not with the archetecture of the chip,
|>but rather that the error could be caused by heat, environment, etc.

luis, you misunderstood what I said... Intel did not deny that there is
a bug in the chip. When I posted the program to the 80386 mailing list,
Intel sent me E-mail saying
	1) this program will not identify most bad chips
	2) no program will identify most bad chips
	3) only hardware can reliably find bad chips
	4) if there was a program which found bad chips intel would
	   distribute it and use it in-house instead of an expensive
	   and time consuming hardware test.

Let me make it perfectly clear; the program doesn't work.  90+% of the
bad chips will pass this program. 

-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me