Laurie: In the new version of JTAlert (2.50.5), I note that for some windows, like the Decodes window, it makes sense to clear the panel after each decode, while for others, like the Callers panel,

Like I said that is not always true. I've filled a number of needed band slots simply by calling a needed entity that was not currently transmitting but was receiving me as indicated by Ham Spots and

I am not seeing the main window.. Don't know why. Just a window with Callsigns #1 That is my issue I see Tks gerry

The buttons for testing Sound and adding/removing Countries are where they have always been, within the Settings window. That hasn't changed for many years now.

I just downloaded the latest version of JTalert, I have no sound and there is no button to test sound. Also there is no place to add or remove wanted countries etc. I tried reinstall and still same

If you see yourself spotted it doesn't mean there is an op ready to answer your call. Many operators leave their rigs on 24/7 to spot for networks. The only way to know for sure is to hear them on the

I believe I have set up Multicast correctly but wsjt-x log info does not transfer over. Am I missing some setting?

That would involve a lot of internet activity, and hitting up the two sites creating more congestion at the sites. Wouldn't it be easier just to keep a browser open to Hamspots, as it does pick up

Often while using FT8 I've seen needed entities in PSK Reporter and/or Ham Spots that are receiving me but not currently transmitting on the band. I'll give them a call and many times they respond and

The Callsigns window is controlled by the JTAlertV2.Manager.exe process and that process is started by the main JTAlert.exe process which is also the main window. Likely the main window

First do a Windows restart to ensure that any pending updates are applied. Then check that you have WSJT-X and JTAlert setup correctly for multicast UDP. See the JTAlert "Help -> WSJTX UDP Setup"

If you're using Unicast then it is likely that ACLog is seizing exclusive control of the UDP port and preventing JTAlert from receiving the UDP messages. Either turn off ACLog integration with WSJTX

Mike, Thanks for the tip. Deleting the directory restored the JTAlert Main window and the alerts have been reconfigured. So everything looks "normal" now. However: 1. no WSJT-X decodes are being

I went from an early 2.x version (2.05 I think) to the newest version, and now it does not monitor any longer from WSJT . I installed the .Net 64 bit . Ideas? 73 Jim NX0R Hays, KS

Try removing C:\Users\[username]\AppData\Local\HamApps That will start it all over again with a new config. Mike W9MDB

All, I am assisting a local ham to troubleshoot the following problem. He has upgraded from an earlier version of JTAlert 2.16.17 I believe to version 2.50.5 X64. .NET 5 Desktop has been installed

Thank you all for you wisdom is pointing me in the right direction. I will seek the help of local hams in my group to help me with the migration. I am pretty good with general pc issues but i am

Second the MariaDB install. Works great. https://www.youtube.com/watch?v=C7f-RZOnmDs Alton N4IDH

Got it Laurie, thanks. Bob -- K6RWM

Just make the window active. Click anywhere on the window then use the F2 Key. That will open the Options popup the same as if you clicked the gear icon if it was visible. This is the