Dopa: don't worry, just enable windowsupdate and it's gonna force itself down your throat sooner or later.
Seems like most got it working well. Funny, considering when i tried to install it on the other compy in the house out of curiosity later today, it screwed up too. I blame MS.
' Wrote:So it tried to force itself on me through auto-update today, I thought "what the heck, it can't be a bad thing". Little did I know that I would spend the next three hours rolling back all the changes after the very installation process failed, and in doing so literally destroyed the OS. When I read up on the beta, it appears SP3 had a ton of bugs in it, quite severe too like killing the windows installation on a system with an AMD processor and a specific, popular motherboard model.
Anyone else get this sort of weirdness, or am I just doing it wrong?
XP sp3 works great when properly installed.
BTW a good sysadmin knows how to completely disable all communications with microsoft and install updates when they are ready, thats where most of the problems come in.
Heh, a "sysadmin" only applies when you're running servers or dedicated machines. We're talking about the regular user here. How do I exactly "properly install" a MS product? Click "next" in the installation in a very specific timing?:PSeriously mate, SP3 is out of beta for two months now, they released it on windows update, it should work as close to perfect as possible.
But it doesn't. The installer itself screwed up two computers, go figure. Therefore, I blame MS. If they make it ultra user friendly, they should make it work flawlessly too.
I updated SP3 to a granny's comp without problems. It's my old AMD Opteron rig that she uses for Skype.
I've heard about good things and bad things. I've got a hunch that SP3 goes neatly into pretty clean Windows installation (not much new programs etc.), but to a tweaked and customized and full of stuff it can be a nightmare.