• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

w2k uptime

jema

Senior member
Is there any way of tellign how long a w2k machine have been up and running? I though one might find out in the system information window but that was a no-go.
 
I asked the same question a few months ago, and this is the file the guys here pointed me to. Works great -- just run it from a command prompt.

Uptime

-RedFox1
 
another way, but doesnt work if you login/logoff a lot, is just do a ctrl-alt-del and it will show you your login time
 
You can look in Taskmgr under Processes. System idle time will give you a good approximation. If you have your machine running background tasks just add the few largest ones and you will get a pretty good idea.
 
if you're running dual processors you need to halve that time, because the system idle proc will show the time for both processors combined. my record on my dual-proc machine is close to 4 months under regular daily use without a reboot.

-syf3r.
 
24 days uptime is ok for win2k - you'll find that you have to restart because you need to add/remove hardware more often than windows crashing. But just because windows can run for several months w/o rebooting doesn't mean you necessarily should. It's a good idea to reboot every week or so (every month on linux) to prevent problems.
 
See how long the **RC5 service** has been running. 🙂

I have a few NT4 workstations that I reboot every 45 days or so, just for kicks.

-SUO
 
Back
Top