reasons to reboot w2k

  • Thread starter Thread starter badgolferman
  • Start date Start date
B

badgolferman

Some time ago there was a discussion about reasons why you would have to
reboot W2K. Since W2K is so stable there is very little reason to do this
at all. My two computers and others that I admin at work have been rock
solid except when flaky software has been installed.

I would be interested in people's list of reasons for rebooting W2K, e.g.
hardware install, IP change, etc. Also, is XP as stable?
 
Usually for Windows Updates or something unusual like a freeze that can not be
corrected with Task Manager or if it seems that Task Manager is reporting more memory
than usual being used at "idle" that may indicate a memory leak. --- Steve
 
badgolferman said:
Some time ago there was a discussion about reasons why you would have to
reboot W2K. Since W2K is so stable there is very little reason to do this
at all. My two computers and others that I admin at work have been rock
solid except when flaky software has been installed.
Click to expand...
I would be interested in people's list of reasons for rebooting W2K, e.g.
hardware install, IP change, etc. Also, is XP as stable?
Click to expand...

I normally reboot only when a software install or uninstall demands it,
when a power glitch forces the issue, or when I've powered down the system
because I'm going to be away for more than 24 hours.

Lately I've had to reboot a couple of times because my cable internet
provider was having problems that resulted in a bad IP address assignment.
Rebooting is one way to clear that up, but I'm hoping to find a better
way.

My machine at work has been up continuously for 21 days.
 
Back
Top