Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km. Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged

Jim, Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correc

Apparently this problem has a mind of it's own. The LY28A callsign now works to store the distance. I tried different bands and different modes. I also tried logging a qso with the internet disconnect

Dan, Good try, but not the issue here. These were directly logged in L32. When I import logs from my contest logger, the Distance field is left blank. Actually, I wish L32 did compute the distance whe

Steve, It worked OK here. I think the error you got indicates a download timeout. Try again.

Jack, The K3WW cluster might be down at this time. Try a couple of different clusters. There are always new ones coming online and others being closed or down for a failure or maintenance.

Jan, You can turn off out of band messages through the menu by disabling this option: View/Enable Out of Band Messages

Jan, Now you have my curiosity up. How was the issue resolved?

Fabien, Perhaps until a change is made to the program, you could log FT8 qsos in a new, separate logbook and continue to log CW/phone qsos in your existing logbook. You could even add a third logbook

Glen, This whole topic always makes my head spin and once I get mine working OK mostly by trial and error, I leave it alone. Perhaps the following might help you. QSL Rcvd only reflects paper cards. I

Perhaps there is some minor corruption in your log file. First, try Recalculate statistics to see if that fixes the problem. If that doesn't work, export your entire log to an ADIF file. Create a new

Andy, I think we need a bit more context. What program? What were you doing? Do you know which software generated the error? .... Other than that, a quick Google search shows that this could apply to

My preference is to turn off all of the automatic formatting and leave it off. It works great. I get what I type and I can edit things as I like.

JC, Typically, your description is symptomatic of Windows 10 power management where it turns off power to certain devices if it decides they are no longer active. That is controlled under the Power Ma

Aki, I think he meant this: "A few days after upgrading to latest version - 358, I checked ..." The difference between I and 1 is difficult to see in some fonts.

Gary, Those are indeed the solutions, but the source of confusion, at least for myself and Mike, is that doing what I thought was a one time Clublog exception cleanup left over 2,000 invalid call exce

Gary, I understand how it is being implemented, but removing over 2,000 entries by hand is not practical. Not only that, they would reappear if I ever wanted to do a log review using Clublog info. Hav

Delete the .chi file. It is no longer used with the newer help files.

Mike, Deleting them from "Tools > Setup Bands and Modes" will get rid of them. I haven't yet found a way to only disable the modes in the Worked / Confirm window.

Jim, I don't have a solid answer for you. However, after making sure I had backup(s) just in case things got worse, I would try the following, 1. Sort log by callsign. Presumably a blank callsign will