If i remember correcty, then 'cmdwiz.exe gettime' should return the passed time since system start in milliseconds.
The return value is an integer, so you probably got an overflow, which is at least (uint) (-421671808) milliseconds, which is 44 days, 19 hours, 54 minutes, 55 seconds, 488 milliseconds.
If your PC didn't run that long, you should check your time and date (and if that has changed to a false value, then you should also search for a reason).
penpen
Cmdwiz - 54 operation cmd helper tool (now with Unicode)
Moderator: DosItHelp
Re: Cmdwiz - 54 operation cmd helper tool (now with Unicode)
Please, read my post carefully, I have posted actual date and time, and boot date and time. So you can simply see the data and possibly perform debug computation.
Re: Cmdwiz - 54 operation cmd helper tool (now with Unicode)
Above i only can see your Windows date and time, but your BIOS also tracks date and time on its own and depending on the function to detrmine time might affect the result.
penpen
penpen
Re: Cmdwiz - 54 operation cmd helper tool (now with Unicode)
am I understand it correctly, that your utility read boot, actual or both times from RTC, and not from OS??
Re: Cmdwiz - 54 operation cmd helper tool (now with Unicode)
It's not my utility, so without seeing the source code, I can only make more or less educated guesses. Therefore I can't say for sure that, what you described above, is caused by changes in OS and BIOS time.
I only can say that unexpected changes to date and time might lead to unexpected issues and software behaviour (though mainly with older software), so i would check that (given that checking that doesn't cost much time if BIOS and OS date and time didn't change).
penpen
I only can say that unexpected changes to date and time might lead to unexpected issues and software behaviour (though mainly with older software), so i would check that (given that checking that doesn't cost much time if BIOS and OS date and time didn't change).
penpen
Re: Cmdwiz - 54 operation cmd helper tool (now with Unicode)
Sorry fro that, for some reason I think you are an author :-/penpen wrote: ↑06 Jun 2024 17:18It's not my utility, so without seeing the source code, I can only make more or less educated guesses. Therefore I can't say for sure that, what you described above, is caused by changes in OS and BIOS time.
I only can say that unexpected changes to date and time might lead to unexpected issues and software behaviour (though mainly with older software), so i would check that (given that checking that doesn't cost much time if BIOS and OS date and time didn't change).
penpen
There were no 'unexpected changes' on my laptop. Utility display data correctly after reboot (resetting uptime), without any date/time changes.