So far, so good

[A Nonnie Moose]

Installed SP3 from CD last night; installation took about 20 minutes, no
burps during installation, restarted smoothly.

After installation, ran the computer for several hours -- opened and used
every application, no problems.

 

[Big_Al]

A Nonnie Moose said this on 2/21/2009 7:35 AM:

Installed SP3 from CD last night; installation took about 20 minutes, no
burps during installation, restarted smoothly.

After installation, ran the computer for several hours -- opened and used
every application, no problems.

Just like its supposed to do. Congrats.

 

[Pegasus \(MVP\)]

Installed SP3 from CD last night; installation took about 20 minutes, no
burps during installation, restarted smoothly.

After installation, ran the computer for several hours -- opened and used
every application, no problems.

This must be the "Good News Channel".

 

[olfart]

Installed SP3 from CD last night; installation took about 20 minutes, no
burps during installation, restarted smoothly.

After installation, ran the computer for several hours -- opened and used
every application, no problems.

been running SP3 for months on 4 different machines with no problems at all.
Don't know why everyone seems to be so gunshy of SP3

 

[Big_Al]

olfart said this on 2/21/2009 8:44 AM:

been running SP3 for months on 4 different machines with no problems at all.
Don't know why everyone seems to be so gunshy of SP3

They are gun shy because things go boom. Believe me, I'm not trying to
defend MS, but since XP is so easy to 'play with' and there are oh so
many cute little tools out there to help 'fix' your pc and registry,
when you go to install SP3 its no wonder things go boom. I'd say it
mostly the users fault but.... in MS defense, I write software and I
know for a fact it's impossible to second guess what users will or can
do, they are always one step ahead of you, and I don't mean on the
intelligent side of things. So no wonder SP3 fails now and then.

 

[Bruce Chambers]

Installed SP3 from CD last night; installation took about 20 minutes, no
burps during installation, restarted smoothly.

After installation, ran the computer for several hours -- opened and used
every application, no problems.

As would be expected.

--

Bruce Chambers

Help us help you:


http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

 

[PA Bear [MS MVP]]

Always reply to your original thread, please.

 

[Twayne]

If things do go wrong with SP3 can restore get rid of it and make
things the way they were ?

http://www.wowway.com/~helmsman/

Not in the sense you're probably thinking, but SP3 will create an
uninstall program in the C:\windows folder, just like all the updates
do. You can run that and go back to SP2 or SP1, whichever you have
installed prior to SP3.

I've found that with a couple of exceptions stated on the MS site abuot
SP3, most problems with it are failure of people to bother to read the
details of how to install it. They're right there on the MS site with a
step by step process of how to be sure you're ready. Mainly it consists
of making sure you have no malware and things are working right to begin
with. A worthwhile read. I hesitated too but had no problems in the
end. There ARE a couple of specific things on the site to be aware of;
give it a read. Just look for SP3 install.

Cheers,

Twayne

 

[Frank Slootweg]

If things do go wrong with SP3 can restore get rid of it and make
things the way they were ?

The point is that for users with *one* machine, if they lose the
machine, they also lose access to *information* to (try to) *fix* the
machine. Catch-22.

 

[Twayne]

The point is that for users with *one* machine, if they lose the
machine, they also lose access to *information* to (try to) *fix* the
machine. Catch-22.

Not sure I understand that post; that's precisely the reason backup
strategies exist; so that the information won't be lost, regardless of
the situation that causes the problem/s. Whether it's one or a hundred
machines, the stratagies can all be the same.

 

[Frank Slootweg]

Not sure I understand that post; that's precisely the reason backup
strategies exist; so that the information won't be lost, regardless of
the situation that causes the problem/s. Whether it's one or a hundred
machines, the stratagies can all be the same.

Sorry for my somewhat sloppy/ambiguous wording.

I'm referring to how-to information which is needed to *do* the
recovery. For example if the system does not boot anymore (and you can't
easily fix it), you want to have a look at information sources which can
help you fix the problem. But most of the time these information sources
are either on the (dead) computer itself - catch-22 - or on the web -
catch-22, because you can't access the web because your computer is
dead.

OTOH, if you have a dead system *and* another working system, you can
use the working system to access the how-to information (whether from
backup or web).

I hope this explains what I was getting at.