I have a Windows Task where two triggers are defined: one to run upon logon and another to run every hour thereafter at 55 minutes of each hour. This value is applied at the time of logon and the system time offset will be continuously monitored to see if an adjustment is required of this value.Īs can be seen in the log, the program is run every hour. If my program is run in 1-hour intervals, it will usually find an optimum SystemTimeAdjustment value in several hours and record it in NTP_TimeSync.ini file. With 4, the clock runs a little too fast with 3, it runs a little too slow. I found that my desktop needs 3 or 4 units of spike in SystemTimeAdjustment value for a typical day. The program must have updated the ini file as well.
This is the seventh line which shows that my desktop's clock was running too fast now and the SystemTimeAdjustment value was reduced by 1 unit. This number(4) was picked up from an ini file, which is created when this program is run for the first time.ĩ 11:55:02.322 Offset: -0.017 second(s), GGL Latency: 55.908 milliseconds*3 This means the system time will gain 23.04*4=92.16 milliseconds every hour. *4 at the end of the line indicates that periodic time adjustment was enabled and my desktop's clock was set to run at the rate of 4/156250 faster than the default time keeper, by using _Date_Time_SetSystemTimeAdjustment() function. It took 59.505 milliseconds to fetch NTP time from Google time server. The desktop must have picked up the initial system time from its CMOS clock and it was 360 milliseconds ahead of the NTP server time. This is the first line which shows that my desktop was turned on at 6:16 in the morning and it's system time was sync'ed to NTP time. Created by my NTP_3, this log shows what the program does.ĩ 06:16:53.887 Offset: -0.360 second(s), GGL Latency: 59.505 milliseconds*4 The following is time sync log of my desktop for a typical day. I am pretty sure that my desktop's system time is always within 20 milliseconds of NTP server time. I came up with this program and I am satisfied with it. I wanted my desktop's system time to be as accurate as possible without consuming too much of resources. Usualy it gains or loses several seconds a day. The time-of-day clock in any desktop or a laptop computer does not keep the time very well. I especially thank his kind help and guidance. I learned a lot from my earlier post in General Help and Support section.
0 kommentar(er)
