( OT) XP Service Pack Crashes
 

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

"Diverd4777" wrote in message
...
All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

Workin fine for me.

All:

PRIOR to installing the new XP Service pack
Go to Internet explorer
go to tools
go to Internet options
Delete cookies
delete files
click OK

Sweep your machine for Spyware ( spysweeper)

THEN install

Diverd4777 wrote:

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

Did you tell Chandler7600 and Soames123 about this apparent problem?

dxAce
Spotter of NYC 'Tards

In article , "MnMikew"
writes:


Advise against loading curent XP Service pack. ( 8/19/2004)

( Just got off 'phone with Microsoft )

UNTIL

You remove Spyware ( Spysweeper recommended
looks like spyware was the problem )

Go to IE Explorer
delete files
Delete Cookies..

do a Disk Clean up

THEN try the install

On Fri, 20 Aug 2004 15:31:30 +0000, Diverd4777 wrote:

All:

PRIOR to installing the new XP Service pack
Go to Internet explorer
go to tools
go to Internet options
Delete cookies
delete files
click OK

Sweep your machine for Spyware ( spysweeper)

THEN install


That last line, you forgot a word....Linux.

In article , Tom Randy
writes:

Subject: ( OT) XP Service Pack Crashes ( revised)
From: Tom Randy
Date: Fri, 20 Aug 2004 22:27:29 GMT

On Fri, 20 Aug 2004 15:31:30 +0000, Diverd4777 wrote:

All:

PRIOR to installing the new XP Service pack
Go to Internet explorer
go to tools
go to Internet options
Delete cookies
delete files
click OK

Sweep your machine for Spyware ( spysweeper)

THEN install


That last line, you forgot a word....Linux.


Right , Linux ( Sigh...)

- Looks like spyware & something else totally freeze the system if you have
multiple browser pages up & flip between them, loading them as you go..
And this is only on an intermittant basis..
Their " crash sendback" doesn't work on this either..

Spent 2 hours with Microsoft, ( yes, people in the U.S. ) testing every
configuration ;
Sometimes it would freeze, requiring a full power cycle.

Sometimes 2-3 times in 15 minurtes, sometimes hours between freeze-ups.

deleted cookies, files,
ran Norton,
Ran Spysweeper, Spykiller2004, Spybot search & Destroy

Downloaded a newer copy of Mozilla..
treating it gentle..
- Let see...

Dan

Diverd4777 wrote:
In article , Tom Randy
writes:


Subject: ( OT) XP Service Pack Crashes ( revised)
From: Tom Randy
Date: Fri, 20 Aug 2004 22:27:29 GMT

On Fri, 20 Aug 2004 15:31:30 +0000, Diverd4777 wrote:


All:

PRIOR to installing the new XP Service pack
Go to Internet explorer
go to tools
go to Internet options
Delete cookies
delete files
click OK

Sweep your machine for Spyware ( spysweeper)

THEN install


That last line, you forgot a word....Linux.



Right , Linux ( Sigh...)

- Looks like spyware & something else totally freeze the system if you have
multiple browser pages up & flip between them, loading them as you go..
And this is only on an intermittant basis..
Their " crash sendback" doesn't work on this either..

Spent 2 hours with Microsoft, ( yes, people in the U.S. ) testing every
configuration ;
Sometimes it would freeze, requiring a full power cycle.

Sometimes 2-3 times in 15 minurtes, sometimes hours between freeze-ups.

deleted cookies, files,
ran Norton,
Ran Spysweeper, Spykiller2004, Spybot search & Destroy

Downloaded a newer copy of Mozilla..
treating it gentle..
- Let see...

Dan

Try using Mozilla Firefox. The extensions alone are a good reason to
switch. All that pesky security stuff comes second...

e

Dan wrote:

On 20 Aug 2004 12:05:50 GMT, (Diverd4777) wrote:

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

Nonsense. I've installed it on 5 machines here at home and 3 at work.
SP2 is nice, has some nice new features, and works fine.

Kim Komando mentioned some apparent problems with the Service Pack on her
program this morning.

She mentioned something about it being in her newsletter or on her site.

www.komando.com

dxAce

"dxAce" wrote in message
...


Dan wrote:

On 20 Aug 2004 12:05:50 GMT, (Diverd4777) wrote:

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

Nonsense. I've installed it on 5 machines here at home and 3 at work.
SP2 is nice, has some nice new features, and works fine.

Kim Komando mentioned some apparent problems with the Service Pack on her
program this morning.

She mentioned something about it being in her newsletter or on her site.

www.komando.com

dxAce

Service pack 1 looked for known pirated keys, and disabled systems it found
with them. It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

Beyond that, some programs use "illegal" entry-points into various WinXP
processes, and these hooks may have changed with the new service pack.
That's why a lot of malware and spyware makes it crash -- some of those
programs actually replace MS system files with altered ones.

-- Stinger

"Dan" wrote in message
...
On Sat, 21 Aug 2004 12:07:29 -0500, "Stinger"
wrote:



Service pack 1 looked for known pirated keys, and disabled systems it
found
with them.

Not true. Nothing was "disabled". It just would not install SP1.
The system would continue to run. You could then change your key to
an "unknown pirated key", and then install SP1.

It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

No, in fact quite the opposite. Microsoft has taken the other
approach, as they realized it's better to get *all* systems patched,
legal or not.

I'll leave it as an exercise for you to figure out how I know these
things......... :-).

