7 ms·
>"It was somewhat unfortunate that this was called an “AMD fix” (the file containing the solution was called AMDK6UPD.EXE), even though Microsoft was clear that
by TwoBit 6y ago
>"It was somewhat unfortunate that this was called an “AMD fix” (the file containing the solution was called AMDK6UPD.EXE), even though Microsoft was clear that this was not a problem in AMD CPUs but rather in their own code."
I'll bet the AMD name was suggested by producers and/or management at the protest of engineering, with the argument that the public knows this as an AMD problem and so it's better to call it that regardless of the technical reality. I've seen this logic many times in my career and do understand there's some rationale to it.
- Nextgrid 6y agoCould it be simply because since the bug primarily affected AMD CPUs at the time it would make it easier for everyone if the update was called the “AMD update” as opposed to some cryptic name like “network stack delay loop update”?
- Lammy 6y agoI figure it's for the same Microsoft×Intel mutual-back-scratching reason that made Microsoft try to charge $35 for the fix: https://www.theregister.com/1998/11/26/amd_posts_windows_95_k62/ https://www.theregister.com/1998/11/26/amd_posts_windows_95_...
- WalterGR 6y agoAh, yes, The Register. Faced with the Great Satan of Software's apparent refusal to admit its mistake and eliminate the charge, AMD has made the fix available from its Web site free of charge.
- mjevans 6y ago"Fast PC support"