Re: Windows won't settle
- From: "David J Taylor" <david-taylor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Apr 2006 04:13:30 GMT
Richard B. Gilbert wrote:
[]
Windows is simply not very good about keeping time! It can lose clock
interrupts when busy. Starting and stopping the multimedia timers can
mess up the clock.
W32TIME is an implementation of SNTP rather than NTP. It's not even a
very good implementation of SNTP. You may get better results with NTP.
Then again, Windows being Windows, you may not.
For an example of what Windows can do when running a recent version of NTP
(which takes the multi-media clock behaviour into account) and syncing to
a local stratum one FreeBSD server (top graph), please see:
http://www.david-taylor.myby.co.uk/mrtg/daily_ntp.html
W32time, at least in its older incarnations was not good, but for many
purposes today time-keeping in Windows using NTP is quite adequate.
David
.
- Follow-Ups:
- Re: Windows won't settle
- From: David Rush
- Re: Windows won't settle
- References:
- Windows won't settle
- From: David Rush
- Re: Windows won't settle
- From: Ry
- Re: Windows won't settle
- From: David Rush
- Re: Windows won't settle
- From: David Rush
- Re: Windows won't settle
- From: Richard B. Gilbert
- Windows won't settle
- Prev by Date: Re: Windows won't settle
- Next by Date: Re: WWVB 60kHz Receiver
- Previous by thread: Re: Windows won't settle
- Next by thread: Re: Windows won't settle
- Index(es):
Relevant Pages
|
Loading