Thanks for taking the time to run these tests and report your results. When you get a chance could you repeat the tests (no need to run a large number) with the "Do not check or report logging success

All of my testing was done on FT8 signals. I didn't make any actual contacts, I would select a strong signal and then log it. I would then watch for B4 or lack of on subsequent transmissions. I made a

Laurie, The lack of a B4 is only for callsigns logged in the current session. I have restarted WSJT and JTAlert (JTAlert starts WSJT) and the B4 status is then correct. I did not restart Log4OM2 in th

Laurie, I am seeing the missing B4 in the Decoded Callsigns display. I don't use the Log fields display so I can't speak to that. As it turns out, I do not clear the dx call in WSJT-X. I don't do that

Herb, I'm kinda on the same wavelength. I don't use the cluster feature but it feels like JTAlert is checking the log before the logging is complete. We all know that logging really takes a long time.

Laurie, I've done some additional testing and have this to report: Log4OM2 ver 2.3.0.0 Database SQLite JTAlert 2.15.11 Win 10 64 bit 1903 Build 18362.657. Logging to Log4OM using JTAlert instructions,

Walt and Roger, I have the 2.5.1 sound file and have looked both of you up on QRZ. I will rename the .exe to .zip and send it as an attachment in a few minutes. Rename the file I send back to .exe to

Tonight I upgraded to 2.15.11 and made a few contacts. I'm experiencing the same thing, no Worked B4 notification on these contacts. Also using Log4OM2 ver 2.3.0.0. I've not noticed this before but th

Laurie, Nice job. I did the re-install and there is now a male (as well as female) version of Michigan. The male version is an improvement over the female version that used to get installed whether yo

Laurie, Man, are you quick! I use individual state. I figured timing also especially with how you have sped up things. By the way, the Michigan announcement is difficult to understand and there is no

I've been experiencing wanted states not being announced with version 2.15.6. Here are the circumstances. Mode FT8, Decode set to Normal or Deep (AP setting doesn't matter). When receiving, calls can

Ray, In my case, I am running only Windows Defender on a Win 10 machine at OS Ver 1903 Build 18362.476. I have setup only one folder to be excluded and it is C:\Program Files (x86)\HamApps\JTAlert. Th

Laurie, I was afraid my explanation was not real clear. The point I was trying to make was that after installing 2.15.3, the Program Updates section of Settings DOES show the callsign database version

Laurie, I installed 2.15.3 a couple days ago and expected the Callsign Database to update to 2019-11-16 but have JTAlert still show 2019-11-07 which is what I had installed manually after upgrading to

Laurie, I have installed 2.15.1 like many others. Install went fine except as noted below, but I read about the sound issues some are experiencing. I’ve not used sound alerts but was curious if I had

Hey Laurie, thank you for an outstanding piece of software. JTAlert is so fantastic, I have awarded it the NS8K Software of the Decade Award! There was stiff competition out there but JTAlert came out