SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 36.15-0.6%Dec 24 12:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Bill Jackson who wrote (148154)11/14/2001 4:25:17 PM
From: wanna_bmw  Read Replies (2) of 186894
 
Bill, after seeing several press releases on this issue, it appears that no one really knows where the issue is. Compaq would obviously like to think it's a processor issue, because otherwise it would be a Compaq issue. Intel is not going to say one way or another until they've had time to test it and root cause the problem. The fact that this has leaked into the public, and people still don't know the root cause tells me that it's a pretty obscure problem. Since Compaq's tests were the only ones able to uncover this problem, that suggests that it is infrequent enough not to have been detected elsewhere.

All that Intel can do is progress further into debug, but such things are normal in a prerelease state. If this thing hadn't leaked out, you'd have probably never heard of it. Even IBM and others have these kinds of issues, but it's big news when the media is able to catch such a leak and then make ignorant conclusions based on their inexperience with the debug process.

wbmw
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext