Uptime wraps after 50 days

[LoRenZoR]

Hi!

I have registered last weekend, because i wanted to show a bug, that i've found in v7.04. I wanted to show the bug on a screenshot, but i couldn't post a message with a link because of the restrictions. I hope it will work now. (I couldn't even send a p.m.) I just paste the message here, which i originally wanted to post:

"My computer is running since 50 days. Today morning i've checked the "time since Win start" in "Commands/System Information..." and there was "1179 h" written. Later today i've checked it again, and now i only see x h (instead of 118x h - as you can see on the screenshot). I think the program doesn't shows the uptime above 1180 hrs properly. For a proof i've included an event log information too."

Sorry if i've posted this in the wrong topic but i don't wanted to create a new for this. I hope my post will be useful.

I still can't make a link (no other post yet), so i'll will include it in the next post.

[sqa_wizard]

2LoRenZoR This is a windows bug/feature as you like.

See TC help 3.c: Commands - System Information - Dialog Box - Software

Code: Select all

Time since win. start	Elapsed time since Windows was last started. Unfortunately, the counter wraps to 0 approx. every 50 days.

[LoRenZoR]

Sorry, this is the first time that i saw that happening. I wanted to ask about it in a p.m., but it isn't allowed here... Thanks for telling that information.

[karlchen]

Hi, LoRenZoR.

The title of this thread reads Strange bug with archives. I really do wonder how the Windows uptime may be in any way related to this topic?

So it would have been nice not to hijack a random thread and add your question(s) here, but open a new thread instead. - Just a hint for future reports.

Karl

[Hacker]

[mod]Thread split from Strange bug with archives.

Hacker (Moderator)[/mod]

[LoRenZoR]

Karl, you can blame me for posting in the wrong topic.. But like i wrote before, i just wanted to ask (the author) about it in p.m., don't wanted to post it anywhere. What's the meaning of disabling p.m.s anyway?? Sorry! Nevermind... I would never guessed that i can found something about this bug in the help... And why is it a windows bug? There's an other program called l33tsig, maybe you've heared of it (the service is currently offline due the upgrades), and there's nothing wrong with the uptime counter. If it's a windows bug, wouldn't it be buggy there too...?
Sorry for my bad english! (It could be the reason for my post in the wrong topic.)

[karlchen]

Hi, LoRenZoR.

If your read my post carefully, you will notice that I used the term "Windows uptime" only. I did not blame either Windows, nor TotalCommander for doing anything the wrong way. So I have not stated it were a Windows bug.

Yet, SqaWizard's reply indeed suggests it is a Windows limitation.

Regards,
Karl

[icfu]

49.7 days is the limitation of GetTickCount function. The time is stored in a DWORD (32 bit registry value) which overruns after that time.

An alternative function is only available starting with Vista/Server 2008. As almost noone uses Vista, even less run Windows for longer than 49.7 days and among those almost noone will ever complain about a reset after that time, I would guess that a switch to GetTickCount64 is a scenario which can be expected for TC 27.0 at best, if ghisler should still be alive at that time and todo list should be empty, which will probably never happen.

Icfu

[Horst.Epp]

Hi!
...
"My computer is running since 50 days. Today morning i've checked the "time since Win start" in "Commands/System Information..." and there was "1179 h" written. Later today i've checked it again, and now i only see x h (instead of 118x h - as you can see on the screenshot). I think the program doesn't shows the uptime above 1180 hrs properly. For a proof i've included an event log information too."

Sorry if i've posted this in the wrong topic but i don't wanted to create a new for this. I hope my post will be useful.

I still can't make a link (no other post yet), so i'll will include it in the next post.

Use "net statistics server" on a command line for correct information.
Thats not an importand function of TC at all.

[LoRenZoR]

Thanks for your advice Horst.Epp, i didn't know about that command till now. But why have you suggested it? It doesn't shows me much intresting information. Besides, i know that the uptime counter is not an important fuction of TC, it's just about that i tought i can show the author something he doesn't knows about. If i would have known that he already knows about that, i would not have bothered. TC works fine for me, even without that would be changed.

And Karl, it was about SqaWizard's reply...

[StatusQuo]

It doesn't shows me much intresting information.

It shows the date when the PC was last (re)started - instead of the time elapsed since then (like TC).
(Tested on W2k SP4 and XP SP2)

Maybe that could be an alternative for TC's system info in a future version as well?