(09-07-2024, 08:57 PM)Pete Wrote: It's a temp thing these days, because MS control your life. So if you want to change the date and time about all it's good for is creating or saving a program with a manipulated date and time stamp. Oh, and of course time travel. Look, it's 1992 again!
Pete
- Win 3.1 Forever!
Edit: On another note of interest, why can't the boneheads who sync the time function get it right? The older a system becomes, the more minutes your system clock goes off. Mine is 10 minutes behind.
If you go into the registry, hunt for: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\W32Time\TimeProviders\NtpClient.
Right click on the SpecialPollInterval key, then click Modify.
That's the time -- in seconds -- between when syncing happens. You can set the date for 01-01-0001, and it won't matter. In XXXXX number of seconds, you'll sync and reset the time, or else a vast majority of windows based software won't work properly anymore.
If you want to disable time syncing, simply go into Firewall and Disable UDP port 123 -- that's the one which Network Time Protocol uses to connect and sync times with. (NTP Services)
So ...
1) block UDP port 123
2) compile my code above
3) run as admin
4) change your time
OR..
1) Change it via Windows, like most normal folks would.
And if looking at the above doesn't make folks realize WHY QB64 doesn't perform such actions, I dunno what to tell ya. Personally, I don't think I'd want a basic programming language, or a 1-line command, screwing with such deeply embedded policies and settings and such on my stuff.