A fix is currently being verified by the Beta group. Will be in the next autoupdate. Jim – w5ifp-

Same here, disable tracking until fix is out.

Is your Telnet callsign the same as the cluster callsign? Don't know if this matters but mine are the same and telnet populates the dxspot window here. 73 Jan (hi)

Thanks Bob for implementing <ESC> to DVK. Work fine. I do have more request when you in the mood to do it... 🙂 1-Can we have more buttons. Twelve would be nice to have or as many as in CW

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. 

Jan, Did you press <Enter> after your !callsign? Jim – w5ifp-

Jan It looks DX spot window not working. Try virgin Logger32.ini and see whether DX spot are displayed in DX spot window. Virgin Logger32.ini ? Yes look for Logger32.ini in Logger32 folder. Rename

Just go to the obvious place, the source of the application: http://www.dxatlas.com/Download.asp Scroll down to Ssn.dat

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,

Gary, Thanks for the reminder. However, the link you referenced is pointing to data from VP9KF's "guesses" in 2018. I would recommend instead using the updated SSN number info for Hamcap directly from

These are the settings in my OLD .INI file Logbook Page Index = 45 Logbook page Index column = 0 I will play again tomorrow, it's bed time here. Many thanks for the help so

Ken Delete Logger32.ini. Rename Logger32.ini.OLD to Logger32.ini again. Open Logger32.ini with text editor. Maybe something wrong in [wndLogbookPage Settings] section.

That works ok. Now how do I find the difference in the two INI files?? 73 Ken

Ken Try with virgin Logger32.ini. Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD. Run Logger32. Try edit in Logbook page window. How now ? 73

I should add that I have done this lots in the past without trouble. 73 Ken ZL4NR

Yes I see the same, but then I can't edit anything. As soon as I click on a box to edit it, the logbook page just goes back to the latest QSO entered. 73 Ken ZL4NR

Ken What you see when you click any line. I see the line highlighted with Yellow back color. This color depends on your setting. 73 -- 73 de

If you use the add on HamCap program for propagation prediction, you may find that it doesn't work beyond December 2019. That's because the predicted sunspot numbers within it ended in December

Using version 3.50.408 on W10 Home desktop computer. I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change

I have been running the latest update (v3.50.408) on Windows 10. I noticed that even though I have WAZ credits in all 40 zones, the Spots Window highlights are indicating that I need many zones for