What are your usual longest uptimes before (reboot/shutt)ingdown old, updated, 32-bit Windows XP SP3?

It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
forced to reboot.

What about the rest of you guys? Thank you in advance.
--
"If someone makes you angry, I think the thing to do is tie them down to
the ground, cover them in honey, and then release a swarm of killer ants
on them. That way, you can hit them over and over again and say, 'Hey!
I'm just trying to help!' and they can't really get mad at you." --R.M.
Weiner
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.

In article ,
NT, Ant says...

It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
forced to reboot.

What about the rest of you guys? Thank you in advance.

It's old skool MS kernel. Give it clean undies onece a week.

--
Duncan.

In article ,
NT, Ant says...

It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
forced to reboot.

What about the rest of you guys? Thank you in advance.

It's old skool MS kernel. Give it clean undies onece a week.

--
Duncan.

Per Ant:
It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
forced to reboot.

What about the rest of you guys? Thank you in advance.

I am sure it is overkill, but I have gone over to re-booting one of my
machines (in a remote location where I would have to drive to reset it)
automatically every morning at 0200.

Does not seem to me like there has been any cost during the couple of
years I have been doing this: schedule the reboot and forget about it.

On all my machines, I have BIOS set to automagically re-boot the machine
if/when power is removed/restored so, for those machines within easy
reach, there is always yanking the power cord as a last-ditch move if
the three-finger salute does not work.
--
Pete Cresswell

Per Ant:
It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
forced to reboot.

What about the rest of you guys? Thank you in advance.

I am sure it is overkill, but I have gone over to re-booting one of my
machines (in a remote location where I would have to drive to reset it)
automatically every morning at 0200.

Does not seem to me like there has been any cost during the couple of
years I have been doing this: schedule the reboot and forget about it.

On all my machines, I have BIOS set to automagically re-boot the machine
if/when power is removed/restored so, for those machines within easy
reach, there is always yanking the power cord as a last-ditch move if
the three-finger salute does not work.
--
Pete Cresswell

