• On BNET: Give your browser a panic button
The Download Blog
advertisement
May 12, 2008 9:14 AM PDT

XP update throws some for a loop

by Ina Fried
  • Font size
  • Print
  • 20 comments

This blog was updated at 9:30 a.m. PDT with information from Microsoft about the cause of the glitch.

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 for 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.

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 at the 11th hour an incompatibility with one of its own programs.

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.

Originally posted at Beyond Binary
During her years at CNET News, Ina Fried has changed beats several times, changed genders once, and covered both of the Pirates of Silicon Valley. These days, most of her attention is focused on Microsoft. E-mail Ina.
Recent posts from The Download Blog
Tell the time and destroy the Death Star: iPhone Apps of the week
Windows Starter Kit refreshed for 2010
Big changes in Security Starter Kit 2010
Why to embrace Firefox 3.6's new-tab ethos
Sale: CoPilot Live GPS for iPhone, $19.99
Three apps we're thankful for
Mozilla issues near-final Thunderbird 3
eBay opens auction app for BlackBerry
Add a Comment (Log in or register) (20 Comments)
  • prev
  • 1
  • next
by rmva May 12, 2008 9:49 AM PDT
I am appalled that Microsoft didn't anticipate this problem. They obviously knew about it four years ago!
Reply to this comment
by wolivere May 12, 2008 10:07 AM PDT
Yes and they warned OEM's 4 years ago. I'm sorry if you don't clean up your own issues why expect others to do it for you.

See this is why you have bloated code. You can't rely on people to actually read relase notes or patch's... or in this case OEM's to even follow simple instructions.

Thus you need to code in for stupidity, which results in code bloat which results in people saying why is the code so bloated? BTW I use to run my CP?M share ware app on my Win 3.11 box why can't I run it on my XP box?? Microsoft sux
by groink_hi May 12, 2008 11:30 AM PDT
Microsoft did the due diligence in instructing the OEMs in 2004. Although you know that techs continue to improperly image PCs, you cannot expect Microsoft to address techs not following procedures. This lack of following procedures is just one of the many things PC builders continue to do, along with other things such as installing the wrong HAL.
by smokified May 13, 2008 12:41 PM PDT
Your one of those idots who does not recognize that Microsoft is actually good at making software aren't you....
by custompcmax May 12, 2008 12:08 PM PDT
Makes you question who is lining M$ pockets... Any bad press for AMD systems is killing them at the moment, and only make Intel look so much better. But, I am just speculating. M$ should have anticipated and nullified this problem, prior to rolling out the update. They are only like the biggest freaking software company in the world, they should have enough resouces to cover things like this.
Reply to this comment
by azcomicgeek May 12, 2008 12:55 PM PDT
Typical Anti-MS rhetoric, blame MS for an OEM issue. They tried to save a few bucks by mass imaging regardless of chipset and you blame MS for a problem they had no control over. I am no MS fanboy but even I can see this is an OEM/AMD issue, not MS/Intel. Force incompatible software onto a system and things are bound to go wrong when updating.
Reply to this comment
by fgsdfgdsfgdsfg May 12, 2008 1:31 PM PDT
this isn't microsoft's fault.

only a complete idiot would build a windows image on an intel based system and then install that image on a AMD system with a different motherboard and chipset and CPU.

Microsoft has been saying don't do that since windows 3.1 people.

there are some programs that let you restore images to different hardware platforms, but you have to BUY that software. Acronis snap deploy is a good example.
Reply to this comment
by Imalittleteapot May 12, 2008 5:26 PM PDT
Yes, Yes, and more Yes. I'm so glad I didn't have to post that myself.
by Tergon May 12, 2008 4:20 PM PDT
That said with all your comments but I'm going to add this helpfull piece of advice for those who are (or who have clients who are) using AMD Processors.
Windows reference dot com has advice to fix this issue.
Plz Note I have nothing to do with (employmentwise) MS, AMD, Intel, CNet or Windowsreference.com (or any one else). Knowledge is free
I couldn't post a link so
Reply to this comment
by JCPayne May 12, 2008 5:52 PM PDT
Updating windows.....

