AMD doesn't say much when you ask them questions, but the correspondence I have been having with them over the last week is very interesting, and very important for all of the Windows 2000, and AMD Athlon XP users.
The emails speak for themselves, but to make it an easier read I have Highlighted the most important, and interesting bits.
Please take the time to read this, especially the last two emails.
My first email to them, about the supposed problem with Athlon processors, and AGP video cards in Windows 2000, and Windows XP (Later AMD informed me that the issue is not present in Windows XP, only in Windows 2000):
Which AMD replied to in the following email:
I replied with another email, and some more questions about this issue, and some other stuff (some of which I shouldn't have bothered to ask - because we all know that AMD would never answer them):
The answer I really wanted was whether or not the patch for Athlon processors and the AGP issue was included in any Windows 2000 service paks. I shouldn't have asked about steppings, locked processors, and powernow, because AMD doesn't like to put anything about those topics in writing.
This response only answered one of my questions (the Thoroughbred one). Although unrelated to the AGP fix, Their answer to my Thoroughbred question implies that some Thoroughbreds are still being manufactured, just not in full-scale quantities. I sent them another email to clear up the AGP issue in Windows 2000:
To which I received an answer:
So, why isn't this fix - which causes crashing, and freezing in Windows 2000 when you use any AGP video card, with any driver revisions, with any Athlon processor - not inculded in any of Microsoft's service paks for Windows 2000?
What is going on here? Has this simply been overlooked? This is a fairly serious issue, and makes me wonder what other known problems are floating about.
If you use Windows 2000, and haven't installed the registry fix, I suggest you do so immediately. The registry patch is linked below.
CLICK ON THIS TEXT IF YOU USE WINDOWS 2000
I would appreciate any comments and thoughts about this.
The emails speak for themselves, but to make it an easier read I have Highlighted the most important, and interesting bits.
Please take the time to read this, especially the last two emails.
My first email to them, about the supposed problem with Athlon processors, and AGP video cards in Windows 2000, and Windows XP (Later AMD informed me that the issue is not present in Windows XP, only in Windows 2000):
Email from felinusz to AMD
It has recently come to my attention that some AMD processors have a compatibiltiy issue with Windows XP (NOTE: AMD LATER STATED THAT THE ISSUE IS NOT PRESENT IN WINDOWS XP, ONLY IN WINDOWS 2000), and Windows 2000 where applications that use an AGP graphics adaptor will freeze, or exhibit instability. Here, on your website - http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_756_759^871^2367,00.html - is a registry change for Windows 2000 which fixes the issue. This error, and the need to install the Windows registry fix, has only been *confirmed* by you to be present
with the use of Nvidia GeForce 256 and Matrox G400 video cards. Myself,
and several of my associates, are wondering if this problem is known
to be present in machines using other types of video adaptors besides
the ones you have listed (GeForce 256, Matrox G400 AGP adaptors);
specifically newer AGP graphics cards. Thank you for your time, I appreciate
your help, and advice.
Which AMD replied to in the following email:
Email from AMD to felinusz
Thank you for contacting AMD's Technical Service Center. This
issue was really between how the OS and the processor were handling
AGP Gart table paging. I am not aware of it being tied to a specific
video card but more between the OS and processor. The registry changes how the paging between memory, OS and Processor is handled. If you are running Win XP and NOT Win 2K, then you should not need the registry patch. Likewise, you should be able to use any video card (old or new) without any issues or corrupted data. If you are running Win 2K, then simply install the patch and you should be fine with any video card. If you are running Linux, then simply compile with the nopentium switch and you should be in good shape as well. Hope this helps. If you have any other questions, please feel free to contact me.
Happy Holidays,
Jay Taylor
Supervisor / Apps Engineer
AMD Technical Service Center
I replied with another email, and some more questions about this issue, and some other stuff (some of which I shouldn't have bothered to ask - because we all know that AMD would never answer them):
Email from felinusz to AMD
Thank you for your quick response Jay, your help is much appreciated
by myself and my colleagues.
I do actually have another couple of quick questions for you
regarding this issue, and AMD processors in general.
Is the fix for this issue applicable for all video cards, using all
new and old video card drivers? Is this registry fix distributed
in any of the Windows 2000 Service packs from Microsoft?
Unrelated to the AGP issue, I am wondering about the supposed
multiplier lock on new Duron Applebred, and Mobile
Athlon XP-M Barton core processors. Are the desktop Duron Applebred
processors being produced with a hard-multiplier
lock, like the new desktop Athlon XP Bartons, and the last
Thoroughbred Athlon processors? Are the mobile Barton
2400+ processors, and up, being produced with a multiplier lock? How
does a multiplier lock incorporated into a mobile
Athlon procesors affect the Powernow! feature that mobile Athlon
processors incoporate? If they are, indeed, being
produced with a multiplier lock, I am wondering if you can tell me
which production week was the first to have the lock
incorporated?
Lastly, I am wondering if the Thoroughbred core line of Athlon XP
Desktop processors has been discontinued.
The answer I really wanted was whether or not the patch for Athlon processors and the AGP issue was included in any Windows 2000 service paks. I shouldn't have asked about steppings, locked processors, and powernow, because AMD doesn't like to put anything about those topics in writing.
Email from AMD to felinusz
Thank you for contacting AMD's Technical Service Center. Since the
AGP issue is between the AMD AGP GART driver and the OS, the patch is
required regardless of what video card and drivers you are using.
Unfortunately I we cannot provide stepping information, or details on
work week changes. This would also include which processors have
locked clock multipliers and which do not. We apologize for not being
able to provide more information.
Manufacturing has moved on to model 10 which is still based on the
.13 micron manufacturing process. Model 8 may still be manufactured
at certain speeds, but is not in full scale production.
Hope this helps. If you have any other questions, please feel free
to contact me.
Regards,
Ryan Gardner
CPU Specialist
AMD TSC
This response only answered one of my questions (the Thoroughbred one). Although unrelated to the AGP fix, Their answer to my Thoroughbred question implies that some Thoroughbreds are still being manufactured, just not in full-scale quantities. I sent them another email to clear up the AGP issue in Windows 2000:
Email from felinusz to AMD
Thanks for the quick, and helpful, response. I am still wondering if the registry patch for this problem with Athlon processors, AGP video adapters,and Windows 2000 is included within any of Microsoft's Windows 2000 service paks.
Thank you for your help, and time.
To which I received an answer:
Email from AMD to felinusz
No, it is not included in any service packs unfortunately.
Regards,
Ryan
So, why isn't this fix - which causes crashing, and freezing in Windows 2000 when you use any AGP video card, with any driver revisions, with any Athlon processor - not inculded in any of Microsoft's service paks for Windows 2000?
What is going on here? Has this simply been overlooked? This is a fairly serious issue, and makes me wonder what other known problems are floating about.
If you use Windows 2000, and haven't installed the registry fix, I suggest you do so immediately. The registry patch is linked below.
CLICK ON THIS TEXT IF YOU USE WINDOWS 2000
I would appreciate any comments and thoughts about this.
Last edited: