From: Peter Laws
I've noticed the same issue (running Meinberg's build of NTP) with the
same amateur radio program where the PC is a certain number of seconds
off (4 or 6 or so or whatever but on the order of what the OP
reported). A restart of NTP "fixes" it. This happens after a cold
boot and even if I let the system run for an hour, NTP never fixes
things.
You've reminded me that I need to check if I did, in fact, disable the
Windows Time service (whatever it is on W10). That's much more likely
to be the issue rather than NTP.
Peter Laws | N5UWY | plaws plaws net | Travel by Train!
==========================
Peter,
You might also check that NTP is working correctly. Have you used the
"ntpq -pn" command? If your PC is out by more than 500 ppm (43 seconds a
day) special steps are required for NTP so that it corrects such an
inaccurate clock!
73,
David GM8ARV
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-tay...@blueyonder.co.uk
Twitter: @gm8arv
_______________________________________________
time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe, go to
http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com
and follow the instructions there.
