I tried to update to the latest Logger32 version, and had a number of error messages. The result is that I no longer have a working Logger32. I had failed to make a backup ADIF, and my rollback says i

I am one of those who lost Logger32.exe and recovered it from the most recent update files folder. Then it disappeared again. This time I went to its properties (right-click on Logger32.exe and select

Bob, I followed the link, went to "Virus Threat & Protection." Next step is to click "Protection History," but these words and this link do not exist on this page. Also, under under "Windows Defender

I am pretty dense and need explicit instructions to do things. Here is what I plan to do: Rename the Logger32 folder to Logger32.bak Reinstall from the Logger32 site, using the full version of Logger3

I use AVG for virus control and Windows seems to recognize that and does not do virus checking. AVG has an easy way of seeing quarantined items, and there have been none since2018. If Windows did it,

I found Windows security, but do not see such a notice. Where should I look once I am at Windows Security? Jan, KX2A

I was operating JTDX under Logger32, and when I worked someone I received a message about a communications failure. When I tried to go to the open Logger32 logbook, nothing happened. I then found that

There is a reset. Left-click File > Settings > Frequencies put the cursor in the upper left pane and right-click. It is the bottom choice. I just went through that again and had to be retold the metho

Here is another follow-up. I managed to get DX spots working again. I had entered PSK in the Setup Bands and Modes matrix, but failed to put in a frequency. This caused the failure of the spots to ent

JA1NLX, I renamed Logger32.INI (sic) to Logger32.INI.old. Logger32 started as if it were the first time. I connected to K2LS, which was already in Telnet, and did a sh/dx in the telnet window. A dx li

JA1NLX, I typed !KX2A into the callsign field in the entry window and nothing happened in the DX Spot window or in the telnet window. That is an exclamation point in front of my callsign. 73, Jan, KX2

Jim, I followed these links: DX spots-> Setup -> DX spot -> blocking/pass filters -> tabbed display. I created the following: Spotting cont. : no checks Destination cont. : no checks Band: blocked 60

When using Logger32 (any mode, not just FT8), DX spots show in the Telnet window, but no in the DX spots window. However, the DX spots window shows when a WWV or propagation announcement is made. "Hol

I have JTDX V2.1.0-rc148, and I use it with Logger32, Version 3.50.308, which was downloaded this morning. It was working for me yesterday. Suddenly, today several things have gone wrong. First, the w

Bob, Your additional suggestions came up while I was trying alternatives and typing. I tried your first suggestion and it seems to have done the trick. I will look over the second one and try that lat

It just dawned on me to try DIG. That works, and now there is a column called DIG. In my case, it means FT8 and RTTY are both digital. Ah well. 73, Jan, KX2A

Bob, It just dawned on me to try DIG. That works, and now there is a column called DIG. In my case, it means FT8. 73, Jan, KX2A

Bob, I used the term RTTY, since, once upon a time, that was the ARRL's alternative for all digital modes. Things have changed, and I found, after much hunting, this document page: https://www.adif.or

John - G7SSE Mea Culpa, my typo, FT8 is in the 20 meter row, and yes, there is a Y in the stats column for 20 meter, FT8. The Radio Mode is RTTY, as it is for all modes that use TX DATA in my K3. So m

Is there a way to put FT8 as a column in worked/confirmed, similar to the PSK column? I already have FT8 entered for 40 meters in the Bands & Modes chart, but this did not result in a column in worked