Hi- I'm noticing lately with the increased solar activity, my mode activity display is almost always showing the top level (greater than 50) for most bands most of the time. It would be cool if we cou

JTAlert has 36 “boxes” that display the received stations. Many times there are more than 36 with the remaining stations not displayed. Please consider increasing the number of boxes. Maybe another ro

Hi, I made a new PC with W10, now I would to transfer all the settings of JTAlert on the new PC. How I can make this operation? Thanks, Camillo iz6gvc

had to reset all groups. is this one working?

Hi, I am in the middle of the RTTY Roundup and have been using WSJT-X, JT Alert for WSJT-x and DX Keeper. All has been going very well using this combination, however, my desire is to switch to RTTY a

I have just begun using JTALERT. It works fine. I do not use the logging feature as I manage my own thru Ham Radio Deluxe and Club Log. I just use it for the alerting feature. When I have worked a sta

During contesting this past weekend, I realized that I had no way of knowing which states I still needed to work in order to rack up multipliers, as my JTAlert's database is set to only trigger alerts

Hi Laurie - HNY Would it be possible to make designated needed entity post stay in place on JTAlert until manually removed? Sometimes we are distracted for a few minutes and do not want to miss a desi

For some reason, when I rebuild the WAS wanted alert DB, some states are getting dropped from individual bands. For example, on 30, DXKeeper says I need NJ, ND, and NC, whereas the rebuilt DB says I o

The Swedish sound file uses the word "nytt tillstånd" for "new state". Without context, "nytt tillstånd" is a correct translation but it means "new state" as in a state machine changing state or "stat

It seems the text (Updates) in the banner of JTAlert shows in spite of my installation being up to date. When I start it shows 2.16.17.0 and (Updates) in the banner but it then changes to 2.16.17 with

Hello, this is Pepe EA4ZQ, KC0CLF. Before working FT8 mode, I need start Logging software, Time sync soft, JTDX soft and JTAlert soft. Well, this is a huge work for an old mind... hi, hi.. I use a bat

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