sp2 is a certified killer

  • Thread starter Thread starter jg
  • Start date Start date
J

jg

I installed this "trash" last week, 8/25, and i destroyed
my hard drive..went out bought a new one. installed this
trash, and now my screen is so small, I cant see it, and
my logon is slower than with dial up,, and I have
pipeline..what a sad state of affairs..beware folks..
 
-----Original Message-----
I installed this "trash" last week, 8/25, and i destroyed
my hard drive..went out bought a new one. installed this
trash, and now my screen is so small, I cant see it, and
my logon is slower than with dial up,, and I have
pipeline..what a sad state of affairs..beware folks..
.
We cant help you have a worn out system,if you replaced
Click to expand...
a HD sp2 was not at fault,you probably destroyed it with
all the viruses you got from free Russian porno sites you
visited.
 
SP2 can't trash your system..if your HD died then it was about to do so
anyway......there's something else wrong with memory or drivers
 
"...i destroyed my hard drive..."

You got that right. Don't blame it on Microsoft.
 
First of all, software is incapable of "destroying" a hard drive. If indeed
your hard drive died, it was coincidence. The screen resolution is part of
your video card drivers, not SP2. I have no idea what pipeline is...must be
new. If you had cable or DSL, perhaps we could help with that.

Bobby
 
I have not installed sp2 at this point,with all the negative info on this
form,I do not want to install. Has anyone noticed any connection, ie. pc
brand,software installed etc. I ordered the cd from Microsoft today. I do not
want to destroy this new pc or have to do a complete os restore from boot
using f10 complete restore. Greg in Canada
 
Greg;

You must realize that the people who post here do so because they have a
problem. Rarely does anyone post when they don't have a problem. I have 5
computers in my home...different makes, models, processors, etc. I have
installed SP2 on all of them , and had one minor issue with a NIC card that
was corrected by downloading updated drivers. Otherwise, SP2 runs
wonderfully on all my machines. I would estimate, from my conversations
with colleagues and clients, that roughly 80% of those who install SP2 have
no problems. The other 20%, I believe had issues BEFORE they installed SP2,
and the problems were compounded with the installation. I would recommend
that you back up what information/data you consider important, and then
install SP2. It can't hurt to try.


Bobby
 
JG

I agree with NoNo.. I have installed SP2 on my system.. it is still working
and I have had no problems related to SP2 at all..

Mike H
 
I agree with NoNo.. I have installed SP2 on my system.. it is still
working
and I have had no problems related to SP2 at all..

Mike H


in message
on connection,
ie. pc
Click to expand...

Only problem I had when I installed SP2 was that Nero6 needed an
update. Other than that, pc runs the same.

I work in computer repair, and have seen alot of the SP2 issues, seems
to mostly come from people that do have other problems on the pc (i.e.
malware, virus).

Keep your pc clean and SP2 should be no problem. There are however a
few hardware items that could cause problems, most average home users
would have no clue on how to fix.

This is a pretty good link to hopefully help a few people:

http://www.michna.com/kb/WxSP2.htm#Boot_or_shutdown_problems_after_Service_Pack_2_installation
 
My screen did the same thing after installing SP2 and a
couple of freezeups. It's not permanent. You can
resize/adjust it, thank goodness.

I had to run my modem CD to get rid of the severe lag.
Couldn't connect at anything other than 28.8kbps.

I downloaded the updated graphics drivers & that worked
for my freezeups & glitchy graphics, until I visited the
same FLASH site again. Others on that site have had
similar problems.

I'm still trying to fix the SP2 glitches before resorting
to uninstalling it. My computer is used almost 24/7 for
all types of things from gaming, to graphics work in
Adobe, to building sites, to chatting, you name it. XP
has been wonderful. SP2 has some glitches. Take it from
someone who USES computers & doesn't just tweak them for
little purpose:)
 
On Tue, 31 Aug 2004 11:47:02 -0700, "Mike DalBon"
Conceptually, did any of you who've had issues with SP2 read ANY of the
documentation from the MANUFACTURER of your system's web site prior to
installing?
Click to expand...

