JTAlert gets the frequency from WSJT-X, and passes it along to the log program. JTAlert doesn't have any direct knowledge of the frequency, except what is passed to it by WSJT-X. 73, Jim N6VH

#FT8

Bob, Great! Glad I could help. 73, Jim N6VH

Bob, Go to Settings - Alerts - Miscellaneous Alerts - Wanted Callsign. Under Options, check "Alert when decoded Callsign worked B4". 73, Jim N6VH

Dana, Understood. Then the question might be better asked on the Log4OM forum, on their web page. There are several people there who could help. 73, Jim N6VH

JTAlert doesn't interact with any transceiver. Is it possible the problem is with WSJT-X? 73, Jim N6VH

Don, Will this do what you want? See attached. Settings - Alerts - DXCC 73, Jim N6VH

#JTDX

Bob, Great! Glad it's working for you now. 73, Jim N6VH

Bob, Thanks for the info. Based on what you have said, the worked grids should show up immediately after doing a "Rebuild Alert Database" process. Since that isn't happening, something is wrong. Also,

Bob, Yes, any good log program will certainly have a big learning curve. DXLab has a great reputation and support from the author. Once you get it going, you will find your workload will be a lot less

Bob, This won't answer all of your questions, but I suggest moving to WSJT-X 2.4.0 and JTAlet 2.50.4. The order might not matter (not sure, though), but I would do WSJT-X first, then JTAlert. Net 5.0.

Dave, I would also suggest moving to WSJT-X 2.4.0. 73, Jim N6VH

JTAlert 2.50.3 is running fine here - no problems. 73, Jim N6VH

Dale, The xmt & rcv freqs that JTAlert puts in the file are what is sent to JTAlert by WSJT-X. JTALert is not connected to the rig, and has no direct knowledge of the frequencies. JTAlert can only kno

Stan, I see one thing that might be causing the problem. You have "LOTW or eQSL(AG) member" checked. Even though TM13COL has uploaded to LOTW, I don't think the call has made it into the most recent d

Ronald, In the message I replied to, you said you ran the "Install.exe" file and you showed the Callsigns window. The "Install.exe" file is the JTAlert.2.50.2.Install.X64.exe. Is that what you mean? W

Ronald, Left-click on the cog at the lower right of the Callsigns window. That will bring up the menus. Another method is to make certain the Callsigns window is the active window, and press the F2 bu

MSDATL3 is part of Windows, so the problem might not be with JTALert. Could you post a screen shot of the error message (just the message, not the entire screen)? What version of Windows? What log pro

Wayne, In order to resize the entire window, in the Callsigns window, at the lower right, click the settings cog. Then, make certain "Size locked" is NOT checked. 73, Jim N6VH

#FT8

Erik, Here are some suggestions. They might seem obvious,, but they are worth checking. Is it possible that you have DXCC set for Individual Band (Or Digital Mode, etc), and the alert is for the Stati

Bill, That is what I was trying to say, but I see I could have worded it better. Yes, they all should be either 64 bit or 32 bit. In general, my preference is to use 64 bit programs when they are avai