In case anyone wants to see the history on this, the original thread was called "Multiple Grids per QSO - Grid boundaries and corners." started on 7/22/19

The FCC database is the primary source. If the most recent FCC download (downloaded 8-June 2020) , WI9D is listed as in AZ. The Callsign database is the only source of US State data that JTAlert uses

Hi Laurie, I just tested the new multiple grids per QSO feature. Now my grid count in JTAlert exactly matches that in DXKeeper. (19 additional grids found by JTAlert) Very nice! And just in time

Hi, I have a question as to how grid alerts are handled. Is the grid part of the call sign database? In the picture below, WV4P is initially alerted as a needed prefix. In the next section, calling

You're only turning it off in order to be able to download the file from a known SAFE site. You then add the HAMAPPS directory to your SAFE exemptions on your antivirus, and turn it back on. An

How does JTAlert determine the US state of a station? Today, I worked WI9D. He was showing on JTAlert as being in Arizona despite his Wisconsin grid square (EN53). It was logged as Arizona with the

Hi, I just installed jtalert 2.16.7 on my Win10 pc.  I'm having a problem opening the settings window...nothing happens when I try to open settings.  I happen to recall a post talking about windows

I ran into a similar issue with the download. I turned off "Avast", successfully downloaded, turned on "Avast" & then installed successfully. Environment is Win 7

Hello Laurie, Thank you for your reply. Despite the fact that I had looked at Log4Om settings several times I had not noticed that I had the wrong UDP INBOUND MESSAGE selected. Rectifying

Sid, Does the QSO get logged despite the error popup? If not, than likely you have not setup Log4OM correctly. See the JTAlert Help File "Settings -> Logging -> Lo44OM V2"

Hi Laurie, I believe it is not zone but call area. Once it was required in the days when calls were strictly issued by call area, now calls can be moved at will there's no longer a

JTAlert lists only the Audio devices the OS tells it are available in response to an api call. Since your on Win10, try a Windows restart. de Laurie VK3AMA

I believe JTAlert is doing EXACTLY what is expected with that callsign. AH6P should be signing /W4!

Looking at a US map with a zones overlay, I note that zone 4 covers a majority of the US land-mass, perhaps he should be signing AH4P/K to indicate he's operating from the US or is

The problem is the "/4" AH6P is using. The JTAlert cty.dat file parsing is returning KH4 which is Midway, I don't know if that is correct or not If he had signed for the other US

Please send me a zipped copy of your adif file. Send it direct to (remove spaces)... vk3ama . ham . apps @ gmail . com de Laurie VK3AMA

Saw this.....but he's in Hawaii and working from a 4 zone. So how do we get Midway? 2.16.7 I can just put his callsign in WSJT-X and it shows up like this. Mike W9MDB

Place JTAlert in your safe file, and have exceptions for JTAlert. The trouble with many anti-virus programs, is that they have a lot of false positives.

Just a few moments ago, I downloaded the new versions of JTAlert and WSJT. It was a fast download – using Firefox. I also use Chrome and Edge. I installed both without issue. Equipment

Thank you Laurie I have found that it is easier to locate the WAE entities which are mostly small islands by searching for their GRID/LOCATORS. Amos 4X4MF