Windows XP SP3: Good for many but not for all
Last time, in my column titled "Updates to the left of me, downgrades to
the right, here I am, stuck in the middle with you-know-who," we talked about the imminent arrival of Windows XP Service Pack 3. I wondered who would be more excited about it, people currently using XP SP2 or frustrated Vista users begging for a downgrade.
Today, we know one thing for certain: if your customers are running certain Hewlett-Packard PCs with an AMD processor, head for the hills. Or, at the very least, don't install the update. Too late? Bummer.
You'll recall that at the last moment, the Softies decided to hold off for a few days while they fixed a recently discovered incompatibility (that means "problem") with Microsoft Dynamics Retail Management System (RMS).
The same issue applied to Vista SP1, which also was delayed.
That may have been fixed, but no doubt you've been reading about the problem (that means "incompatibility") with AMD on HP.
According to reports, some HP systems equipped with AMD's Athlon processor reboot endlessly, not a good thing. Some reports go on to say the problem is related to XP disk images made on an Intel-based system subsequently run on an AMD machine.
This isn't the right time to point any fingers toward the Pacific Northwest. But this is the time to get the information you need to either avoid the problem in the first place, or address it if you've started receiving phone calls from unhappy customers. Thus, I'll be brief.
The information nexus for the woes is turning out to be the blog of Jesper Johansson, a former Microsoft security guru and current Microsoft MVP (Most Valuable Professional). His first piece of advice is to stay calm and not overreact by reformatting and reinstalling everything. The blog is quite lengthy and discusses a conflict between intelppm.sys, used for power management on Intel-based systems, and amdk8.sys, the AMD equivalent.
There's this nugget from Johansson: "Ordinarily, having intelppm.sys running on an AMD-based computer appears to cause no problems. However, on the first reboot after a service pack installation, the computer either fails to boot or crashes with a STOP error code of 0x0000007e." I suggest you read the blog for details; there are links to many other resources.
Microsoft TechNet has a discussion forum where the issue is being discussed.
Hewlett-Packard seems to have stepped up to the plate with sp37394.exe, a 1.85MB utility that it says solves the issue. Alas, there's one major problem: HP says "you must install this update prior to applying Windows XP SP3 update." That's a bit like going to the hospital and telling the emergency room nurse that you're going to break your arm tomorrow. HP does not discuss what to do if you've already installed SP3. Nevertheless, you can download the utility here.
As for the AMD Web site, I couldn't find anything relevant after 15 minutes of searching. If anything is there, it's well hidden.
Lastly, Microsoft itself has posted a Knowledge Base article stepping through the process of removing XP SP3 altogether.
It all made me think back to what may have been the most stable PC operating system of them all, MS-DOS 2.1. Those were the days.
ITworld.com
Build your tech library with our book giveaways.
Windows PowerShell 2.0 Unleashed
By Tyson Kopczynski, Pete Handley, Marco Shaw; Published by Sams
Windows PowerShell Unleashed will not only give you deep mastery over PowerShell but also a greater understanding of the features being introduced in PowerShell 2.0–and show you how to use it to solve your challenges in your production environment. Enter now!

Ubuntu Server Administration
By Michael Jang; Published by McGraw-Hill Osborne Media
Realize a dynamic, stable, and secure Ubuntu Server environment with expert guidance, tips, and techniques from a Linux professional. Ubuntu Server Administration covers every facet of system management -- from users and file systems to performance tuning and troubleshooting. Enter now!









XP SP3
I have an AMD processor-based desktop system that I built myself. It is not an HP or Dell or other OEM kit. I am running a stable XP SP2 and tried to install SP3. BANG!, I ran into the endless reboot problem. Luckily I had saved the ghost image prior to this irresponsible action (installing more MS SW), so I was able to recover. As such this issue is NOT only applicable to HP as it is suggested above.I tried to do this in August so THERE WAS NO EXCUSE FOR MS NOT TO POST A BIG RED GLOWING WARNING ON THE SP3 DOWNLOAD SITE about this issue.
Not doing so is simply irresponsible and adds to the perception that MS simly does not give *&%$ about its users.
I mean, how hard can it be to put a simple line in bold next to the "download" button, saying that if you have an AMD processor, please first install patch xyz?
...I can't wait for Linux to be just a bit more user friendly and then it's bye bye MS...