In that case, just change the default time server that Windows is trying
to use, to pool.ntp.org (works anywhere in the world you have
reliable* internet.)
Or.. north-america.pool.ntp.org If you're in the USA.
See
https://www.pool.ntp.org/zone/north-america and
https://www.ntppool.org/en/use.htmlUnless you have a really flaky CPU clock, or some other CPU hogging
issue, Windows own timekeeping service is more than good enough for the
JT modes where you only need to be +/- 1 second or better, so long as
you do not use the highly congested default time.windows.com (or
whatever) server they set it for by default.
(* Reliable and stable, not necessarily fast, and avoid mobile internet,
the latency is too variable.)
73.
Dave G0WBX
------------------------------------------------------------------------
For me, simple just ROCKS.
Rick nhc
On 09/10/18 13:29,
[hidden email] wrote:
> For me, simple just ROCKS.
>
> Rick nhc
--
Created on and sent from a Unix like PC running and using free and open source software.
::
______________________________________________________________
Elecraft mailing list
Home:
http://mailman.qth.net/mailman/listinfo/elecraftHelp:
http://mailman.qth.net/mmfaq.htmPost: mailto:
[hidden email]
This list hosted by:
http://www.qsl.netPlease help support this email list:
http://www.qsl.net/donate.htmlMessage delivered to
[hidden email]