Bob, Are you saying that column ordering is not being obeyed when you restore a Layout? You didn't mention that before. I am not seeing that here. I have several layouts with different ordering and co

I answered your question in your other thread. See here https://hamapps.groups.io/g/Support/message/26750 de Laurie VK3AMA

Tom, Follow the advice I posted here https://hamapps.groups.io/g/Support/message/26752 Until you get the decodes database schema updated you will never see FT4 entries in the Decodes window. de Laurie

Bob, I have been able to reproduce the problem, so I should have a fix available for the next public release depending on what happens between now and Christmas as I am currently on Vacation so coding

Russ, The Text Messages online indicator uses Internet https calls into the HamSpots server to check if recently decoded Callsigns are online (the results are cached with a suitable timeout). Perhaps

What Alert Filters do you have set in JTAlert? They control what is displayed. de Laurie VK3AMA

Misplaced or missing menus on the JTAlert titlebar is a know problem affecting some Win10 users. There is not fix, but thee is the "Alt Layout" build of JTAlert which moves the menus to below the titl

Russ, Rule #1 when running Win10 and you start to observe unusual or unexpected application behavior (not just JTAlert), before changing settings, is "Restart Windows". I have lost count on how many t

David, This indicates that the source of the failed logging is HRDLogbook. "[c] Found 39 Valid Fields..." is coming from HRD and indicates that it has received valid log data from JTAlert. "Failed to

Sorry, A separate alert for "CQ DX" is not available. There is however are settings to shown a different CQ indicator prefix character and colored border around the Callsign for directional CQs. While

Prior callsign history will show in ACLog when it receives the Callsign of your current QSO partner from JTAlert. You need to enable the "Enable sending of new DX Call..." checkbox under the "Logging

Yes please upgrade. Once you have upgraded, operate as normal and then when you observe the failed JT9 audio alerting take note of the Callsign and UTC time and include that information in the support

All first time posts from users are moderated and don't automatically appear. With time-zone differences (plus I am on Vacation) there can often be several hours delay before a post appears. Regarding

Both Band Activity and Text messages are handled by the JTAlertV2.Manager.exe process which receives instructions form the main JTAlert.exe process. It would appear that these instructions (via UDP) a

Bob, I was in error when I indicated that the Miles/Km settings was contained in the layout files. The layout files only control the columns width/ordering and the Decodes window position. The Miles/K

The JTAlert Miles/Km settings are independent of what is set in WSJT-X. de Laurie VK3AMA

Please use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. de Laurie VK3AMA

JTAlert does not affect the B4 status shown in WSJT-X. JTAlert and WSJT-X operate independently with respect to B4s. If both apps have suddenly started to show all callsigns as B4s something has chang

This sounds like a JTDX coding limitation. If JTDX is responding to JTAlert callsign clicks for CQs that indicates the code in JTAlert is working correctly. JTAlert doesn't distinguish between decode

JTAlert not shewing B4s on a single Band will only occur if the Callsigns you feel should be B4s are not present in your Log for that Band & Mode You need to search your log for the Callsign(s) in que