Yes. At the time, www.jetway.com.tw claimed latest July 2004 BIOS
version 04 was OK for Prescott; no FAQ on SP2, etc.
Did you read the information from Microsoft (which you have to
really try hard to avoid) before installing SP2?
Click to expand...

Yes. At the time - and I have not checked this week - there was no
specific caveat on my issue (Prescott microcode level), just a general
"check your hardware vendor for updates". See above.

More recently, Intel added a new page with documentation on the
Prescott issue; there was zero there before.

Most recently, Jetway brought out a new version 05 of their BIOS that
better supports Prescott, in the sense that it now pushes Intel's
microcode to rev it up so it will work with SP2. That BIOS's date is
1 September 2004, so it wasn't there when I needed it.
The first thing any of them say is "back up your data".
Click to expand...

That assumes it's acceptable to have to redo the whole PC if an SP
installation barfs, and then restore data on top. It is not.
The service pack even creates a restore point just in case.
Click to expand...

Doesn't help when XP won't boot at all, even into Safe Mode.
To make the statement that software "trashed your hard drive" really shows
why some people really ought not to just click "OK". There's no shame in
taking your PC to the shop to have it fixed. And they read the "before you
begin" articles.
Click to expand...

Reading those articles at the time would have given NO inkling about
the particular problem I hit the hard way, and described here:

http://cquirke.mvps.org/sp2intel.htm

The point is, not all SP2 issues appear survivable to the average
users SP2 is aimed at, and are not documented "before you start".

Consider also that SP2 is now delivered via WU and on CD-ROMs, which
is lot less likely to be researched than when a user navigates the web
site to download it deliberately.
To discourage others from installing a worthwile, and in this day and time
necessary, update is a great disservice to the community and user base.
Click to expand...

You have to caveat the advice to "just install it, it's great!" as
there are (now) certain PC configs that are 100% certain to become
unbootable after installing SP2.
4 SP2 installs, no issues.
Click to expand...

If I'd installed SP2 this week, after updating my BIOS to 1 September,
I'd be able to say "1 SP2 install, no issues". Because I did this a
couple of weeks ago, I'd be able to say "1 SP2 install, 100% failure".

In both cases, I'd be right; in both cases, my observation would have
no predictive value for you. It is however significant that WU
started pushing SP2 before the issue was well documented, and remains
significant if SP2 (or the WU wrapper that pushes it) still does not
detect at-risk PCs and step aside.

--------------- ----- ---- --- -- - - -
Click to expand...
Never turn your back on an installer program
 
cquirke (MVP Win9x) said:
In both cases, I'd be right; in both cases, my observation would have
no predictive value for you. It is however significant that WU
started pushing SP2 before the issue was well documented, and remains
significant if SP2 (or the WU wrapper that pushes it) still does not
detect at-risk PCs and step aside.
Click to expand...

A new update.sys is the obvious short term MS fix for SP2. MS IS where that
responsibility lies at least in the short term.
 
A new update.sys is the obvious short term MS fix for SP2. MS IS where that
responsibility lies at least in the short term.
Click to expand...

Assuming the OS will work fine without whatever it is that Update.sys
does (the OS runs "fine" with no Update.sys at all), the question is
then how to retrofit a fixed Update.sys into SP2 so that it is in
effect at the time that SP2 is installed.

