On Thu, Dec 08, 2011 at 12:50:12PM +0000, Dave Hart wrote: > The results are worse than FreeBSD or Linux I suspect the difference > is mostly due to the interpolation code having to guess at when, on > the counter timescale, the system clock ticked up to the present > value. Some ugly busy-looping logic might help refine that and also > overcome the incompatibility with newer Windows versions' clocks.
It's a pity the system doesn't provide a function for precise clock reading. What resolution has the clock frequency adjustment? I'm reading about the SetSystemTimeAdjustment function and the adjustment is in 100-ns units applied over an lpTimeIncrement interval. If the interval is too short I suspect this could also limit the time and frequency accuracy of the system clock. -- Miroslav Lichvar _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