| It seems after a couple weeks of nonstop uptime (no hibernation and
| sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
| Pro SP3 will start misbehaving. I would need to start exiting stuff
| because softwares were not responding (Explorer, SeaMonkey, Trillian,
| cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
| forced to reboot.
|
| What about the rest of you guys? Thank you in advance.

The longest for me is several hours. If I'm going to
be away for a break I "sleep" it. If I'm going out I
usually shut it down. I always shut it down at night.

I don't understand why people waste electricity and
increase hardware wear by leaving it on for no reason.
Are you just too impatient to wait a few seconds for
the machine to boot? Do you also leave your car running
all the time so you won't have to wait an interminable
30 seconds to start driving? Is your oven permanently
pre-heated? Do you leave all your lights on so that you
won't have to deal with the tedium of lifting your arm
*yet again* to flip the switch? If you don't do those
things then why do you leave your computer running?

There used to be a myth that shutting down wears
out the hardware. I once read a repair book that siad
there's some truth to that. Micro cracks can develop
in solder with temperature changes. But the book said
it would take 10 years or more for such affects to
show up. Meanwhile there's electricity wasted and
wear on hard disks, maybe RAM, monitor, fans, etc.
I'm guessing that myth was perpetrated by lazy office
people who didn't want to wait for boot each morning
at work.

| It seems after a couple weeks of nonstop uptime (no hibernation and
| sleeps too; highest was 22 days!), my very old updated 32-bit Windows XP
| Pro SP3 will start misbehaving. I would need to start exiting stuff
| because softwares were not responding (Explorer, SeaMonkey, Trillian,
| cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I am
| forced to reboot.
|
| What about the rest of you guys? Thank you in advance.

The longest for me is several hours. If I'm going to
be away for a break I "sleep" it. If I'm going out I
usually shut it down. I always shut it down at night.

I don't understand why people waste electricity and
increase hardware wear by leaving it on for no reason.
Are you just too impatient to wait a few seconds for
the machine to boot? Do you also leave your car running
all the time so you won't have to wait an interminable
30 seconds to start driving? Is your oven permanently
pre-heated? Do you leave all your lights on so that you
won't have to deal with the tedium of lifting your arm
*yet again* to flip the switch? If you don't do those
things then why do you leave your computer running?

There used to be a myth that shutting down wears
out the hardware. I once read a repair book that siad
there's some truth to that. Micro cracks can develop
in solder with temperature changes. But the book said
it would take 10 years or more for such affects to
show up. Meanwhile there's electricity wasted and
wear on hard disks, maybe RAM, monitor, fans, etc.
I'm guessing that myth was perpetrated by lazy office
people who didn't want to wait for boot each morning
at work.

Per Mayayana:
There used to be a myth that shutting down wears
out the hardware. I once read a repair book that siad
there's some truth to that. Micro cracks can develop
in solder with temperature changes. But the book said
it would take 10 years or more...

I'm guessing that myth was perpetrated by lazy office
people who didn't want to wait for boot each morning
at work.

I suspect it came from experience with dumb terminals.
Back in the mainframe days.

Somebody in our shop got the bright idea of turning off all the dumb
terminals at COB every day to save electricity.

They got an award from the suggestion system for it because they were
able to quantify the project savings:
#OfTerminals*WattsPerTerminal*Hours).

But what we found was that service calls for the terminals
increased enough to more than outweigh the electric
savings. I guess it was the heating/cooling/cracking
thing, but I don't really know - but the service calls
*did* increase enough that and we went back to leaving them on 24-7.
--
Pete Cresswell

Per Mayayana:
There used to be a myth that shutting down wears
out the hardware. I once read a repair book that siad
there's some truth to that. Micro cracks can develop
in solder with temperature changes. But the book said
it would take 10 years or more...

I'm guessing that myth was perpetrated by lazy office
people who didn't want to wait for boot each morning
at work.

I suspect it came from experience with dumb terminals.
Back in the mainframe days.

Somebody in our shop got the bright idea of turning off all the dumb
terminals at COB every day to save electricity.

They got an award from the suggestion system for it because they were
able to quantify the project savings:
#OfTerminals*WattsPerTerminal*Hours).

But what we found was that service calls for the terminals
increased enough to more than outweigh the electric
savings. I guess it was the heating/cooling/cracking
thing, but I don't really know - but the service calls
*did* increase enough that and we went back to leaving them on 24-7.
--
Pete Cresswell

Ant wrote:
It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows
XP Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I
am forced to reboot.

What about the rest of you guys? Thank you in advance.

I probably have to reboot due to problems every month or 3.

Ant wrote:
It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows
XP Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I
am forced to reboot.

What about the rest of you guys? Thank you in advance.

I probably have to reboot due to problems every month or 3.

It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows
XP Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I
am forced to reboot.

What about the rest of you guys? Thank you in advance.

I probably have to reboot due to problems every month or 3.

Wow, three/3 months! I wished mine go that high! I assume you used your
daily and a lot?
--
"Caution is not cowardice; even the ants march armed." --Ugandan Proverb
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.

It seems after a couple weeks of nonstop uptime (no hibernation and
sleeps too; highest was 22 days!), my very old updated 32-bit Windows
XP Pro SP3 will start misbehaving. I would need to start exiting stuff
because softwares were not responding (Explorer, SeaMonkey, Trillian,
cmd.exe, etc.) correctly. Eventually, this won't work anymore, and I
am forced to reboot.

What about the rest of you guys? Thank you in advance.

I probably have to reboot due to problems every month or 3.

Wow, three/3 months! I wished mine go that high! I assume you used your
daily and a lot?
--
"Caution is not cowardice; even the ants march armed." --Ugandan Proverb
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.

On Sat, 28 Mar 2015 00:57:38 -0700, Ant wrote:


I probably have to reboot due to problems every month or 3.

Wow, three/3 months! I wished mine go that high!


Why do you care? What would be the value of doing it that seldom? I
probably boot about once a week or so, and that's more than infrequent
enough for me!

Not very long ago, I used to boot once a day, every morning. I would
get out of bed, shower, get dressed, turn on my computer, and go into
the kitchen to make my coffee. When I got back to the computer, it was
done booting, and that was fine for me.

On Sat, 28 Mar 2015 00:57:38 -0700, Ant wrote:


I probably have to reboot due to problems every month or 3.

Wow, three/3 months! I wished mine go that high!


Why do you care? What would be the value of doing it that seldom? I
probably boot about once a week or so, and that's more than infrequent
enough for me!

Not very long ago, I used to boot once a day, every morning. I would
get out of bed, shower, get dressed, turn on my computer, and go into
the kitchen to make my coffee. When I got back to the computer, it was
done booting, and that was fine for me.