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


To: Elmer who wrote (41927)11/19/1998 9:39:00 PM
From: Scumbria  Read Replies (2) | Respond to of 1572942
 
Elmer,

We should all demand AMD recall these bug infested processors immediately!!!!!

I had a good week at work so far. I've only had to reboot my PII/Windows NT system once (so far.)

Scumbria



To: Elmer who wrote (41927)11/19/1998 10:40:00 PM
From: Ali Chen  Read Replies (1) | Respond to of 1572942
 
350 "bug": Just downloaded the 350 patch from
hardware.pairnet.com
Just for fun I compared the old binaries with
the super-patch. Results: the two files
differ in a single byte only, at byte
location 36B5:

Old bad IOS.VxD contains code 90 (=NOP),
New patched VxD contains code 41 (=INC EAX)!

Microsoft did a really hard "job". The piece of
code actually is trying to get timer difference
before and after a 1,000,000 LOOP to itself
command, and to fix the timing problem they
incremented something. The next byte is also
NOP, so we can be sure that there is a room
for one more INC command to fix the next
"ourage" when K6 hits 600MHz...




To: Elmer who wrote (41927)11/20/1998 2:00:00 AM
From: Yousef  Read Replies (1) | Respond to of 1572942
 
Elmer,

Re: "This is an outrage!!! We should all demand AMD recall these bug
infested processors immediately!!!!!"

I would have to agree with you, Elmer.

Make It So,
Yousef (...Who Loves Intel Innovations...)