|
It depends on how you look at it. The root cause of the problem are"Unsupported configuration"? Since when did AMD become unsupported? In this day of plug and play, Microsoft creates software that can't even tell what kind of CPU it is running on, thereby making it the responsibility of the vendor to install the right version, and you say this is the vendor's fault.
OEMs that used an unsupported configuration. Earlier, that unsupported
configuration worked anyway - now it doesn't. The latter can surely be
fixed, and probably will.
But there is *no* way you can QA for every lunatic out there that uses
software in an unsupported manner.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.