Hi Laurie… Yes, something that didn’t occur to me was the CPU load. I am using an old Acer Aspire E1-522, 6GB of RAM but only a 1.4GB CPU, dual core. I watched the task manager for a while and the dec

Good morning, all... I have noticed that the callsign window does not always clear the old callsigns. I have experienced the window populating 6 or 7 decode cycles before clearing. It's not a constant

Excellent, John. Thanks for that. I searched the Help file but didn’t find that. 73, Tom

Hi Laurie… Again, a solid program for me cuz I know how to read J Just a quick one….in the callsign window, when I mouse over any call, I can see their eQSL and/or LoTW status. The date in brackets fo

Good day…. Here’s a screen shot of the API settings. Only check the first check box, not the bottom one. Also, the logging program MUST be running before you start JTAlert else you will get an error,

Wouldn’t this be better served on the WSJT-X group, Amos?? This group is for HamApps. Just sayin’….

I’ve had this same thing ever since I used HRD Logger and now the same with ACLog. The accents, tildes and other foreign characters are not in the English language so the software (also set to English

#HRD

Just a thought….uninstall the rc-3 and go back to rc-2. There’s obviously some kind of bad interaction between it and JTAlert. I would also send the same email to the WSJT-X group. With beta software

Hi Jim… Yes, it’s a great program for tracking your needed DXCC, States, Grids….whatever. If you are using one of the supported loggers and you are logging your QSO’s to the log, it’s easy. Go into Se

Hi Laurie…. Yes, the Ignored Callsign appears as it should if it is not B4. I checked several random calls on 40m FT8 and it worked well. Then I tried a couple that were B4 and it failed. So, there ya

Hi Laurie… Yes, the alert is enabled under both Settings> Misc Alerts > Ignored Callsign and also enabled under Settings>Alerts I have already worked the station and it properly identified in the disp

Good morning, Laurie and group... I have upgraded to v2.16.10 and noticed that the callsign listed in my "Ignore Callsign" section of JTAlert are not displaying the default background colour, or any o

FWIW Jon, I use Private Internet Access here. It's a subscription VPN service and it does do split-tunnel as well. I have never had the issue you're describing but it would be interesting to find out

I had the same issue with WSJT-X "skipping" decode cycles. Very frustrating!! Through their forum, I found a workaround that seems to fix it. Just change the priority of WSJT-X to Realtime instead of

Ah, OK. Well I only have one radio so only ever run one instance of it J I have several logs so I thought it was the #1 HRD5 log. Thanks Mike… Tom

Hi Ian… The ~ indicates your mode ( but it doesn’t seem to be there in mine since I ugraded. Used to be ~ or # or@ to indicate the mode. Now it seems to just spell it out) 17m is obviously the band DX

I have noticed that WSJT-X will "skip" a decode cycle on both FT-4 and FT-8 and then work fine for the next. Of course, if WSJT-X doesn't decode anything then JTA will display the previous decode, not

Likewise....Avast Security Premium scanned the download file when I tried to execute it and called home to have it checked. After about 2 minutes, Avast replied that it is safe to install and I did. I

I upgraded to JT Alert 2.16.3 this morning and it runs just fine. Much faster decoding it seems, too. I am using HRD Log v5.24.0.38 and JTA is still logging to it even though the log is closed. I gues

Yup...that worked. Thanks...Tom VE3II