All of a sudden this started happening, no logging to acl. I have restarted the app and upgraded to 2.16.13 and the problem still exists. Any help on this one. Thanks Deni - WB0TAX

John, Your friend is welcome to join this group, there are no restrictions. More Callsign slots is on the "currently being worked on" list (in fact unlimited callsign display), but I cannot provide an

Setting up a new computer for the shack. I'm unable to get the "Show Log Fields" to display. It is grayed out so can't access. Ideas?? Al W1JHU

Hello Laure- Would be nice to filter USA calls from the display. Currently the NA continent filter removes calls that are of interest on some bands, for example 6M. Thanks; -- Bill Barrett W2PKY

i have been using JTAlert with WSJT latest versions with my IC-7300 and i3 PC successfully. Lately I notice on the WSJT waterfall, the signals become distorted and will not decode with JTAlert running

I see numerous posts on this topic, but no solutions. Unchecking "Color Band Activity" had no effect. I have the same problem. Double-clicking in the WSJT-X window works as expected. . Tested on Win 7

I forgot to mention that in addition to the previously worked 8P and 6E prefix stations calling CQ not having a gray background in the WSJT-X Band activity column, I also have noticed that they also D

Every time I have windows upgrade I have problems with software that was running good begins to not work properly: SOOO! I now set windows to up grade when I want and I hold off as long as can. Since

Hello- Attempting to download the 2.16.13 latest rev and met with setup files are corrupt. Anyone else having this issue?

Using JTA version 13, I am getting "New Grid" and "New Prefix" announcements OK, but no colored callsigns in either JTA or WSJT-X to identify which call is the wanted grids or prefix. When a "Wanted C

I am looking for some additional members to participate in JTAlert testing. My expectation is that members of this group are computer savvy, are frequent users of WSJT-X and its modes, are comfortable

Hello Laurie, I hope all is well up there. I have had a request from a mate who is not a forum member to ask for this, and I also think its might be handy. FT8 is soooooo popular now that jtalert cann

In WSJT-X, when stations that I have not worked call CQ, colors the entire decoded CQ line is green. as is expected. When a station has been worked before on a band, the background of the callsign is

In previous release notes the quoted JTAlert supported UDP Multicast IP range for WSJT-X was incorrect. The correct range supported by JTAlert is 239.0.0.0 to 239.255.255.255 The previously suggested

Power & 'net been out for three days, bad storm also took out my main antenna, and a small (minor) house fire have all conspired to shut me down for the past three days. I hope to catch up on email (a

Is there a way to change the browser to Chrome using the "Q" button on the right side of the JTAlert decode window? -- de Fred KE0EF

Hi all, Tried to update JTAlert this morning (v 2.16.12) but get the following message when installing : Run the installation file as administrator and added an exception for my AV program without luc

Steve, JTAlert will continue to Alert on a Wanted entity until it is removed from the Alert Database except when the Callsign just logged becomes a B4 then that Alert is no longer triggered for that C

Something that I see fairly often, and not a big deal, but.... I will get an alarm for new DXCC or mode on a band, and work the station. It gets sent to DXKeeper as expected, and the "OK" box pops up.

No great surprise that when Windows 10 decides to update it messes with settings. Previously if there was a call in the JT Alert window I could click on it and it would then populate the Generate Std