Owners of some AMD-based computers are finding that the move to Windows XP Service Pack 3 has sent their systems into an endless reboot cycle.
"While the root cause of this issue is complex, it results from OEMs improperly placing a Windows XP image created for an Intel-based computer onto machines with non-Intel chipsets," Microsoft said in a statement. "Microsoft issued guidance to OEMs advising them to only load Windows XP images onto like hardware in 2004."
The issue was noted late last week on Microsoft forums and by others, including ZDNet's Mary Jo Foley. Those with a problem are encouraged to contact Microsoft's customer support.
Want to know more?
For all the latest news, analysis and opinion on Windows, click here
The reboot cycle glitch is the latest hiccup for Microsoft with the service pack update. The company had to delay the release of the XP update after discovering an incompatibility with one of its own programs at the 11th hour.
With that issue, customers running Microsoft's Dynamics Retail Management System could face data loss if they run that program in conjunction with SP3.
After delaying the release of XP SP3 because of the issue, Microsoft finally made the OS update available last week, after creating a filter to ensure that those running Dynamics RMS did not get offered XP SP3.
just what microsoft is doing i don't know.
i got sp3 without asking for it and got a totally crippled computer.
yes i am using a dual core amd.
there was not way i could fix this problem. i had to do a total new install after a slow format of my drive just to make sure i was totally clean.
luckily i had backups for everything.
to be honest this has just about finished me with microsoft.
linux is looking better and better.
i am sure mirosoft is trying to commit suicide within the software business, after the vista rubbish i went back to xp pro and what do i get sp3.