In JTDX ... select the "MISC" menu, scroll down to "Accept UDP Reply messages" and select "any message". Now JTDX will respond to clicks on callsigns in the JT-Alert RR73/73 decodes window (or any sta

#TIP #WISH

I studiously avoid any "automation" ... AutoSeq is set for "Single shot QSO". There is no help built-into JTDX and the old e-mail list on groups.io is gone. You may be able to find your answer by sear

In JTDX -> Settings -> Reporting, make sure all three "UDP Requests" boxes are checked. *IN ADDITION*, in the JTDX "MISC" menu, click on "Accept UDP Reply messages" and select the type of decode (CQ,

Specifically: <https://www.pcworld.com/article/626854/kaspersky-blacklisted-as-a-risk-to-u-s-national-security.html> 73, ... Joe, W4TV

Install the required service pack for your Windows 7 (if you still can). *MICROSOFT* (not Ham-Apps) is blocking the installation of *any* version of the dotNET 5 Runtime beaus your Windows installatio

Get rid of Kaspersky! The US government has declared it a security risk, in any case. 73, ... Joe, W4TV

The error information from the other user indicates that he does not have the latest [last] Service Pack installed in his Windows 7 system. Microsoft will not install the Windows Net Runtime on system

True ... but marking QSL_Sent as invalid/ignore should be an indication that the QSO is not valid for some reason and should be ignored [as if it did not occur]. 73, ... Joe, W4TV

ADIF (3.1.2) defines <QSL_Sent:1>I and <QSL_RCVD:1>I as "Ignore or Invalid". I would interpret those states, if a logger supports them, to mean "ignore this QSO" for QSL_Sent and "ignore this QSL" for

Yes - unless HRD have a way to mark a QSO "invalid". You will also need to restart JT-Alert and Rebuild the Alert database. 73, ... Joe, W4TV

What logger are you using? JT-Alert refers to your log book for B4 status. 73, ... Joe, W4TV

Ask HRD support. JTAlert does not provide that option with HRD logging. 73, ... Joe, W4TV

Offline/Online applies only to JTAlert users - whether they accept text messages (have that capability turned on in JTAlert). JTAlert detects on/off line by contacting the HamApps server to find out w

The LotW users list is provided by ARRL. The eQSL (AG) list is provided by eQSL. They are incorporated (along with the FCC Database for US calls/states, and AD1C's "Country Files" for countries/zones)

The process to move IOTA support forward is to provide Laurie the necessary information to download the DB schema and data on downloading the database on a regular (monthly, semi-monthly) basis. Wheth

Not to speak for Laurie but that does not sound acceptable. Online searches for every decode in a 7/15 second cycle four or eight times a minute would be too limiting. Understanding that Laurie has de

I *DO NOT* see a "Wanted IOTA" alert nor do I find any IOTA status in the Alert Database. In other words, there is no IOTA support in JTAlert. States are in the Callsign Database (from the FCC Databas

Since IOTA is not supported in the WSJTX protocol, the only way to know of an IOTA decode is if you already know the callsign. In that case, place the callsign in the Wanted Calls list and use the WAN

The differences between ARRL International Digital Contest and WW Digi lie in available bands (ARRL includes 6m), power levels (WW Digi includes a high power category) and operating time (length). 73,

Either/both <G>. The two options generate identical standard messages and log data. I simply chose NA VHF since I had a stored configuration from ARRL VHF Contests. 73, ... Joe, W4TV