Yeah, the one thing I have wondered about is all the the version to version -X
variance in protocols that are out there right now. How does everyone know the
decode failures are related to DT and not 72/75/77 bit issues? Checking
against Time.Is my computer's are always spot on and I almost never see a DT of
zero. I also don't seem to have decoding problems.
I use Net Time Sync on both Win 7 and Win 10 machines for both terrestrial and
EME FT8/JT65.
Anyway, following the thread with interest and hoping we do not over,- engineer
the solution when the cause is a bit unclear
John
Sent from my Verizon Motorola Smartphone
On Dec 5, 2018 6:30 PM, David Fisher <dsfis...@outlook.com> wrote:
>
> Since I apparently put the match to this issue, I’m going to run an
> experiment.
>
> I normally run my Win 10 Pro (homebuilt) computer with the Meinberg NTP
> service. It has worked extremely well. But, it has also been said that the
> Windows service may be fine. So, let’s find out.
>
> I’ve disabled Meinberg on my computer and reenabled the WTS. I’ve verified,
> and will continue to verify, that these setting stick across reboots. They
> are. The hardware clock on this computer has some miles on it and runs a bit
> slow, so whatever time service I use, it has some work to do.
>
> Before someone jumps on it – this is Windows 10 PRO, not Home. It’s running
> 1809, and updates regularly as the patches come out. The system runs will and
> is reliable.
>
> I’ll keep an eye on “DT” readings and compare the system clock with WWV from
> time to time. I’ll report what I find. Maybe this is a tempest in a teapot.
>
> Dave / NX6D
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
