So I did a bit more research. I had a look at a couple of Windows 10 systems that I haven't tinkered with the W32Time settings for, one crusty old slow notebook with slow WiFi, and one fairly new, fast notebook with fast WiFi. The Win 10 machine I use for WSJT-X is connected to the gateway router via 1Gb Ethernet.
[ Clarifying, I don't expect 1mS precision with _only_ the suggested registry changes, for all the reasons you mention. I do anticipate something on the order of ~ 50mS without infrastructure changes, though. ] Both of them were powered-on a few hours before I looked at them. Both of them were reported as being ~ +2.1 seconds by time.is. I had a closer look at the crusty old slow notebook; sure enough, the W32Time service is set to 'Manual' start and wasn't running. Here are the original settings for the W32Time registry values: MinPollInterval: 10 MaxPollInterval: 15 UpdateInterval: 360000 FrequencyCorrectRate: 4 and the NTP Client: SpecialPollInterval: 604800 Of course, these values are in various units that I really don't claim to understand - no claims to being a Windows expert from me :-) One thing I often do on the Win 10 machine I use for WSJT-X is manually do Internet time sync before launching WSJT-X (historically to time.nist.gov, but I'm now using time.microsoft.com, and I suppose I could look at pool.ntp.org). So I did this on the crusty old slow notebook, and (a) time.is says ~ +43mS and (b) W32Time is now running. So I went ahead and made the registry changes to the crusty old machine, rebooted it, and first look, it was ~+35mS. With the 'high accuracy' changes, my wired Win 10 box reports ~ 5-10mS difference the few random times I've looked. Sure, registry changes are not for the feint of heart, but they're not that hard. Cheers & 73, Dana K6JQ
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
