SP2: any problems?

Dave C. wrote:

Yeah, all they have to do is search google. So they turn their computer

on

and . . .



How one gets the instructions is an entirely different matter than whether
they have the skills to do the fix.

The problem here is that all you want to do is whine about how it can't be
done rather than get it done.



Sympathizing is not the same as whining. You seem to take great glee in the
fact that many average computer users are going to experience unwanted
downtime due to Microsoft's screw-up.

I really do get tired of you dreaming up dumb fantasies about what's been said.

Oh, ****, now you're going to tell me
that it's not Microsoft's screw-up.

It's about time you figured that out.

-Dave

Dave C. wrote:

For a computer that runs just fine without SP2, WHAT problem are you

talking

about, exactly? -Dave

The entire processor errata list that's left UN-fixed because the broken
BIOS doesn't have the proper microcode.



So I take it this processor errata list causes the computer not to boot? Or
it causes the computer to unexpectedly shut down? Maybe it causes global
thermonuclear war? What kind of problem does it cause that the end user
will NOTICE? That is, before installing SP2 . . . -Dave

Why don't you go to Intel's site and DOWNload the damn thing so maybe you'd
learn something instead of talking out your arse.

In article , Dave C. says...

Well according to some here your BIOS is broken if your computer boots
correctly and runs OK. -Dave

You're stupid aren't you?


Hey, I'm not the one claiming a computer that boots correctly and runs OK
must have a broken BIOS. -Dave

How long did you claim you've been into PCs?


--
Conor

Opinions personal, facts suspect.

"Dave C." wrote in message
...

Well according to some here your BIOS is broken if your computer boots
correctly and runs OK. -Dave

You're stupid aren't you?


Hey, I'm not the one claiming a computer that boots correctly and runs OK
must have a broken BIOS. -Dave

No, you are the one publically proclaiming your own lunacy.

Howdy!

"Dave C." wrote in message
...
But your definition of a proper BIOS conflicts with reality.

That's just plain silly. There's no 'conflict with reality' in expecting
the mainboard manufacturer to use the proper microcode.


And for the thousandth time, there is nothing wrong with the BIOS until
SP2
is installed. -Dave

Why, yes, there is, if it's not doing the microcode updates that
Intel *ahem* "highly recommends".

RwP

In article ,
says...
In article , Dave C. says...
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



The new version of XP conflicting with a poorly written BIOS? Shaun



OK, I think poorly written is pretty harsh, but I'll concede that point.
Still, as I've posted before, is it easier for microsoft to change a few
lines of code or is it easier to expect dozens of mainboard manufacturers to
reprogram their BIOS so many clueless computer users can risk their
mainboard with a BIOS flash just so SP2 MIGHT work? -Dave

Why should Microsoft bother pampering to crap taiwanese motherboard
manufacturers?


Why should this be about pampering to CTMM's? Surely it's more about
doing right by their customers (the ones who bought their O/S).
Sometimes companies can be good guys for a change, can't they? Is that
such a big deal?
--
Pete Ives
Remove All_stRESS before sending me an email