[]
David Taylor is right that it is normal for Windows to keep running
the clock at whatever rate was last set after the program setting the
rate goes away. It's also true that Windows does not have any rate
limits itself -- you can easily tell Windows to advance the clock 1
usec per tick (nominally 15.625 msec), one hour per tick. Unless I
misread the nt_clockstuff.c code, it shouldn't be possible to get ntpd
to set the Windows clock rate more than 500 PPM from nominal.
Thanks,
Dave Hart
Dave,
How does NTPD_TICKADJ_PPM affect this? If that was set to -800, for
example, wouldn't the adjustment range be -300/-1300 rather than +/-500?
Or are you including NTPD_TICKADJ_PPM in "nominal".
Thanks,
David
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
