PCMech Forums - View Single Post

Paul Victorey · 01-14-2002, 10:30 PM

I keep mine on 24/7 most of the time, I shut it off on the nights insomnia makes the fan noise unbearable.

I do agree that any 9x kernel machine needs a daily reboot; there are a lot of applications with miniscule resource leaks. But because two of the system resources (User and GDI heaps) are, for win3.1 compatibility, 16-bit, these are each only 64K of memory which every program running must share. If one program fails to play nice, it's not hard to burn 64 kilobytes and run out of system resources.

2000 and XP are, like NT 4, fully 32-bit, with no 16-bit addressed memory spaces, so for a resource leak to really matter, it would have to be quite huge. I'm running 2K now, I can probably get by with never rebooting except for when I shut down the machine to transport it somewhere, or rebooting for program installations.

I've had NT4 machines running 24/7 for more than 6 months without a reboot, or any problems at all.

01-14-2002, 10:30 PM	#25
Paul Victorey Member (12 bit) Join Date: Mar 1999 Location: MN or WI Posts: 3,017	I keep mine on 24/7 most of the time, I shut it off on the nights insomnia makes the fan noise unbearable. I do agree that any 9x kernel machine needs a daily reboot; there are a lot of applications with miniscule resource leaks. But because two of the system resources (User and GDI heaps) are, for win3.1 compatibility, 16-bit, these are each only 64K of memory which every program running must share. If one program fails to play nice, it's not hard to burn 64 kilobytes and run out of system resources. 2000 and XP are, like NT 4, fully 32-bit, with no 16-bit addressed memory spaces, so for a resource leak to really matter, it would have to be quite huge. I'm running 2K now, I can probably get by with never rebooting except for when I shut down the machine to transport it somewhere, or rebooting for program installations. I've had NT4 machines running 24/7 for more than 6 months without a reboot, or any problems at all. __________________ Paul M. Victorey ------------------ I am not responsible for any problems that may arise as a result of following my advice. This includes, but is not limited to, computer failure, loss of data, nuclear war, famine, boils, no clean laundry, your daughter running off with a biker gang, or armageddon. Take my advice at your own risk.