On 22/07/2014 16:53, Nick wrote:
[]
ntp runs well on Mint 17 and the drift is reported to be -17ppm.
ntp does not run well on Win 7 x64 and the drift is reported to be +493ppm.
What makes ntpd think that the frequency error on Windows is +493?
[]
Any ideas chaps?
Nick, I have seen (some tim
Hi--
On Jul 22, 2014, at 8:53 AM, Nick wrote:
> The box is very lightly loaded.
>
> ntp runs well on Mint 17 and the drift is reported to be -17ppm.
That seems to indicate that your hardware is sane and reasonable timekeeping
works fine under some platforms.
> ntp does not run well on Win 7 x6
On Tue, 22 Jul 2014 10:53:52 -0500, Nick wrote:
>> What have I missed?
> ntp does not run well on Win 7 x64 and the drift is reported to be +493ppm.
Thats on the edge! How much do the computer loose/gain when you do not do
anything
to adjust time?
NTPD requres drift to be within +-500ppm.
/hjj
_
On Tue, 22 Jul 2014 10:53:52 -0500, Nick wrote:
> The QPC execution time for 100 calls varies between 26ns and 37ns.
(typo)
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
> What have I missed?
Having read all the recent posts I have installed 4.2.7p450 binary from
satsignal.eu to run with -M switch.
Disabled the following drivers;
- delta 44 soundcard
- pe0fko Si570
- com0com
Everything else looks standard; I'm using the on board Intel G31 graphics,
and the dis
In article <84lv9b-i5v@ubuntu-server-1.py.meinberg.de>, Martin
Burnicki wrote:
> Nick wrote:
> > Brian
> >
> > thanks for your useful reply...
> >
> > On Fri, 18 Jul 2014 02:03:48 +, Brian Inglis wrote:
> >
> >> Windows is using the MM timer as its high precision time source, not PM
> >>
Rob wrote:
Martin Burnicki wrote:
Except what I've mentioned before I have had rare cases where the
Windows timekeeping was generally broken due to some drivers.
If I remember correctly then one case was a hard disk driver, and a some
latency checker program was used to show that the driver ha
