The Latest JTAlert version 2.15.4 is now available @ https://hamapps.com/JTAlert/ This release has a critical fix for "NO Log" users. Please review the Release notes at the end of this message. de

Laurie, The log functions have started woring again. The only thing I know I did was close and reopen WSJT-X and JTAlert. I guess the restart fixed the issue. Tnx

Neil, A scan Log & rebuild will NOT resolve any B4 issues your having, it only affects the internal lists used by the Wanted Alerts. If your seeing some B4s on the

Revo removing needed JTAlert files would not cause JTAlert to stop receiving UDP data from WSJT-X, if anything it would produce a critical error dialog from JTAlert which would subsequently

Thinking about the problem.....I used Revo Uninstall to remove an Acom program. I think in the list of "leftovers" was an important file for JTAlert. It wasn't listed as such or I would have

Rick, Did JTAlert work previously and this is new behavior? If new, the likely cause is another application started prior to JTAlert taking exclusive control of the WSJT-X UDP server

Bob, All online log uploads are handled by the JTAlertV2.Manager process, while DXK logging is handled directly from the main JTAlert process. Do other

GM All, I am using JTAlert to log my QSO's to DXLabs DXKeeper. This functions fine. I also have JTAlert logging all Q's to my QRZ callbook and Clublog, and HRDlog

Laurie, Thank you. The callsign entry was indeed missing in the registry. I added it per your suggestion and JT-Alert now runs. Thanks again. Much appreciated. 73… Paul (VE3PS)

JTAlert 2.15.3 will not communicate with WSJT-X 2.1.2. Get the famous I have rebooted the computer, reloaded both programs, checked that the 3 boxes are checked. I don’t know what else to

Hi Mike and Laurie, No, I had not done a "Scan Log and Rebuild" I will. And Laurie, Yes I see one or two as worked "B4". I use Ham Radio Deluxe...latest version, and have for many years. Neil N4FN

Hi Laurie I fully appreciate your comments on existing users and thank you for changing the auto-close for new users😊 Cheers David VK7YUM

Stuart, What logger do you have enabled? If the Scan is not finding prefixes then your log doesn't contain the Prefix data recorded with each QSO. Similarly for

Thanks very much Laurie. I will definitely look into this tomorrow morning. 73… Paul (VE3PS)

Paul, JTAlert will abort trying to start if it is unable to determine your Callsign as that controls which config file to load. Either the necessary Registry entry is missing

I have installed, uninstalled, and reinstalled the JT-Alert app 4 times and I am still unable to get it to run. Following each installation, I ensure that my virus scanner will exclude the HamApps

When JTAlert scans for wanted prefixes, it finds no prefixes. Previously, it found 400 fewer than the number of prefixes, so it reported many false positives. I also scanned for states and it found

The default timeout is 20 seconds. I wouldn't characterize that as too short. While I can alter the default setting to "No Auto Close" that will only affect new users with newly

There is no separate install of the Alt Layout version, that was abandoned back in version 2.14.5. Both layout types are automatically included in the one installer file. de

Mike, The Scan Log & Rebuild does not influence the B4 display, it is only used to maintain recorded the Wanted Alert lists. B4 determination is done using a direct lookup of the users log file with