SP2: any problems?

  • Thread starter Thread starter ToolPackinMama
  • Start date Start date
David said:
ToolPackinMama wrote:

That does NOT mean 'SP2 conflicts with XP'.
Click to expand...

So you say.
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.
Click to expand...

Oh, God, Listen to yourself.
 
ToolPackinMama said:
David Maynard wrote:




Right. Assuming that you can boot.
Click to expand...

To use your auto mechanic example, that's like saying you can only get your
car fixed if you can drive it there.
 
ToolPackinMama said:
David Maynard wrote:




So, here come the hired hands who fix things...
Click to expand...

Only if you're clueless.
:/

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

If the BIOS wasn't broken to begin with SP2 wouldn't have a problem.
 
ToolPackinMama said:
So you say.
Click to expand...

Simple fact.

If you have a proper BIOS and operational hardware then it works just fine,
which is proof that SP2 has no 'conflict with XP'. It has a 'conflict' with
a particular BIOS deficiency.

Oh, God, Listen to yourself.
Click to expand...

I heard it before you did. LOL

Look, you can stomp and hold your breath till blue in the face but that
won't alter the fact that 'problems' happen. Always have and always will.
That's why the word exists.

You don't have to like it but you DO have to deal with them.
 
ToolPackinMama said:
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.
Click to expand...

Dread that and their Prescott CPU....hmmm...do I smell a lurker under the
bridge.
 
Under bridge warning.

ToolPackinMama said:
ROFLMAO!

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

Get with reality, you bumpkin. :)
Click to expand...
 
Ron said:
Under bridge warning.
Click to expand...

To you, anyone who can hold their own in an argument is a troll. IMHO,
that makes you worse than a troll. See your psychiatrist for a
solution.

;)
 
ROFLMAO!

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

Get with reality, you bumpkin. :)
Click to expand...
And here is the reason that worms, trojans and viruses are so rampant
on the internet...
 
You're joking, right? :D That's like saying that you need to be an
auto mechanic to ~drive a car~. :D
Click to expand...
No it isn't. If your car breaks and you're not an auto mechanic you
take it to a garage to be repaired do you not?
 
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.
Click to expand...
Find someone who repairs PCs. Ask them to fix it.
 
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.
Click to expand...
Ands like the average car driver, they then take it to a technician to
fix.
 
So, here come the hired hands who fix things...

:/

But if SP2 didn't break it, it wouldn't need fixing, FWIW.
Click to expand...
You've already shown amply in the past that you are the last person
someone should turn to when they have a PC problem.
 
Dude. Doooode. It's clearly a SP2 PROBLEM that didn't exist before
SP2, Dude.
Click to expand...

The problem did exist. The BIOS was badly written but the motherboard
maker "got away with it" because the functionality wasn't used.

Its akin to having a broken car heater on a car that is used solely in
the Sahara desert. Untl you go somewhere where its so cold you need to
use the heater you'll not know its broken.
 
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.
Click to expand...

THANK YOU!!!
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.
Click to expand...

There is no easy solution. There is a file that you can rename, but you
won't be able to do that unless you have a linux boot disk or something,
because you can't boot windows at all. You can supposedly turn off L1/L2
cache in the BIOS to allow the system to boot. You'll obviously have to
talk your loved one through that. IF THAT WORKS (don't hold your breath),
then the very next step is for the affected person to transfer all data
files to external storage (CDR/W, flash drive, SOMETHING). Then you start
an uninstall of SP2 which is supposed to take several hours in Microsoft
hours. (yikes)

Oh yes, someone is going to pipe up and say the "proper" solution is to
update the BIOS. Problem is, many of the affected boards have no BIOS
update available, and Microsoft knows that. And during a BIOS flash, there
is always a possibility that you will end up with a non-functional
motherboard. So before you try updating the BIOS, you need to back up your
data files and uninstall SP2. You can always reinstall SP2 later if you
find their IS a BIOS update available, and assuming the BIOS update goes
K. -Dave
 
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?
Click to expand...

That question can't be answered as stated. Many systems have a proper BIOS
and functional hardware, but do NOT have a BIOS that is compatible with SP2.
On these systems, SP2 prevents windows XP from being run, in any manner. As
I wrote before, if someone sold gas that would cause certain car engines to
melt, would you then blame the automobile manufacturer? Not bloody likely.
But Microsoft and YOU want to blame this on hardware or firmware. That's
just not logical. It could be argued that the mainboard manufacturers
SHOULD release a BIOS update. That's a perfectly legitimate argument. But
when there's no BIOS update available, it's also a red herring. On certain
systems that are running the latest BIOS version available and have NO
PROBLEMS AT ALL with hardware or firmware, SP2 causes Windows XP not to
boot. Not normally, not safe mode, and not from CD-Rom. If that isn't SP2
conflicting with Windows XP, what is? -Dave
 
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.
Click to expand...

Many computer users don't know a computer knowledgeable person who would be
willing to help them. And when your computer is broken, how do you google
it, exactly? -Dave
 
But if SP2 didn't break it, it wouldn't need fixing, FWIW.
If the BIOS wasn't broken to begin with SP2 wouldn't have a problem.
Click to expand...

You are under the mistaken impression that the BIOS is broken. On many of
the machines in question, the latest BIOS version available works just fine
without SP2 installed. That could hardly be called "broken". Note that I'd
agree with you if you say the mainboard manufacturer should release an
updated BIOS version soon. But not because the BIOS is broken. Microsoft
really needs to address this issue from THEIR END, and stop trying to pass
the buck. -Dave
 
Ands like the average car driver, they then take it to a technician to
fix.
Click to expand...

Let me get this straight. Microsoft releases software that breaks perfectly
working systems. Mainboard manufacturers are guilty of having improper
microcode in the latest BIOS version of some of their systems. The end
result of these two things happening is that many systems become unusable
after SP2 is installed. You think the average computer user should have to
pay a professional to fix a problem that shouldn't exist? **** that, I say
send the bill to Microsoft. It could be argued the mainboard manufacturers
should receive just as much of the blame. But Microsoft had the last
opportunity to avoid this mess, and they have the best opportunity to fix it
quickly. That is, it's a lot easier to fix SP2 than it is to force dozens
of mainboard manufacturers to fix their BIOS and then somehow force millions
of mainboard owners to update it and risk damaging their mainboard in the
process. That's why I say send the bill to Microsoft. -Dave
 
Dude. Doooode. It's clearly a SP2 PROBLEM that didn't exist before
That does NOT mean 'SP2 conflicts with XP'.


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.
Click to expand...

I will say this as gently as possible. You obviously know hardware pretty
well. From reading your posts, I'd guess you are a IT professional of some
kind. Your weakness is that you need to learn to see computer problems from
the point of view of the average computer user. You are so far ABOVE the
average computer user, that it seems you have lost that point of view
completely. You say SP2 does not conflict with XP. Technically, you are
RIGHT on that. I know that, YOU certainly know that. The average computer
user who has one of the affected systems would say we are BOTH full of shit
if we said that SP2 has no conflict with Windows XP, though.

As I wrote elsewhere, Microsoft had the last opportunity to prevent this
issue, and Microsoft has the best opportunity to fix it now. Computer
owners shouldn't have to "deal with it", if Microsoft was responsible enough
to DO SOMETHING about it. Again I'll state that I don't think SP2 is ready
for public release. -Dave
 
Back
Top