Hi Bob Several weeks ago you suggested that I try JTDX again. I have done so. Thanks for the suggestion. It is growing on me; I'm beginning to really like it. Now, in the Department of Wouldn't it be

Fixed it! Stupid mistake on my part! Live and learn. John VE1JS

I do not have the USB upgrade. I still use a USB com port.

Is anyone else using a K3 with Win4K3 and Logger32 Version 4 (latest)? I have trouble with the sharing of com ports used by Win4K3; they are from com-0-com as recommended. I see the L32 uses a differe

Thanks for the quick reply and explanation. I may have to try JTDX again. The last time I tried it, I didn't like it nor see any advantage to using it. To each his own!! 73 John, VE1JS

Thanks for all the previous help with getting version 4 to work. Now I see another problem: When I click on a call in the "ME window" the call is transferred to the Log Entry Window as expected with t

Ignore previous message. I have it fingered out now. I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X to.....

Hi Bob Thanks for the reply. I did miss the bit about reopening the K3 radio port. However, when I do that, after stopping WSJT-X properly, I keep getting a message "Invalid Port Number: Comm port 16"

Exactly right, Gary! 73 John

It took me a while, but I thought I had everything working as it should after the upgrade to V44. RTFM! However this is not the case: When I start L32, having closed WSJT-X from within L32, the freque

That's where mine is set. Works like a charm. VE1JS

Yes, "Clear logging window..." is checked. Happens always in auto logging I don't use cherry picking so I can't comment! John, VE1JS

With the installation of 3.50.370, I notice that the Log entry window is no longer cleared when WSJT-X logs a QSO in Logger 32. The seems to happen no matter what is set in the Config drop down menu n

Our "friend" in ON should be patient. "The difficult we do immediately, the impossible takes a little longer." Given someone time to work on it. In the meantime, Bob, please reinstate it. For now, I'm

What does this mean? Upgrading versions has gone on for years, literally, without a hitch, once I starting running Logger32 as Administrator. Now I get this message: "CopyFile API failed to copy Logge

SOLVED!!! In Band and Modes setup, list CW as starting at the bottom of the band for lowest frequency and the top of the band for highest. CW is valid anywhere!

Logger 32 refuses to accept 6m FT8 QSOs. I am loading them by importing from the ADI file which WSJT-X generates. All other bands import OK, but 6m QSOs all turn up in the BAD.ADI file with the messag

If I had a restore point, I would try. Didn't do it! I thought I had auto backups running, but didn't. I do now! The lost file has been recovered from LoTW submission files as far as 6 weeks ago. Not

I made a QSO on 20m CW. Pressed enter to log it. Logger 32 froze. I had to kill it with Task Manager to get the machine back. Restarted the computer. Log that was in use will now not open. Other logs

Over the last couple of weeks, I have spent many hours making my DXCC and IOTA stats show almost identical numbers in both Logger32 and DX4Win, my present logging program. The job is as complete as it