'#' is directed CQ, '*' is general CQ can be turned on or off by user. LOTW user can be set to a flag (corner fill) or a stripe - position configurable by user, Likewise eQSL (AG) user. Both

directed cq, i think, as in cq dx ... Dave Garber VE3WEJ / VE3IE

In JTA, what is represented by the # to the left of the call sign? If memory serves (and often it doesn't) the | and the * represent ops who upload their logs to LotW and eQSL but I missed the part

I have JTAlert 2.16.9 and AC Log 6.6. I have all states worked on 7 bands.When I run Rebuild Alert Database and then look at Wanted US States, it still shows a multitude of states needed on those

I updated to v 2.16.9 from 2.16.8. Now I get the error shown here (AutoIt Error). I went back to v 2.16.8 and got it again. I un-installed the program including registry and folder. Installed 2.26.9

You got more than me Ron, I got no sounds at all, had to go in and manually change to a sound from the sound files, but as I say, it's no good having the same sound for both a successful QSO log and

ARRL isn't even self-consistent. See this list. ZR-ZU is "South Africa": http://www.arrl.org/files/file/DXCC/2020%20Current_Deleted.txt I'm just pointing out the inconsistency. Every time I

2.16.9 Along these same lines I now get both the "windows Notification" sound and the "Text Message" sound when a text message comes in, one after the other. If I turn off the " Windows Notification"

This is a minor issue at best, but one that appears could be easily changed. I compare with LoTW frequently to insure that DXCC's are staying in sync between JTA and LoTW. When I see that JTA and

Thanks Laurie. Deleting the "decodes" files did the trick. I keep my decodes database set for 100 records. Really don't keep an eye on the Statics, but noticed it was stuck with Zeros after reading

Laurie: Thanks for your reply and the explanation. Therefore I won't worry about it. Thanks for such a wonderful app and for all the time and patience you expend.

Thanks for the update. de Laurie VK3AMA

The one change that explains this behavior is having updated your HRD Log to be ADIF 3.1 compliant with respect to FT4 QSOs. You need to tell JTAlert that your HRD log is now

Callsigns and DT highlighting is only available with WSJT-X. JTDX does not support this, the developers chose to remove that functionality from the WSJT-X UDP protocol. de

There are three parts to successfully installing a false positive JTA version. 1) The browser may flag the download file during the down load phase. Since each new version has a

Mike W9MDB Thanks. Windows Defender has already been set to "ALLOW" JTAlert. And that has worked in the past for updates until now. Jona KK4HMQ

Kevin -KX4KU Thanks. I will give it a try. Jona KK4HMQ

Downloaded and installed 2.19.9 and worked all OK except: I'm running JTDX with the the proper JTDX version of JTAlert. I found that the "Highlight Band Activity DT" does not work. Out of tolerance

I've used WSJT-X with JTALERT and HRD for over a year suddenly about 2 weeks ago I stopped seeing B4 markings on FT4. FT8 is fine but FT4 just shut down as far as identifying stations worked B4. I

I have a problem with this update "Windows notification sounds: Used by some JTAlert popup messages, like logging success/failure, have been replaced with a dedicated sound file/volume