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.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Goutam who wrote (78084)11/1/1999 5:16:00 AM
From: Process Boy  Read Replies (2) of 1571714
 
Goutama - <Also, as I think of more and more about the lack of PIII-733EB parts in the channel, it's becoming more clear to me that Coppermine 733MHZ was released to save Craig Barret's honor (remember about his proclamation of releasing 7xxMHZ Coppermine parts in a recent Intel developers forum). PIII-733EB-CBH ;o)>

Message 11760483

Also, Otellini said that he is utterly confident that whatever speed grade Intel releases, it will be in volume.

I guess there is a choice whether to believe him or not.

Also worth repeating; I wonder how much the i820 delay has to do with the 733's being somewhat in short supply? If there is an impending release of i820 before the end of the year, might the OEM's who are going to release i820 based systems be getting the lions share of 733's?

But if you really want one, CPQ has a couple of i840 / 733 systems on their Website, and Micron has a 733 system also.

I'm curious if the report of i820 systems at Comdex is true.

I will take this opportunity to grovel a little bit: I did expect to see more Coppermines in the channel post launch. This is obviously not the case. I was flat wrong, as I did not anticipate a situation where demand was such that the OEM's would be getting virtually all Coppermine shipments post launch.

Best I can tell, some disti's are expecting Coppermine product in the middle of November.

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