booting continuously

[Tuna]

My computer is booting continuously. Nothing I do in
advanced setup (safe mode, command prompt, etc) is able to
stop this. Any suggestions?

 

[Bacchas]

Tuna-

Im no expert dude, but it sounds like that Sasser worm that came out a
few months ago. Do you have updated virus protection?? Even if you do
go to this site
http://securityresponse.symantec.com/avcenter/venc/data/w32.sasser.removal.tool.html

Good Luck

-Bacchas

 

[Baz]

My computer is booting continuously. Nothing I do in
advanced setup (safe mode, command prompt, etc) is able to
stop this. Any suggestions?

Have you installed the criminally dangerous SP4? If so, check this out:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839517&Product=win2000

What it doesn't say in the article is that the bluescreen flashes up
briefly, and then the system restarts. Again. And again. And again. And
so on. Also, although the article specifically refers to W2K Server, I can
assure you from bitter experience that exactly the same thing can happen
with W2K Pro.

Anyone who hasn't installed SP4 yet, take heed: DON'T!!!

Baz

 

[Pegasus \(MVP\)]

Have you installed the criminally dangerous SP4? If so, check this out:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839517&Product=win2000

What it doesn't say in the article is that the bluescreen flashes up
briefly, and then the system restarts. Again. And again. And again. And
so on. Also, although the article specifically refers to W2K Server, I can
assure you from bitter experience that exactly the same thing can happen
with W2K Pro.

Anyone who hasn't installed SP4 yet, take heed: DON'T!!!

Baz

While I'm sure you're speaking from bitter experience, your
experience is an isolated one. The vast majority of all PCs
work very nicely with SP4. I have installed about 50, without
the slightest problem. Out of interest, how many did you
install, and how many failed?

 

[Baz]

http://support.microsoft.com/default.aspx?scid=kb;en-us;839517&Product=win2000

While I'm sure you're speaking from bitter experience, your
experience is an isolated one. The vast majority of all PCs
work very nicely with SP4. I have installed about 50, without
the slightest problem. Out of interest, how many did you
install, and how many failed?

I installed one, and it failed: a 100% failure rate! Googling the problem
shows a fair number of other people experiencing the same problem, including
some desperate sysadmins who couldn't start their server after installing
SP4. Of course, those who submitted their anguished please for help to NG's
are the tip of the iceberg: I, for one, fixed it without resorting to
Usenet, but it took a significant amount of my expensive time.

IMNSHO, it doesn't matter that it works with the "vast majority". If your
computer happens to one of the minority which does get screwed up, then the
problem will certainly be expensive, and could be disastrous. Microsoft
released a Service Pack that, by their own admission, renders some computers
inoperable. Their failure to withdraw the SP as soon as they knew about the
problem is, I submit, criminally irresponsible.

Baz

 

[Simon]

Computers screw up all the time for many reasons. When it happens
hours/days/weeks after SP4 install it doesn't necessarily mean the SP4 was
to blame. In many cases it was probably just a coincidence.

Even in MS know that it causes problems in x% of cases, if it solves
problems in n * x% (where n > 1) cases then overall its still a good thing.

I have installed and been running SP4 without any problems. Thats a 100%
success rate.

Simon

 

[Pegasus \(MVP\)]

http://support.microsoft.com/default.aspx?scid=kb;en-us;839517&Product=win2000

I installed one, and it failed: a 100% failure rate! Googling the problem
shows a fair number of other people experiencing the same problem, including
some desperate sysadmins who couldn't start their server after installing
SP4. Of course, those who submitted their anguished please for help to NG's
are the tip of the iceberg: I, for one, fixed it without resorting to
Usenet, but it took a significant amount of my expensive time.

IMNSHO, it doesn't matter that it works with the "vast majority". If your
computer happens to one of the minority which does get screwed up, then the
problem will certainly be expensive, and could be disastrous. Microsoft
released a Service Pack that, by their own admission, renders some computers
inoperable. Their failure to withdraw the SP as soon as they knew about the
problem is, I submit, criminally irresponsible.

Baz

We both know that a sample of one does not allow you to
draw any conclusions other than "failure is possible". We
know this already. It is accepted in the software industry
that it is impossible to write code that is totally fail-proof.
There are simply too many combinations and permutations.
Kicking Microsoft prevents you from realising that
other people are dealing with the same issues. Just look
at some of the more spectacular failures within space
agencies, both US and European: Spacecraft missing their
target because some programmers used miles, others
kilometers. Rockets blowing themselves up because the
speed monitor went into an overflow condition. The Mars
probe remaining silent for a few days because the system
was in a permanent overload condition.

You suggest that Microsoft should withdraw SP4 rather
than publish a KB article. Please elaborate how you would
go about doing this! Professionals protect themselves
against this type of mishap by taking a snapshot of
important installations prior to implementing a major change.
If disaster strikes then the system is restored in less than
one hour.