SP2: any problems?

[David Maynard]

OK, let me be more logical. For many of the affected systems,

For a select few running particular processors, and on a BIOS that doesn't
support the proper microcode.

there is no
hardware or firmware solution.

That just simply isn't true. But like a bad politician you repeat it anyway.

Thus, if you install SP2, Windows will not
boot.

Until one applies one of the fixes; the most proper being to have a proper
BIOS.

How can anyone then claim with a straight face that SP2 does not
conflict with Windows XP?

Because if it 'conflicted with XP' then ALL of them would have serious
problems as they all run XP, but they don't. It's only the ones with
specific processors on BIOSs with improper microcode that have the problem.

Now we can debate all day long whether it's more egregious that SP2 has
problems with screwed up BIOSes or that the BIOS is screwed up to begin
with but, the fact of the matter is, SP2 does not 'conflict with XP'; it
has a problem with the screwed up BIOS.

Seems pretty clear to me. -Dave

That's exactly what a poor politician says just after having burped up a
pile of B.S.

 

[David Maynard]

True!!! But two wrongs don't make a right.

No one claimed it did.

It seems irresponsible to
release software that will cause windows not to boot and then say "Oh, well,
you need to talk to your mainboard manufacturer about that".

"Seems" don't cut the mustard and it's absurd to arbitrarily demand that
software 'work' regardless of how screwed up everything else is.

Imagine if
someone started selling gas that would cause a car engine to melt if it
wasn't running a certain compression ratio. And then imagine the gas
station trying to blame the problem on the car manufacturers. Somehow, I
don't think that would fly.

Bad analogy. The more proper analogy is the car maker specs his car to have
'X' compression ratio, the gas is made to, and does, work properly with 'X'
compression ratio but it turns out that some of the cars *aren't* 'X'
compression ratio after all and you blame the gas station.

 

[Dave C.]

That just simply isn't true. But like a bad politician you repeat it anyway.

Then I guess microsoft is guilty of spreading bad rumors about it's own
software. Why the HECK would they do that?!? -Dave

 

[David Maynard]

:




I agree.

And what part of 'XP' would you say SP2 'conflicts' with considering that
if one has a proper BIOS and functional hardware it works perfectly fine?

 

[David Maynard]

anyway.


Then I guess microsoft is guilty of spreading bad rumors about it's own
software.

And, again, the bad politician repeats a falsehood he's already been shown
is a falsehood.

Why the HECK would they do that?!?

They don't.

 

[ToolPackinMama]

And what part of 'XP' would you say SP2 'conflicts' with considering that
if one has a proper BIOS and functional hardware it works perfectly fine?

Look, on a practical level, we're talking about a formally working PC
that suddenly doesn't work after applying SP2. The poor person effected
doesn't know/care about how it happened or whether it's "really a BIOS
problem". From their point of view, the BIOS was fine before, and now
suddenly it's not, thanks to SP2.

My question is: if this happens to you or to someone you love, what is
the "easy" solution? The victim can't boot, so how do they proceed to
implement the solution? Details, please.

 

[Ron Reaugh]

Define "easy", especially if you can't boot.

In BIOS setup disable L1 & L2 cache. Start up XP in SafeMode. Rename
update.sys. Re-enable L1 & L2 cache. SP2 now works fine.

 

[Ron Reaugh]

Then I guess microsoft is guilty of spreading bad rumors about it's own
software. Why the HECK would they do that?!? -Dave

More lies....back under bridge.

 

[Ron Reaugh]

fine?

Look, on a practical level, we're talking about a formally working PC
that suddenly doesn't work after applying SP2. The poor person effected
doesn't know/care about how it happened or whether it's "really a BIOS
problem". From their point of view, the BIOS was fine before, and now
suddenly it's not, thanks to SP2.

My question is: if this happens to you or to someone you love, what is
the "easy" solution? The victim can't boot, so how do they proceed to
implement the solution? Details, please.

Enter BIOS setup and disable L1 & L2 cache. Boot into SafeMode and rename
update.sys. Re-enable L1 & L2 cache. SP2 works fine now.

 

[ToolPackinMama]

In BIOS setup disable L1 & L2 cache. Start up XP in SafeMode. Rename
update.sys. Re-enable L1 & L2 cache. SP2 now works fine.

What's "easy" about that, if you don't ~just know~ to try that?

 

[ToolPackinMama]

Enter BIOS setup and disable L1 & L2 cache. Boot into SafeMode and rename
update.sys. Re-enable L1 & L2 cache. SP2 works fine now.

