The easiest way to test the entire Messaging infrastructure is to send a message to yourself. This will test all parts of the pipeline, Your PC -> Messaging Server -> Your PC. de Laurie VK3AMA

This is why in all my messages, release notes & help files, I deliberately use the word "Desktop". Not much more I can do if that advice goes unheeded or ignored. de Laurie VK3AMA

Sorry Jim, you're incorrect. The first reply (mine) to the initial post in the thread advised setting up multicast UDP along with instructions on how to find the setup instructions. Subsequent message

It is not working since you didn't follow the setup advice. You have not setup UDP Multicast in WSJT-X. Without doing that you cannot have ACLog and JTAlert concurrently working. While you continue to

The "???M" in the titlebar text indicates that JTAlert has net established UDP comms with WSJT-X. I suggest using the JTAlert "Help -> WSJT-X UDP Setup" menu and follow the simple setup instructions p

Also, check the Callsigns window Options (click the gear icon) and see what you have set for the "Wsjtx reply" setting. Perhaps you have it set for double-click and have only been using a single click

OK. Since you're clicking Callsigns in JTAlert, that indicates the UDP comms between JTAlert and WSJT-X is working correctly. If the comms was broken than JTAlert would not display callsigns or report

Its not complicated. If you hate Ham Radio and admit to not being a Computer user (only a commuter user whatever that is), why are you getting involved in the Digital modes which by their nature requi

Interesting you mention Blat. I recently went looking for an alternative as it has some serious shortcomings working in modern Email environments requiring SSL/TLS to access SMTP servers. I found CMai

I never said it was a logging problem. The problem is very likely caused by accessing the log at the end of a decode period when the worked B4 checks are performed. Crashing at the end of a period as

You don't have the Callsigns window open. Use the "View -> Callsigns Window" menu of the main JTAlert window. de Laurie VK3AMA

Click the gear icon or press F2 when the window is active (has focus). This is not new, it has been that way since 2.50.0 for all the windows introduced with that version. Alternatively, activate the

Bill, Sorry, no idea. This is the first report I have seen of this type of behavior. If your friend hasn't already done so, a Windows Restart wont hurt. I have lost count of the number of times that u

Tnx Greg. Since those files didn't exist that suggest to me that you were upgrading JTAlert from an old 2.16.x version. Was that the case? de Laurie VK3AMA

Tnx Andy, Good to hear. de Laurie VK3AMA

Already examined. Check you inbox for my answer & solution. Thanks de Laurie VK3AMA

Your in the wrong config directory if your seeing "JTAlert" & "JTAlertX" sub-directories. There are two config directories, one with above mentioned sub-directories is used by the main JTAlert. They c

Tnx Jim, Something to try... With a failing JTAlert 2.50.3 install stop JTAlert then delete any files starting with "Callsigns_" in the %localappdata%\HamApps\JTAlert\<your_callsign>\Config\ directory

What is event viewer showing with respect to the JTALertV2.Manager.exe faulting? Have you tried disabling pcmatic, it could be interferring. I note it was mentioned explicitly in your posted event xml

That is a classic problem caused by a defect within NET 5.0.7 breaking the Audio Library used by JTAlert 2.50.0 & 2.50.1. JTAlert 2.50.2 & 2.50.3 uses a patched Audio library that avoids the NET 5.0.7