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) -- Ignore unavailable to you. Want to Upgrade?


To: pgerassi who wrote (106953)8/3/2000 9:11:40 PM
From: semiconeng  Read Replies (1) | Respond to of 186894
 
Then why did it work just fine at 850 on same CPU same motherboards? Thus, it is not a software problem.

That's an interesting conclusion that you've jumped to, in light of the fact that Tom himself stated that a microcode update was required for PIII 1.13GHz, as well as a voltage increase to 1.8v. In light of these differences, it appears, that your "comparisons", of the 1.13GHz chip to the 800MHz chip, do not seem to be valid

If it was a speed problem with the software, then 1150 MHz Tbird would have been unstable. Thus, since the motherboards were different, it points positively to the CPU in question.

Boy, that's the biggest leap yet. The freeware worked with the T-Bird, so it should work with a PIII. I never said it was a speed problem, I said it was a software bug problem. Ignore the fact that the T-Bird and PIII cores and microcode, are different designs, and maybe your statement might hold water. Otherwise....

Kyle did go through the simple troubleshooting procedure.

Pete


Ah, and what did he find? Did he examine the uncompiled prime95 code, to determine if there were any further possability of bugs? I didn't read that, did you?

SemiconEng