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

I am using a SignaLink USB interface, Windows 8.1 and the latest versions of JTAlert and WSJT-X. This is how mine is setup for audio and it works perfectly with no stray audio being transmitted. I hav

I downloaded 2.16.0 last night and Avast complained that it “might” be an infected file. It didn’t delete the file but rather froze it from being run while it sent the info their labs for analysis. Af

Dear all.... I have been working out-of-the-country for the past few months so I haven't updated my system. At the time of my last QSO, everything was working 100% (logging, DXCC counts, B4, colours,

I am using Windows 8.1, 6GB RAM with an AMD dual core (1.4GHz) and v.2.15.5/v.21.2 WSJT-X. After the seemingly typical initial audio glitch, it’s been working flawlessly, with quick decodes and popula

Gents… I think that we all enjoy a tremendous piece of software from Laurie. It behoves us (the end-users) to read the advice from Laurie and others when we have a problem and to follow their instruct