You could be right. Was not sure which program initiated it. I only get over to my dad's 1 or 2 times a week. So when I get there I will get the picture and post it. Bob W8RID

Ken, I previously sent you a link to the latest JTAlert Beta build (sent 2-Jan), did that not correct your QRZ problem? I couldn't find a response from you so I assume

This does not appear (as best I can remember) to be a JTAlert generated error message. Is this a Windows or HRD message? Please post an image of the offending error window.

Simple, set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu. de Laurie VK3AMA

Bill, While JTAlert itself doesn't provide for explicit exclusion of Country of origin decodes, the Decodes window does. Make the "Country Name" column visible then right click

Hi Laurie, Any progress with this issue?

Fixed the UDP problem I posted about before. Forgot to check the 3 boxes that related to UDP. Now everything seems to be working but I am getting this error now: "TCP QSO Data transfer socket

There all kinds of filtering options on the Decode History window. I like using it rather than the regular call display.

You might know that there is another program that does all of that for you. JTDX Best regards - Bry Carling, AF4K

Along the same lines, I would like to see an option to NOT display any new callsigns from a State or DXCC that is already confirmed. This alone would greatly reduce the items in the display. I run 3

Hello Laurie- Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app.

Thanks Laurie for the tip and a great program.!! Neil N4FN

Yes, Yes, Yes, this year I forgot it… Thank you so much and HNY Carlo IK2RPE Da: Support@HamApps.groups.io <Support@HamApps.groups.io> Per conto di HamApps Support

Carlo, Set the Ignore B4 Date to 1st Jan 2020. Settings Window, "Alerts -> Worked B4" section. de Laurie VK3AMA

Doing the DxMarathon 2020 and having set the relevant alarms, I discovered that a Call for which I had a B4 warning (on that band, also grey colored) BUT that I need this year for DxNarathon is NOT

Hi Andy, in theory it works by using a multicast address group rather than the unicast 127.0.0.1 address, unfortunately the tools used to create JTAlert do not directly support

I’m running WSJT- x 2.1.2 and JT alert 2.15.6 along with logger32. What is the best way to receive UDP info on all programs? As jtalert wont receive the udp because logger32 udp map is, is there a

If you have set JTAlert with the Station Callsign of "N4FN/QRP" then the own call alert will only get triggered on that Callsign, it will not trigger if someone calls you without the "/QRP"

Recently I have set up my Elecraft K 2 to work FT 8 in QRP. I have changed my call sign from N4FN to N4FN/QRP. All is working fine and contacts are being made, however when a connection is made even

Thank you for understaning Mike, and I will be delighted to try it over the next couple of days as I get time... Sincerely, 73 - Brian "Bry" Carling, AF4K xtl