(In the words of my old C programming book....)

while(dead_horse)
beat();
Reply to this comment
by smokified May 13, 2008 12:43 PM PDT
Would you prefer that they just don't offer you updates? For the amount of money that people spend on a copy of windows, I am glad they offer full time support. Pull your head and that book out of your ass and think with both sides of your brain.
by gggg sssss May 12, 2008 6:13 PM PDT
Told them not to buy AMD
Reply to this comment
by TechieTrekkie May 12, 2008 7:29 PM PDT
Reason #497032 to get Linux.
Reply to this comment
by smokified May 13, 2008 12:43 PM PDT
Except for if you plan on using your computer.
by rpdwpb May 13, 2008 4:22 AM PDT
Reason to buy apple!!! This is completely MS's fault. Their Service Packs are HUGH and could easily be coded to tell the difference between systems, it's just MS passively ignoring the tangled mesh that is their defective Windows product line.

** MS Software is the only product you will intentionally plan on buying defective **
Reply to this comment
by ncaissie May 13, 2008 4:47 AM PDT
Apple blows.
They are for the retard useres that can't take care of their own hardware and need the OS to do everything for them. It's so locked down to prevent the retard user from messing things up.
by smokified May 13, 2008 12:46 PM PDT
Are you serious? Is this the only article you have read this year? Leapord is the most insecure operating system out there. MS products are constantly updated with security updates and fixes. Doesn't Apple release a new version of OSX more often than MS releases a service pack?
by v0dkacomradwe May 13, 2008 5:12 AM PDT
It amazes me that vendors could not work better together to resolve these kinds of things before SP3 got dist'ed to the public. This is a reason to expect, no DEMAND, quality and respect from companies. In my opinion, these days if you aren't a "shareholder" your opinion likely doesn't mean squat. Buying and using (and even referring?) a company's products, software and hardware, no matter how much you spend, isn't good enough apparently. Although this wasn't all Microsoft's fault, enough of the blame IS theirs! It's also a sad reminder for those of us who are or were AMD fans (like me) that AMD is slipping further into the abyss of irrelevance (say it ain't so!).

And NO! Linux and Apple fan boys and girls, it's not a reason to go out and get Linux or Mac OS. Windows XP is a good, mature OS (notice I didn't say Microsoft is a "great" company, just talking about the OS...so we are clear on that!). If Windows and Microsoft weren't around, believe me, the mega corps standing behind Linux might be "prone" to this kind of corner cutting too (YES there is BIG MEGA CORP MONEY behind Linux and Mac too, why is that point never mentioned!??!) It is popular to bash Microsoft, I am not going to argue that. However, that's all it amounts too...bashing just because it's the "thing to do" (reminds me of peer pressure high school kids experience!). Drop the Linux 'tude and the Apple fanboy arrogance and please stop acting like a bunch of politicians and salespeople in the face of real technical issues (oh and when is Apple or the companies backing Linux ever going to "pay" you for your promotion of their wares? Here's a hint...NEVER!!). I don't seem to ever remember hearing that the Mac and Linux OS'es, or any systems that run them, were perfect and flawless in every regard (I know, I've used them all!) Nuff said.

People should use whatever OS is appropriate for their needs! Manufacturers and vendors need to get their s^%t together for the good of their customer base! Period.
Reply to this comment
by KSman01 May 13, 2008 8:44 AM PDT
The SP3 install knows what the processor is. It could check for some known conflicts. Then it could issue warnings, instructions and abort, or rename the offending files and continue. Pointing fingers at system manufactures is not of much comfort when one's system does not work.
Reply to this comment
by 1evr May 16, 2008 6:00 AM PDT
How many AMD or MS bashers did not read or do not understand the point???

".........OEMs improperly placing a Windows XP image created for an for Intel-based computer onto machines with non-Intel chipsets"

OEM's such as HP did the dirty on consumers.
Reply to this comment
(20 Comments)
  • prev
  • 1
  • next

Search Download Blog posts

advertisement
Click Here

About The Download Blog

Download.com editors cover the world of downloadable software and beyond.

Add this feed to your online news reader

The Download Blog topics