Dan


Your mileage may vary -- I know it killed the "FCKW -- " key, and had some
friends that had their computers "hung up" in the process of installing the
service pack who had to use a boot disk to recover files.

As for SP2, that was speculation, as we're "legal."

-- Stinger

In article , "Stinger"
writes:



Service pack 1 looked for known pirated keys, and disabled systems it
found
with them.

Not true. Nothing was "disabled". It just would not install SP1.
The system would continue to run. You could then change your key to
an "unknown pirated key", and then install SP1.

It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

No, in fact quite the opposite. Microsoft has taken the other
approach, as they realized it's better to get *all* systems patched,
legal or not.

I'll leave it as an exercise for you to figure out how I know these
things......... :-).

Dan


Your mileage may vary -- I know it killed the "FCKW -- " key, and had some
friends that had their computers "hung up" in the process of installing the
service pack who had to use a boot disk to recover files.

As for SP2, that was speculation, as we're "legal."

-- Stinger

SP 2 has a sensitve stomach , I let it idle in the driveway, it's fine
- maybe down to the strip mall for a quart of milk.

Take it out on the freeway and the sucker'll
Hurl all over . . .
locking up your system & requiring a hard boot.
NOt as rugged as its predecessor

- Not reliable as shipped, IMHO

"Stinger" wrote in message
...

Service pack 1 looked for known pirated keys, and disabled systems it
found
with them. It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

Beyond that, some programs use "illegal" entry-points into various WinXP
processes, and these hooks may have changed with the new service pack.
That's why a lot of malware and spyware makes it crash -- some of those
programs actually replace MS system files with altered ones.

-- Stinger

True and accurate on all the above. Their "service pack" is
nothing more than MS usual games to screw people out
of more $$$ in the long run .

On Fri, 20 Aug 2004 06:05 am -0600 UTC, Diverd4777
posted: %MM

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

All the more reason to not run Windo$e. If I can install and run Linux
anyone can.

Or maybe more fairly, if you can run a shortwave radio, you can probably run
Linux on most standard equipment (that has not been specifically
manufactured to run MS's system and nothing else). Suggest taking a look
at Red Hat, Mepis or Xandros Linux. Crash free, cheap or free, and no
security issues.

On Sun, 22 Aug 2004 21:13:57 -0600, uncle arnie wrote:

On Fri, 20 Aug 2004 06:05 am -0600 UTC, Diverd4777
posted: %MM

All:

Advise against loading curent XP Service pack. ( 8/19/2004)

It makes the machine unstable, causing repeated hard freezes
requiring power off / On

Do a google search for more info

Spread the word if you think this is important

All the more reason to not run Windo$e. If I can install and run Linux
anyone can.

Or maybe more fairly, if you can run a shortwave radio, you can probably run
Linux on most standard equipment (that has not been specifically
manufactured to run MS's system and nothing else). Suggest taking a look
at Red Hat, Mepis or Xandros Linux. Crash free, cheap or free, and no
security issues.


Agreed! Suse 9.1 here!

"Diverd4777" wrote in message
...
In article , "Stinger"
writes:



Service pack 1 looked for known pirated keys, and disabled systems it
found
with them.

Not true. Nothing was "disabled". It just would not install SP1.
The system would continue to run. You could then change your key to
an "unknown pirated key", and then install SP1.

It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

No, in fact quite the opposite. Microsoft has taken the other
approach, as they realized it's better to get *all* systems patched,
legal or not.

I'll leave it as an exercise for you to figure out how I know these
things......... :-).

Dan


Your mileage may vary -- I know it killed the "FCKW -- " key, and had
some
friends that had their computers "hung up" in the process of installing
the
service pack who had to use a boot disk to recover files.

As for SP2, that was speculation, as we're "legal."

-- Stinger

SP 2 has a sensitve stomach , I let it idle in the driveway, it's fine
- maybe down to the strip mall for a quart of milk.

Take it out on the freeway and the sucker'll
Hurl all over . . .
locking up your system & requiring a hard boot.
NOt as rugged as its predecessor

- Not reliable as shipped, IMHO

I have it on dozens of machines now without a glitch. Must be you.

In article , "MnMikew"
writes:

Subject: ( OT) XP Service Pack Doesn't Crash
From: "MnMikew"
Date: Tue, 24 Aug 2004 14:22:21 -0500


"Diverd4777" wrote in message
...
In article , "Stinger"
writes:



Service pack 1 looked for known pirated keys, and disabled systems it
found
with them.

Not true. Nothing was "disabled". It just would not install SP1.
The system would continue to run. You could then change your key to
an "unknown pirated key", and then install SP1.

It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is bogus.

No, in fact quite the opposite. Microsoft has taken the other
approach, as they realized it's better to get *all* systems patched,
legal or not.

I'll leave it as an exercise for you to figure out how I know these
things......... :-).

