Thanks Laurie. I deleted the "decodes" files per your instructions, and the Fatal Error went away. Just to clarify, my Decodes Window was populating just fine. I got the Error when clicking on a CQ

Laurie, I've been adding a bit to my powershell email script and tried to add the Lotw variables. But I'm not seeing any information in either JTAlert_Lotw or JTAlert_LotwDate they are always 0

On 18/06/2020 7:11 am: Why the hesitation in upgrading? The upgrade had the fix for the problem you were experiencing. You statement has me somewhat confused. de Laurie

Kinda why I hesitated to upgrade in the first place.

That is a system generate sound initiated by JTAlert itself and sent to your Windows default device. All Alert sounds are generated by the JTAlertV2.Manager process which is not

Sorry Mike, that is not going to happen. I went down that path in the past when I implemented a form of sound stay-alive, periodically playing a zero-volume wav file in order to

John, OK, the non-initialized Audio module is not the problem. Lets focus on one PC only now that I know it is not a multiple instance issue. Choose one of your PCs, Run

On 18/06/2020 2:19 am: OM, Your image shows that JTAlert 2.16.6 lost the decodes received in the first decode pass of the Rx period. That was a defect within JTAlert

You need JTAlert 2.16.7 for it to function properly 73BobKo6Lu On 6/17/2020 9:19 AM, Bob Craig via groups.io wrote: -- Bob KO6LU

First, yes I've upgraded. WSJT-X 2.2.1 and JTAlert 2.16.6 Second NO display filters are set. Computer i7-4770 desktop, 8gb ram Calls that are decoded by WSJT-x are not displayed. Attached screen grab

It should. If you're seeing JTAlert instead of JTAlertV2.manager, the sound is probably an error sound (Windows Error). Acts like you do not have JTAlert configured correctly for the proper sound

Bill, I have found a way to get the JTAlert to show up on the volume mixer. But I thought it would say JTAlertV2.manager It will happen after I make a QSO and log it (in

So do I. I run two separate setups. Each radio+antenna has it's own PC, one Win10 home and the other Win10 Pro. same problem on each one John Virus-free. www.avg.com

That would explain why it didn't show on mine until I switched audio devices and played a test sound. I guess that's because the mixer doesn't know the app is running until it plays a sound. Maybe

Me too, but I have it running on two different computers John -- John Mc Hugh, K4AGCoordinator for Amateur Radio National Hurricane Center, WX4NHCHome page:- http://www.wx4nhc.org

I assume it does work through the other Speakers device? JTAlert Manager wasn't showing up on my mixer for my headset until I switched the sound device to another device and back again. Mine is not

Laurie, Here's what I get on both computers JTAlert Instance????? : #1 JTAlert Start Params? : /wsjtx WSJT-X Window Title?? : WSJT-X?? v2.2.1?? by K1JT, G4WJS, and K9AN

John, the JTAlert mixer slider in the Windows Volume Mixerwill only show while sound is being played. Does it appear when you use the JTAlert sound test facility, and what level is it at? --

Laurie, You misunderstood me. I run two totally separate setups. Two radios+antennas and each has it's own computer, one using Win10 Home and the other using Win10 Pro. I only have one

I get the same message if DXKeeper does not upload the QSO to Club Log. I get a message from DXKeeper that the upload failed. Have to click OK on that message. Do you have Club