On 05/12/2018 03:52, Jim Shorney wrote:
NTP is a mature protocol and has been doing it right for years. Windows is late
to the party.
73
-Jim
NU0C
Hi Jim,
that's not really correct. Windows Server variants have had an NTP
client for many years, it is that client that is being shipped with the
latest Win10 builds as far as I know. I suspect that the reluctance of
MS to provide high accuracy clock setting on desktop Windows variants is
because they would also have to provide a robust and Worldwide network
of time servers like Apple do for the masOS community. Operating systems
like some Linux distributions have such networks which rely on the
commercial paid for variants to fund such services (Red Hat Enterprise
Linux and SuSE Enterprise Linux for example). Also individual home users
can select local NTP servers from public network like the pooled servers
offered under the *.pool.ntp.org domain name but these servers are not
really available for free commercial use so if MS were to ship a high
accuracy NTP client with Windows and advised users to use an ntp.org
service for time setting then the ntp.org operators would soon take
steps to stop such freeloading from a commercial entity like MS. Time
servers are not cost free, they need hardware and bandwidth and
ultimately atomic clocks which are definitely not cheap.
Anyway, reading the link Dana kindly posted, it is hardly a simple
facility. You must edit several registry values just to get it working
and it seems very unpolished for a desktop offering. If MS are
automatically disabling 3rd party NTP time clients in favour of that
then shame on them. They need to make it far more user friendly. I
wonder if they are still trying to discourage the higher NTP network
traffic that would be generated if it were as easy as clicking a tick
box in the settings.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
