I will investigate how to submit this document to the Pulitzer Prize committee. Failing that, perhaps a note to the Guinness World Record people for the longest technical manual ever written by a volu

Bob and Keith, Bob's suggestion worked for KB2SSE, but only after I used upper-case letters, as shown in Bob's response. 73 and thanks, Jan, KX2A

Bob, I changed the host address to above (added the dxc and port=23) . That worked. ALSO Ken, KB2SSE, please send the proper remote host address and port. 73, Jan, KX2A

Bob, I followed your recommendation to clear the TCP/IP stack, and finally, to dry the reverse beacon setup. The former did nothing, the latter worked, along with DXFUN . However, the following did no

Bob, I tried GB7UJS. Nothing happened, so I hit return. Here is what appeared: I then tried VE7CC, using http://www.bcdxc.org/ve7cc/ as the address and port 23. This is based on a recommendation by Da

Bob, I have K3LR as my default, using port 73. However, I also have K2LS in my connect list, and when I tried that, nothing happened, meaning that the message: 'telnet dx K3LR.com' remained on the scr

I recently reinstalled Logger32 after a problem. Everything now works except the Telnet sign-on to a spotting host. I have some hosts already set up, but nothing seems to happen when I attempt to sign

JA1NLX, Thank you very much. Somehow, wrong boxes got checked. All if well now. 73, Jan, KX2A

I have been uploading to LotW for years, and now, suddenly, I uploaded and then a day later I downloaded the latest QSLs, and ALL of them ended up in LOTW-mismatch.txt. I tried again at the download a

Bob, Sounds interesting to me. I would love to find out more about FSTing. 73, Jan, KX2A

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