Hm, but how much is 390hrs? Ok, i can just divide by 24, but i think the computer can do this much faster!Would it be possible, to also show the days instead of only hours?A simple command-line-version would also be nice .-)

The only trouble is that the Windows system clock wraps at 2^32 milliseconds, which is 49.7 days (1193 hours), so the days counter would never get above 49. There _is_ a possibility that I could compare the millisecond timer with the other internal clock, which runs in seconds since 1970. This would require that I save a file showing the difference of these two to disk. If the program runs, finds this file and then sees that the difference between its value and the current one is close to a multiple of 49.7 days it could then adjust the readout accordingly. This wouldn't be totally bulletproof though (e.g. what if you restarted you computer after exactly 49.7 days and ran the app again?) so for now I'll just upload the one with days counter.

"As every 11-year-old kid knows, if you concentrate enough Van-der-Graff generators and expensive special effects in one place, you create a spiral space-time whirly thing, AND an interesting plotline"

The uptime counter now reads in days when the number of hours is 24 or more.

"As every 11-year-old kid knows, if you concentrate enough Van-der-Graff generators and expensive special effects in one place, you create a spiral space-time whirly thing, AND an interesting plotline"

Just save the executable to your %systemroot% directory for easiest use.

quote:The only trouble is that the Windows system clock wraps at 2^32 milliseconds, which is 49.7 days (1193 hours), so the days counter would never get above 49. There _is_ a possibility that I could compare the millisecond timer with the other internal clock, which runs in seconds since 1970.

Stephen, do you know how exactly the uptime executable from MS runs? My uptime at home is over 49 days, and the Microsoft program reads it correctly. Also, I thought that this resetting bug was fixed in Windows 98SE, and hasn't been an issue since.

--The mark of an educated man is one who knows a lot about something, and a little about everything.

There's actually an improved 64-bit counter supported on a lot of computer boards. The current version of uptime I have reads from it, if present, so won't wrap for years. I forget to post that upgrade to this thread though - maybe I discussed it with someone else via e-mail.

"As every 11-year-old kid knows, if you concentrate enough Van-der-Graff generators and expensive special effects in one place, you create a spiral space-time whirly thing, AND an interesting plotline"

"As every 11-year-old kid knows, if you concentrate enough Van-der-Graff generators and expensive special effects in one place, you create a spiral space-time whirly thing, AND an interesting plotline"

Update: I've added a version that works as a popup counter in Windows, and also corrected the negative milliseconds bug in both versions. The desktop version isn't 100% perfect but it works for most normal use, and doesn't take up much CPU (<1%) when you have it running in the background. Be careful not to start 2 instances though. See prefs.txt file for configurable options.