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: Kevin K. Spurway who wrote (42028)	11/20/1998 11:43:00 PM
From: J. Plesha	Read Replies (1) \| Respond to of 1574852

I'll give the reporter the benefit of the doubt. Just assume its a newby who decided to cruise on the internet and found the new post on the amd sight. The "bug" as I recall is a timing loop in win 95 that has been known about for some time. Not by me before the conference call. But it did explain why a 3com ethernet driver did the same thing to my machine. I solved it by installing a lower rev of win 95. Anyway Jerry said that the effect was very minimal. The people who would buy just the processor and not the system were the ones mostly at risk. I just took the glitch to mean that the amd chip just ran too damn fast. :-) By the way just to be fair I had a PII 233 chip that did the same thing as described in the article. Joe P.