More likely just a bad decode. They can look very convincing. 73 -Jim NU0C "Arthur Bernstein via groups.io" <n2ka@...> wrote:

I would be curious if people are going into the Windows clock setup and using the "Internet" time tab to pick a reasonable government time server ( assumedly Windows is using NTP ) to set

When my uncle bought one of the early LED watches back in the mid 70s the instructions included a phone number for WWV to accurately set the time. "Oh, yeah, I can get that on the radio" said the

Cool. I didn't know about the time fudge software. Next time I'll suggest that. As for the elevated privileges I didn't think about that being an issue. Jul 27, 2020 at 09:01 AM, Kai-KE4PT wrote:

45+ years ago. I used it when I was in a small radio station (with no network affiliation or audio wire) back in the 1970's. 73, ... Joe, W4TV

Perhaps you did not get that there are circumstances where GPS or LAN connections are not practical. The club shack I administer is one. This does not hamper operation in the slightest. What do you do

Speaking of weird decodes, on July 14 at 1819Z I was called by B0CHR, PP34 and was given –13 report. Oh yes, it was on 6 meters. PP34 is Siberia near Manchuria, I think. B0 should be China. Someone

Looks like a good contest message. 212130 -time -24 sig stength TU: - thank you WF8EWD - callsign 1 U.S. OE9XUQ - callsign 2 Austria (neither seems "strange") R 579 - signal report 0782 -

got a really long decode yesterday 212130 -24 TU:WF8EWD OE9XUQ R 579 0782 I did have AP on - but that takes a lot AP imagination ??? this was 50.313 1965 Hank K7HP

eoh is already there :(

I copied from VE3KI earlier message: Start WSJT-X. If the error message appears, just click on OK and continue. Use the "File > Open log directory" menu item in WSJT-X to open a file manager window

Ronnie, all you need do is a simple edit on the WSJT-X ADIF log file. Change the header line where is has <eh> to <eoh>. The issue is due to a defect in WSJT-X v2.2.2 when

IM going to go back too. I installed 2.2.2 and every since then when I load it I get a .adi error. It never saves the .adi apparently, and every time I run it now it has lost what countries, grids and

Darn . .hit send before I finished. Here's the rest: I have made an update to my WSJT-X BRIDGE so that all DXbase users can use my BRIDGE all ok - with the new WSJT-X ver 2.2.2 program .. To use

Um .. I did a Google Search on DXBase and WSJT-X, and found this: Joe WA6AXE's WSJT-X BRIDGE (newest version) -- is NOW usable with WSJT-X ver 2.2.2 On 7/27/2020 6:04 PM,

On 28/07/2020 00:04, N2TK, Tony via groups.io wrote: Hi Tony, you can download installers for previous versions of WSJT-X from the project Source Forge files area:

I want to go back to an earlier version of WSJT. Trying to figure out why I don’t auto-log into DXBase anymore using WSJT-X ver 1.80 to DXBase Bridge.exe. By going back I hope to find out if it is

Solution found – upgrade to V2.2.2 Mark Lunday, WD4ELG Greensboro, NC FM06be wd4elg@... http://wd4elg.blogspot.com SKCC #16439 FISTS #17972 QRP ARCI #16497

Wow! Thanks Richard, I did not realize that WWV had added the time by phone. Call connected, verified right on time with atomic clock - phone # added to phone contact list. Thanks again. 73 - John -

On 27/07/2020 23:26, M Lu wrote: Hi Mark, such a feature would not be practical for a QSO mode with less than 3 seconds idle between Rx and Tx periods. 3 seconds latency is