Hello, in the UDP window settings I have marked the GRIDs with which there have been no QSOs this month as highlighted, Cherry-picking marked, no calls are taking place. Any

Charlie, You're welcome. I'm sure you'll like it. Enjoy and have fun. 73 de Peter, OE3EPW Am 09.08.2022 um 17:52 schrieb CW Carpenter:

Peter, That downloaded. Thanks for the tip. Roberto, tried that earlier and it gave me the 404 not found, Even though its a cloned version of jtdx, will see how it works. Do appreciate the advice,

Probably becaise there is no index 999 in the logbook database. Looks like you have now gone gone full circle. Logger32 doesn't know what field/colimn you want your logbook sorted by. SeventyThree(s).

This is an other place to find "JTDX" ... <https://sourceforge.net/projects/jtdx-improved/> You may even try "JTDX improved" which brings a lot of advantages

Try here : https://sourceforge.net/projects/jtdx/files/ Robert

Transferring my log from another logging program. All went well, no problems. I was using WSJT-X with a former logger. I want to try JTDX with L32. But it seems that program is being blocked and I can

Help, creating a new log this error appears. Logger version 32 4.0.295 Thank you. Vanni - IK4RUX content_copy share

I ran across this error message when I entered my logs from my POTA outings when some QSO's had the same start time. Just click the "OK" button and it will take care of it by incrementing the time

Tested it again to get exactly what it says... At the bottom of the window, it says Sending information request to LOTW server. Then in 5 to 10 seconds the box, the X is in that you click to close the

Sorry Rick. I've been out of the house. I thought I would get an email if you answered. Guess I will check the settings on this. As far as my computer, I bought a W-10 the first day it was released.

Hi, I found that the display and blocking problem only happens with new logs, probably due to some update. The good BOB will tell us something. Thanks 73s Vanni - IK4RUX

Thanks' to all for all the comment/suggestions. I have fixed it by the export to ADIF, open in ADIF master, delete all GB22GE calls (I couldn't see any difference between them), and import into a new

Paul. I think you need to keep the bag there longer. Set the time format to something like HH:MM:SS. Try again. To see all QSOs in the logbook try exporting it in ADIF format. SeventyThree(s).

Presently, the time format is set to HH:MM How do I see a QSO that is supposed to be in the log ? Can I take that bag off my head ? 73 Paul F6EXV Le 08/08/2022 à

Hi Jerry.. What OS are you using??? In the process of building the URL to access the LOTW server this line of code is executed: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12

Please follow the recommended solution: Step 1: Take a deep breath. Place a paper bag over your head. Count to 10. Step 2: Change your time format to soething other than

Bob OK, I will investigate that further, but this answers the fact I cannot add a QSO that is already in the log... But if already ion the log, whyc can't I see it ? 73 Paul

The choice id yours. As you can see, v 4.0.294 fixed a bug with time formatted as HHMM. SeventyThree(s).

version 293, and I do not want to use 295 because of the "operator" issue... Le 08/08/2022 à 12:22, Bob a écrit :