I tried again, without modifying anythuing, and... it works ! Maybe I pressed the OK button too fast... 73 Paul

You shoud put a mark befor All Operators 73 Jan PA4JJ Op 16-4-2020 om 10:05 schreef Xenofon Labiris via groups.io: --

Hello Rick, I can't see my call in L32 export proccess.. Setup in L32Logsyn done corectly. Regards, Στις 15/4/2020 7:42 μ.μ., ο Rick Ellison

Worked as advertised here!!  Once I got past Windows 10 trying to tell me it could harm my computer. 73 Ken ZL4NR

I just (at 06:46 UTC April 16 2020) tried a download and all was ok. 21 QSO's read and 21 qso's were updated in Logger32. TQSL v 2.5.2 Logsync v 2.0.17 73

Hi Rick Upload to LoTW and update of uploaded QSO in L32 works fine. Downloading does create a file, but "Error 20477 Invalid filename" makes it impossible to update confirmed QSO. Looking forward to

Done. Thanks for the guidance! Jim W1YY

Half way there, did you add C\Logger32 to the exclusion list? So next time Microsoft gets a wild hair up their ass they don't do this again. It's been twice in about three weeks. I think it's because

Bob, all fixed. I looked back through the recent postings, found a useful hint in one of the posts, then went to Windows Defender, looked in the quarantine history, found that Logger32 had been

FB DR Rick, my situation is OK now ;) 73 Villi TF3VS

If you still can't figure it our, just holler. I'll give you a step by step. 73.

Thanks Bob! Jim W1YY

While you were away, you Antivirus software (probably Microsoft) quarantined Logger32. There have been at least 50 messages here since Friday on the subject. Recovery is very simple (about half a

After about a week of inactivity, I just logged on to my radio computer and discovered that my Logger32 program had inexplicably vanished. I had installed the latest Logger32 update about a week ago

I have posted an update to L32Logsyn at the link below. This corrects 2 issues that have come up with recent changes to the latest version of TQSL. I am not going to guarantee that this will be the

Jim, from what I read on the reflector, for a lot of users, not checking for Logger32 updates is a desirable result :) SeventyThree(s)AndBackToNetOverOver.

I notice that during the startup sequence after updating the clublog exceptions etc., if it fails to get the atomic clock time, it won’t proceed to check for updates until you manually get the time

Markku I think you see only "not worked this band" callsign now. Cherry-pick only callsign displayed in UDP BandMap. Please try check/uncheck options under "Cherry-picking options"

One more thing, Is there a way to setup the cherry picking feature such that it only picks calls that are visible on the UDP bandmap? Idea is to just call the highlighted stations, as it is now, it

Thanks Aki! This works. Markku