And the average web-browsing home user doesn't know that, and has no
idea how to find out, genius. For them it's not an easy solution. For
them, it's a PC that won't boot, and they don't know what to do.

 

[David Maynard]

Look, on a practical level, we're talking about a formally working PC
that suddenly doesn't work after applying SP2. The poor person effected
doesn't know/care about how it happened or whether it's "really a BIOS
problem". From their point of view, the BIOS was fine before, and now
suddenly it's not, thanks to SP2.

I am aware of what 'the problem' is but that doesn't justify the illogical
absurdity of saying 'SP2 conflicts with XP' when it's clearly a BIOS conflict.

And your example of the poor person who doesn't know isn't helped any by
those who should know telling them B.S.

My question is: if this happens to you or to someone you love, what is
the "easy" solution? The victim can't boot, so how do they proceed to
implement the solution? Details, please.

Boot original XP CD. Select Recovery console. Rename update.sys to update.old.

If you have problems with that, or no CD, enter BIOS setup and disable L1 &
L2 cache. Boot into Safe Mode and rename update.sys.

Reboot and run.

 

[ToolPackinMama]

I am aware of what 'the problem' is but that doesn't justify the illogical
absurdity of saying 'SP2 conflicts with XP' when it's clearly a BIOS conflict.

Dude. Doooode. It's clearly a SP2 PROBLEM that didn't exist before
SP2, Dude.

Boot original XP CD. Select Recovery console. Rename update.sys to update.old.

OMG, do you realize that 99.9 percent of all XP users would never think
of trying something like that? Are people supposed to ~just know~ to
try that? Be reasonable.

 

[David Maynard]

What's "easy" about that, if you don't ~just know~ to try that?

Contrary to the popular belief, using a computer requires some degree of
common sense competence; the least of which being the ability to seek
solutions when you have a problem.

 

[ToolPackinMama]

Contrary to the popular belief, using a computer requires some degree of
common sense competence

ROFLMAO!

You're joking, right? That's like saying that you need to be an
auto mechanic to ~drive a car~.

Get with reality, you bumpkin.

 

[David Maynard]

And the average web-browsing home user doesn't know that, and has no
idea how to find out, genius. For them it's not an easy solution. For
them, it's a PC that won't boot, and they don't know what to do.

Oh, for heaven's sake, people. What the hell do you do when your car breaks
down? Are you completely clueless on how to get your TV fixed if it fails?
And I suppose you just sit there and freeze to death if the heater goes out
because, woe is me, you don't know what to do?

The only difference is that doing a simple web search for the problem takes
5 minutes, if you're slow, and is free. But if you're REALLY clueless you
end up with the same situation you have with everything else: finding
someone who isn't clueless to fix it for you.

 

[ToolPackinMama]

Contrary to the popular belief, using a computer requires some degree of
common sense competence; the least of which being the ability to seek
solutions when you have a problem.

Right. Assuming that you can boot.

 

[ToolPackinMama]

Oh, for heaven's sake, people. What the hell do you do when your car breaks
down? Are you completely clueless on how to get your TV fixed if it fails?

So, here come the hired hands who fix things...

:/

But if SP2 didn't break it, it wouldn't need fixing, FWIW.

 

[David Maynard]

Dude. Doooode. It's clearly a SP2 PROBLEM that didn't exist before
SP2, Dude.

That does NOT mean 'SP2 conflicts with XP'.

OMG, do you realize that 99.9 percent of all XP users would never think
of trying something like that? Are people supposed to ~just know~ to
try that? Be reasonable.

YOU be reasonable. Problems don't fix themselves and people have to deal
with them regardless of which technological marvel it is: your car, your
TV, your phone, and, yes, your computer.

Sorry, that's life. Deal with it.

 

[David Maynard]

ROFLMAO!

You're joking, right?

Not one bit.

That's like saying that you need to be an
auto mechanic to ~drive a car~.

No, it's like saying you need to know that auto mechanics exist if you
can't fix it yourself.

In the case of the computer, and this particular problem, a simple web
search (assuming you're too clueless to check the Microsoft site) will find
the solution in less than 5 minutes, but if you're too clueless to manage
even that then you're reduced to the same common sense solution you use for
every other problem: find someone who isn't clueless to fix it for you.

Get with reality, you bumpkin.

YOU better get with reality, bumpkess, or else you're going to be walking
for the rest of your life because you, poor thing, don't know what to do
when your car breaks.