I assume an update will eventually cover this development. Regards, Mike VP8NO

Nothing but it isn't what was requested. See the original post. Regards, Mike VP8NO

Quite correct Chris, however, the request was for an upfront display of start and elapsed time during the QSO. Curiously one of the reasons I started using L32 was because I could arrange the logbook

Hi Gary, An undocumented feature! Well, one I couldn't find in the help file. I wondered how the on/off function of the Clublog exclusions worked. Regards, Mike VP8NO

And it would be a good idea to sort it out before the event instead of a real hullabaloo when it was in progress. From my perspective it can be worked around. However, whatever the inconsistency is, w

Good to see I'm not the only one. The simple workaround is to edit the country info after the first QSO has been logged. Right click on the logbook page QSO line and select "Edit Country info" and cha

Hi, See my post. It didn't work when I tried it. Regards, Mike VP8NO

Hi, I have usually updated the country/prefix database manually. I like to keep control and not outsource my log. If I try to add the specific call sign <3Y0Z> a error message pops up: "<3Y0Z> appears

This likely why one is often told not to plug in the cable until the driving software has been installed. Regards, Mike VP8NO

Not in my case. I switch the PSU off when I've done using it. I never leave anything on that I'm not using. It is stone cold dead, even the GPS locked reference oscillator on the same supply is the sa

Not with my K3 with the USB upgrade it doesn't and I use the USB port for all K3<>PC communication, CAT, audio, CW, PTT. I regularly start L32 without the K3 being powered, updates and the like. With

Have you included FT8 in your Tools > Setup Bands and Modes table and enabled stats? Regards, Mike VP8NO

Only FT8 QSOs logged via the UDP interface show this effect in my log. All other QSOs can have the "N" toggled on/off via the view menu option. I've never noticed because to show "N" was never selecte

Hi Kim, The QSO count maxes out at 1000 even when QSO totals are known to be much higher. Similarly if you left click on the individual mode headers. Regards, Mike VP8NO

Not wishing to rock the boat. I normally do but given the recent update issues downloading a 37MB help file just to read the recent "Helpfile changes" is not a good option for those on a skinny Intern

I'm currently sitting tight on .337 so before I go for this is .340 just .337 renamed and reissued or are there some other goodies lurking in there? The update notification only mentions UDP. Regards,

Hi, Just noticed something. With a call in the logbook entry window, clicking on the mode header in the worked/confirmed window displays a QSO count for that country/mode. However, I've noticed that i

Just read it. Really now, did that cause all this uproar? Regards, Mike VP8NO

Where is this review? v377 works perfectly well for me and I have created a FT8 specific instance of L32 which puts all I need in one tidy panel. Nice to see the log incrementing as the exchanges comp

Adding VK9/M0VFC in database country/prefix doesn't fix it either. It used to be possible. There was another instance of this sort of thing recently, can't remember the detail, but it had to be fixed