Never happened before where the Decodes window does not print. WSJT-X is decoding OK. JTAlert is decoding callsigns properly but the window below remains blank. This is a valuable resource showing all

Thanks Laurie! - That did the trick! -- John P. WA2FZW

OM (please sign your messages!) When you double-click a callsign in JTAlert, observe how the DX Call field in WSJTX changes, not when WSJTX starts TX'ing. That will show you

No need to manually change the Log QSO window entries, when you finally make contact with the station, simply double-click the first decode (in WSJTX) you receive from them. That will

You need to set WSJT-X to use multicast UDP. Use the JTAlert "Help -> WSJT-X UDP Setup' menu to bring up the help file open to the relevant section. The help provides a very

After my 'C' drive crashed, my computer guy replaced it with an SSD and upgraded the Windows-7 machine to Windows-10. I re-installed all the latest versions of everything. I run 2 instances of WSJT-X;

I disagree with your disagreement :-) Users don't even look at the fields after doing just a few QSOs. So would never notice the time problem. I don't consider it hand holding when the software

I disagree. Too much automation or hand-holding by software encourages sloppy operating IMO. de Laurie VK3AMA

thanks Laurie.. I have been doing that, but was hoping for an "auto" option.... oh well, manual mode it is. :-) John

Or simply double-click (in wsjtx) the first decode received from a Station you have been trying to work for awhile. That will reset the start time to the time of the double-click.

There is no setting in JTAlert. JTAlert logs both TIME_ON & TIME_OFF values as well as the QSO_DATE & QSO_DATE_OFF values. It is up to the logger as to how it handles those

Or...maybe a warning if stop time is more than 29 minutes from start time to check your start time. That would seem to be an easy one and a better overall solution. Mike W9MDB

LOTW has a 30-minute time match based on start time. So if you get close to that and want a match better check with the other party to see their time too. If they went to work somebody else though

Hello Mike.... I want it to use time off because there can be a vast difference between the start and end times. Down here, it gets rather busy and the qrm means I dont always get to complete a

LOTW uses TIME_ON, not TIME_OFF -- so why would you want different? Mike W9MDB

I think I have lost the plot... I just cannot find the answer to this.. I am using Log4om, WSJT-X and JTAlert. I mainly use FT8 and FT4 modes and recently noticed that log entries are being

Thank you for the reply. The computer in question is running only WSJT-X and JT-Alert, as the laptop is dedicated to these 2 apps only. I will monitor it closer and see how things behave in the next

JTAlert doesn't perform any scanning of the log at startup. The first time JTAlert access the log to lookup B4 data is when the first batch of decodes is received. There is no pre-scanning.  What

Gregg, If your have the "Instruct DXKeeper to upload each new QSO to LoTW" checkbox set, that is all that is needed for JTAlert to format the DXKeeper logging instruction with

Hi, Mike, Glad you got it worked out. The MySQL database is the way to go. I've been using WSJT-X, JTDX and JTAlert for years with HRD, using Access and MySQL database, with no problems. Performance