Dan


Your mileage may vary -- I know it killed the "FCKW -- " key, and had
some
friends that had their computers "hung up" in the process of installing
the
service pack who had to use a boot disk to recover files.

As for SP2, that was speculation, as we're "legal."

-- Stinger

SP 2 has a sensitve stomach , I let it idle in the driveway, it's fine
- maybe down to the strip mall for a quart of milk.

Take it out on the freeway and the sucker'll
Hurl all over . . .
locking up your system & requiring a hard boot.
NOt as rugged as its predecessor

- Not reliable as shipped, IMHO

I have it on dozens of machines now without a glitch. Must be you.


Mike:

I went to a DP seminar today; Unofficial reports are they're 200 programs that
don't work in it;

I am Not easy on software, and can usually find bugs .

This one is an intermittant. even harder to track down

Ran system tools, Norton utilities,
deleted files, cookies,
- Still crashed..

Downloaded / Installed new copies of Mozilla, used three different spyware
scanners,
Tore out a bunch of stuff.

On a non-vital machine, Try popping open 6 sessions of explorer, and quickly go
in bringin up different web pages on each one .

This used to work flawlessly on SP1; on SP2 it tempermental..

As I said, Your mileage may vary.

Dan

"Diverd4777" wrote in message
...
In article , "MnMikew"
writes:

Subject: ( OT) XP Service Pack Doesn't Crash
From: "MnMikew"
Date: Tue, 24 Aug 2004 14:22:21 -0500


"Diverd4777" wrote in message
...
In article , "Stinger"
writes:



Service pack 1 looked for known pirated keys, and disabled systems
it
found
with them.

Not true. Nothing was "disabled". It just would not install SP1.
The system would continue to run. You could then change your key to
an "unknown pirated key", and then install SP1.

It's very likely SP2 does this as well, and is probably more
sophisticated at determining whether or not a serial number is
bogus.

No, in fact quite the opposite. Microsoft has taken the other
approach, as they realized it's better to get *all* systems patched,
legal or not.

I'll leave it as an exercise for you to figure out how I know these
things......... :-).

Dan


Your mileage may vary -- I know it killed the "FCKW -- " key, and had
some
friends that had their computers "hung up" in the process of
installing
the
service pack who had to use a boot disk to recover files.

As for SP2, that was speculation, as we're "legal."

-- Stinger

SP 2 has a sensitve stomach , I let it idle in the driveway, it's fine
- maybe down to the strip mall for a quart of milk.

Take it out on the freeway and the sucker'll
Hurl all over . . .
locking up your system & requiring a hard boot.
NOt as rugged as its predecessor

- Not reliable as shipped, IMHO

I have it on dozens of machines now without a glitch. Must be you.


Mike:

I went to a DP seminar today; Unofficial reports are they're 200 programs
that
don't work in it;

I am Not easy on software, and can usually find bugs .

This one is an intermittant. even harder to track down

Ran system tools, Norton utilities,
deleted files, cookies,
- Still crashed..

Downloaded / Installed new copies of Mozilla, used three different spyware
scanners,
Tore out a bunch of stuff.

On a non-vital machine, Try popping open 6 sessions of explorer, and
quickly go
in bringin up different web pages on each one .

This used to work flawlessly on SP1; on SP2 it tempermental..

As I said, Your mileage may vary.

Dan

I'm not seeing this behavior at all. I routinely have that many IE's open,
usually many more as Im a QA for software development co. Is it actually
crashing (BSOD) or hanging? Have you been able to decipher the stop codes?

"Dan" wrote in message
...
You should *always* test system updates before putting them on your
"main" systems, people.

Dan

Good advice Dan. I would imaging many of these fixes and features will be
incorporated into Windows server 2003 SP1. That should be fun.

"Dan" wrote in message
...
On Wed, 25 Aug 2004 13:01:40 -0500, "MnMikew"
wrote:


"Dan" wrote in message
.. .
You should *always* test system updates before putting them on your
"main" systems, people.

Dan

Good advice Dan. I would imaging many of these fixes and features will be
incorporated into Windows server 2003 SP1. That should be fun.

Yeah, no doubt. Fortunately, where I work, we're just now testing
Server 2003. I don't think it's running on any real, production
servers yet. I have it on a test bed server in my department, and
it's running fine so far.

Dan

I have it on half a dozen boxes, running great so far. Lots of stuff locked
down, takes some getting used to.