Friday, May 30, 2008

Windows XP Service Pack 3
(could the flaws in Windows XP SP3 be a push to Vista?
Not since Windows NT Service pack 2 do I remember so many problems with a Service Pack from Microsoft. So the question is: Are these intentional, or just another failure of quality control on the part of Microsoft? I got to admit, that I have become pretty complacent with Microsoft's Service Packs. They have been pretty reliable since the Service Pack 2 that was released for Windows NT 4. That was a pretty bad one, and they had to quickly release service pack 3 to fix all the problems. Now I think it would be a stretch to say that the Borg (MS) would intentionally break the XP machines to try to push people to Vista which I think is the biggest blob since Windows ME. I had Vista on my work PC because I have to try to stay ahead of the curve, but at home I was no way going to go away from XP. I mean when I go home I sure don't want the problems Vista could produce and was waiting with great anxiousness for another service pack for XP which would allow me to stretch the use of XP farther into the future. By doing this I would ride out the Vista Blast and see if Microsoft would come up with something better. So when problems started arising with XP SP3 I thought, "how convenient?" I got to say that I applied SP3 to my home PC, my laptop, and another 2 computers at work and did not see some of the more horrendous problems experienced by others, but after learning that it could produce problems across a very dissimilar install base in our company, I told my assistant not to approve it in the Windows Update Server. I also put the Vista Service Pack 1 on my work computer, and that seem to have helped a bit, especially on performance, so, with a better Vista because of SP 1 and a worse XP because SP 3, the conspiracy theorist in me starts wondering - nah, I am just imagining things! Delco

3 comments:

Anonymous said...

As a fellow admin i have had similar problems. However, I have traced all of them not to Microsoft but to Symantec. Specifically the home version, Norton (included in 360). It stops the installer from removing place holder registry keys and as result Windows fails at enumerating certain things like network devices, my computer, etc. A note: symantec endpoint, McAfee, and AVG don't seem to do this. To install safely, simply disable auto-protect.

A note, other problems have been traced to AMD and Intel drivers that do things that they're not supposed to.

Before you go off blaming Microsoft for all your problems, remember: there are a lot of drivers and software that control how your system works at a fundamental level that Microsoft has nothing to do with. Its not Microsoft's fault that Intel, AMD, Symantec, et al didn't test their software against the release cannidate and release updates.

Anonymous said...

after hearing for so long how bad vista is, i was glad i had xp.
When i did get a new computer it had vista on it.
love vista, it works great.

Delco said...

Point well taken. Thank you.