If MS had a fixed version of Update.sys right now (and again, assuming
that's the only code that needs revision), that's only half the job.
The rest is how to make this meaningfully and effectively available to
the target audience for SP2, which includes the rankest newbies.

Clearly, the usual approach of a follow-up patch isn't going to help
here, because once SP2 is installed with the buggy Update.sys in
effect, the problem will manifest on first boot.

The only Day 0 ways I can see on this are one/more of:
- detect affected PCs and don't push SP2 to them via WU
- detect affected PCs and abort SP2 install

The first requires a Prescott-aware stub at the WU level, and the
second requires a modified installer within SP2 itself.

Once a fix exists, this approach can be modified - the fix can be
pushed via WU, WU's SP2 stub can check whether the fix is in place,
and only then push down SP2 to affected PCs. Somehow, the fix would
have to patch into SP2's installation process so all ends well.

Revising SP2 itself looks like the obvious solution, but I can
understand some reluctance on that - after all, there may already be
CD-ROMs minted, and so on.

The challenge with "outside the box" fixing is to make sure the fix is
in effect before that first post-installation restart; else, boo-hoo.



--------------- ----- ---- --- -- - - - -
Click to expand...
I've got my mobo workin' babe...
 
cquirke (MVP Win9x) said:
Assuming the OS will work fine without whatever it is that Update.sys
does (the OS runs "fine" with no Update.sys at all),
Click to expand...

That was from Cari's threads which brought the issue front and center in the
MS NGs in mid August. There's now an MS KB article that CURIOUSLY does NOT
show up on a search of microsoft.com :
http://support.microsoft.com/default.aspx?scid=kb;en-us;555185&Product=winxp
the question is
then how to retrofit a fixed Update.sys into SP2 so that it is in
effect at the time that SP2 is installed.
Click to expand...

SP2a or a pre-fix or just a BIG WARNING and a manual fix procedure.
If MS had a fixed version of Update.sys right now (and again, assuming
that's the only code that needs revision),
Click to expand...

We know that is sufficient to allow full booting and substantial functional.
Therefore that is sufficient to justify just an update.sys fix
that's only half the job.
Click to expand...

Possibly. I sure wished that we knew what that JOB was!
The rest is how to make this meaningfully and effectively available to
the target audience for SP2, which includes the rankest newbies.

Clearly, the usual approach of a follow-up patch isn't going to help
here,
Click to expand...

No, WinUp would do fine.
because once SP2 is installed with the buggy Update.sys in
effect, the problem will manifest on first boot.
Click to expand...

Yup, those newbies need help.
The only Day 0 ways I can see on this are one/more of:
- detect affected PCs and don't push SP2 to them via WU
Click to expand...

Well just push a fixed update.sys. SP1's version would be ok.
- detect affected PCs and abort SP2 install
Why?

The first requires a Prescott-aware stub at the WU level, and the
second requires a modified installer within SP2 itself.

Once a fix exists,
Click to expand...

A sufficient fix exists NOW.
this approach can be modified - the fix can be
pushed via WU, WU's SP2 stub can check whether the fix is in place,
and only then push down SP2 to affected PCs. Somehow, the fix would
have to patch into SP2's installation process so all ends well.

Revising SP2 itself looks like the obvious solution, but I can
understand some reluctance on that - after all, there may already be
CD-ROMs minted, and so on.
Click to expand...


They knew in June.
 
On Sun said:
"cquirke (MVP Win9x)" <[email protected]> wrote in message
Click to expand...
That was from Cari's threads which brought the issue front and center in the
MS NGs in mid August. There's now an MS KB article that CURIOUSLY does NOT
show up on a search of microsoft.com :
http://support.microsoft.com/default.aspx?scid=kb;en-us;555185&Product=winxp
Click to expand...

Ah, that was written by Cari ! I've been wondering when MS would
document this, as this is the first specific coverage I've seen there.

I wrote http://cquirke.mvps.org/sp2intel.htm to fill the gap,
immediately after my test PC's regular polling of WU showed that SP2
was beginning to be pushed. I started at 02:00, done by 04:00
No, WinUp would do fine.
Click to expand...

What I mean is, you can't let at-risk PCs install SP2 and then apply a
fix-it, because installing SP2 will kill those PCs and so they won't
be there to pull down the fix-it. The fix has to be in place *before*
SP2 installs, to avoid the whole crisis.
Why?
Click to expand...

Because if you install SP2 as-is, these PCs won't boot.


-------------- ---- --- -- - - - -
Click to expand...
"I think it's time we took our
friendship to the next level"
'What, gender roles and abuse?'
 
Back
Top