Hello Laurie - the date that is showing is 2018-01-01... as this date is not today's date or anything recent, I made no changes. Will wait to hear from you. Thanks. C -- Craig NZ4CW

Check the "Alerts -> Worked B4" section of the Settings window. What date is shown for the highlighted setting shown in this image? If it is todays date or a

Something is very screwy with your PC environment if you cant minimize the Messaging window. As a first step, restart your PC and see if that resolves the issue. de Laurie

Your running DXKeeper. Have you perhaps enabled WSJT-X integration within DXLab SpotCollector? If so, that will be the problem. DXLab supports only unicast UDP and would be blocking

There were no UDP changes in the code with 2.50.6. There haven't been any for several versions now, so it is unlikely that something is fundamental broken in JTAlert. What other changes have you

Does it tell you that you have the correct version of .net installed when you load JTalert?

Did the re-boot. No joy. Un-installed and re-installed 2.50.5 and still no go. Title bar on JTAlert shows “JTAlert 2.50.5 KE5WCT [???m,,DXK,#1] (updates)”. I think the ???m is the band being

Try a reboot. I have that problem when I switch from FT8 to FT4 in WSJT . A reboot restores function. I don't seem to have that problem going the other way. 73 Jim NX0R - Hays, KS

Installed 2.50.6 and now no display of calls, decode in wsjt-x ok. Went back to 2.50.5 and now it also will not displace the decodes from wsjt-x. 73 de KE5WCT Mike Wilson Sent from Mail

OK, Tnx Laurie. I will check my settings some more. Glenn K4ZOT

I continue to struggle with getting B4 to behave accurately. For example, I called VK6EI this evening on 30M FT8 based on JTAlert showing a not worked status. When the QSO was completed and logged

Running 2.50.6 and found that the chat box is now always on top. That option is NOT checked and I even toggled it to make sure. It also will NOT minimize as well. I have to uncheck Position Locked

Mine is working fine with the new version too.

Just sent a test message here to myself with new version and it worked with no issues or configuration changes... 73 Jeff kb2m

Working for me! Thanks!

Laurie has reported that a few people were having the problem you are having. Because of that he just released 2.50.6 yesterday that includes a fix for this issue. Monty, NR0A

I must have had a bad install. Installed the .6 version (Had the .5 one installed) and the problem went away. A bad install is the only thing I can think of. TNX es 73 Jim NX0R - Hays, KS

I tried to send one to myself (Didn't know that was possible) But I did not get a response. Is there some configuring to do on messaging? It always worked before.

2.50.5 is the version I am using

I got your message, but you apparently did not get the 2 I attempted to send back.