For some reason, when I rebuild the JTAlert WAS database from DXKeeper, some needed states are getting dropped from individual bands. The needed states don't match DXKeeper's tracking. I've taken a br

For example, several days or weeks after logging a QSO (using DXKeeper in this case) a QSL is denied by the other station, stating he never received "RRR" or "73". I've always deleted these QSOs from

Happy New Year, I have been running ACLog / WSJT v2.2.2 / JTAlert 2.16.17 without a hitch. However, I just set up ACLog for the RTTY Roundup, was testing it and keep getting the following error messag

Greetings: I'm getting caught up on everything, been on FT8 for about a month, JT-Alert about 2 days. Kudos to the team for their efforts, and for everyone who got us to where we are today, etc. Its a

It looks like B4 highlighting is taking precedence over Marathon Wanted status - Marathon should alert even if it is worked B4, or there should be an option to ignore B4 for wanted Marathon stations,

It looks like JTAlert displays decodes in the order they are decoded. Is there any way to make it display wanted decodes first? On crowded FT8 segments, some decodes are not displayed because of limit

I know this has been reported to death, Laurie, but though maybe a note of interest, I have had this coming up 2-5 times a day, sometimes 1 right after the other to the point of stopping the autostart

Thanks to all that responded; All were all helpful. I did not think the problem was in the JTDX settings as de Laurie VK3AMA suggested. However, he was correct. Based on his comments I held everything

My install of JT Alert does not work properly when using HRD for radio control of JTDX. JT Alert just sits there almost as though it is not connected in any way to the other programs. No error codes.

I've replaced my dying shack Win7 machine with a refurb Win10 PC and have been getting my software up and running again. N1MM - check. DXLab suite - check. Today I got WSJT-X latest version running an

Greetings everyone and lets hope 2021 will be markedly better than 2020 ! Is it possible to have the contents of JTAlert's 2X8 cells (or MXN ) selectable w/r/t "CALL - State" to switch between State o

Just upgraded to 2.16.17 from 2.16.6. Noted that many of my settings did not transfer over. Has anyone else noted this? Also, why do we now have two indicators for a person who is online, the underlin

Good morning to all, I am running two transceivers (on different bands of course) and run two instances of WSJT-x and two instances of JT alert. Everything is working correctly with the system EXCEPT

Hello, It would be nice to have Hamapps (JTAlert) in Dark Mode. JTDX has also the function so to get it equal it would be nice that this would be added. Thanks 73 de Frank IZ7AUH

With HRD supporting Google Earth Pro, the logging record must have the blank fields populated, specifically LAT / LON. Under HRD --> Tools --> Configure --> QSO forwarding, there are two UDP Receive c

The QSO Pop-up is a helpful tool. However, it should include: 1. Timed appearance. 5 seconds is enough, or a user choice 2. Smaller. It could be smaller if there is no activity to report 3. Position.

Greetings All Equipment: DELL E6510 Laptop using WIN-7 SW DXKeeper v15.7.2 WSJT-X v2.2.2 JTAlert v2.16.17 I have installed JTAlert and selected things like Wanted Grids and others and Rebuild Alert Da

Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change? I used the blue musical note shortcut. Do I need to use a differen

Hi, I have JT Alert 2-16-17 and WSJT-X 2.3.0 RC2 installed on the PC in the main shack and everything works perfectly, thanks Laurie. I also have installed both programs on the PC in the house shack a

The 2 x 7 areas I use to fill in are ok, but the area for a selected call sign to be worked does not fill in the Name, QTH, or Grid. Seems to have the State and/or Country though. It does fill in if i