Or do like myself and others do and run the Windows only software in a
Windows VirtualBox VM on Linux.
73
Stan
KM4HQE
On 12/5/18 8:27 PM, Topher Petty wrote:
The solution is simple: For Amateur Radio, dual-boot into Linux and
give Micro$oft the finger... When you need to do something that you
can only do in Windows (what, I don't know... other than MMORPGs and
the like), boot back...
On Wed, Dec 5, 2018 at 8:41 PM Kevin Utzy <krutz...@gmail.com
<mailto:krutz...@gmail.com>> wrote:
I was wondering trying to read this thread. What I haven't been
able to discern is whether or not, if I can turn off the windows
time update and use the USB GPS dongle I have been using. My new
Win 10 machine is coming tomorrow and I would like to know a head
of time if this is going to be a problem?
73,
Kevin
KX4KU
On 12/04/18 8:59 PM, Dana Myers wrote:
On 12/3/2018 7:13 PM, Matt Power wrote:
WSJT-X on Windows has generally expected that the machine has
third-party NTP software and doesn't use the Windows Time service.
This strikes me as perhaps dated with respect to Windows 10.
My Win 10 Pro box here (1809, 17763.134) runs the default Windows
Time Service,
always has - configured to 'set time automatically'. Every now
and again I'll look at
time.is <http://time.is> and it'll say I'm within 15mS. I just
powered-up a Windows 10 Home notebook
that has been powered-down a while; it was off 2 minutes, but I
did a manual
'Internet Time Sync' and it seems to tracking well (I suspect it
might have been
skewing back on-time and I kicked the process along).
[I did select time.nist.gov <http://time.nist.gov> as my time
server on one system, but time.windows.com <http://time.windows.com>
seems functionally as good]
Note that Windows 10 (version 1607 or later) documentation says:
"Time synchronization in Windows 10 and Windows Server 2016 has
been substantially improved. Under reasonable operating
conditions, systems can be configured to maintain 1ms
(millisecond) accuracy or better (with respect to UTC)."
but the *default* configuration isn't intended to provide that
level of accuracy:
"While we support accuracy up to 1ms on Windows 10 or Windows
Server 2016, the majority of customers do not require highly
accurate time."
But they explain how to configure your Win 10 system for high
accuracy:
https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/configuring-systems-for-high-accuracy?tabs=MinPollInterval
I'm going to give the 'high-accuracy' changes a try; I might
change time server
to time.windows.com <http://time.windows.com> to avoid hitting
NIST too often.
Odds are that you're better-off using the built-in Windows Time
Service than
a third-party service on Windows 10 version 1607 or later. Fewer
moving parts
is always better.
73,
Dana K6JQ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
<#m_6762173437814110396_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
