Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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

To: Paul Engel who wrote (37729)	9/29/1998 6:23:00 PM
From: Dr. Saeed Assadi	Respond to of 1572931

Paul, I am not an AMD defender, but I think I understand the severity of the bug. Intel could be better. I expect them to do a better job, and as you have posted, they have. Still, the timing problem is unimportant. Best regards, sa

To: Paul Engel who wrote (37729)	9/29/1998 6:33:00 PM
From: Kevin K. Spurway	Read Replies (1) \| Respond to of 1572931

Re: news.com " A similar problem was discovered with the 333-MHz Pentium II, but the problem was discovered and cured before the release of the chip. The incompatibility with the K6-2 was not discovered until recently. " " AMD has known about the flaw since the release of the 350-MHz K6-2, and has been working on a patch since then. " ________________ Looks like everything Paul has been telling us about this problem is false then. The problem isn't with the chip at all. It's just poorly written software that causes the problem to crop up. Microsoft has admitted it. So who cares? Ultimately, nobody. The fix is easy and free, and most won't ever need it. The reason that it was caught on the PII-333 and not the K6-2-350 is that at the time the PII-333 came out, Win95 OSR2 was the OS of choice. Now, it's Windows 98. Very simple. Kevin