Mike, so are you saying the OPs's issue was that he had entered a port number in WSJT-X that was not available? As an aside, Amateur Radio is technical hobby and many enjoy the challenge of getting co

#FT8

Steve, perhaps you need to review the settings you have for the "Rebuild Alert Database" categories, and also the alert settings. I suspect there is a discrepency between your expectations of what sho

<snip> Steve, you are confusing the manually maintained worked before tables in JTAlert with the automatic system that gathers information from you connected logging program and QSOs in session. The t

Steve, JTAlert loads worked before data form your logging program at startup and updates it as you log stations, if you don't have JTAlert doing the logging into your logging program then it will not

Tony, WSJT-X does not require any .NET prerequisites. Check the documentation for what is required for JTAlert, you don't need to upgrade your current .NET framework, but you do need to install the ri

Hi Bill, as you are running DX Lab Suite I suspect you may have enabled SpotCollector's interoperation with WSJT-X. SpotCollector is not multicast compliant, therefore it cannot share the WSJT-X UDP p

Hi Adrian, and Bill, let me try and clarify a couple of things. Using a UDP resend facility is a half-baked solution that should only be necessary if the application a the end of the chain does not su

Dave, you are checking the wrong process. Both the 32- and the 64-bit versions of JTAlert run the 32-bit executable JTALert.exe. The process that is different for 32- and 64-bit is the one that runs J

Hi Jim, and Laurie, I would recommend that you do not worry about the size of your exported ADIF file, even on a relatively slow PC it will be processed fast and that is done in the background without

Hi Andy, that does appear to be the case, I expect that Laurie has chosen to install the 64-bit JTAlert into "Program Files (x86)" because some legacy parts of it are still 32-bit. It doesn't actually

Andy, you don't appear to have the recommended Microsoft Windows Desktop Runtime v5.0.7 installed.

Hi Greg, that shows you have the 64-bit version of JTAlert installed, do you have the 64-bit version of the .NET 5.0.7 Desktop Runtime installed as well?

Hi Jim, it is not quite that simple and depends what logging application you use. As I understand it JT Alert scan your log for worked before stations every time it starts, it does this silently in th

Hi Jim, "Settings->General->Show DXCC, grid, and worked-before status". For more fine-grained control you might uncheck the "New Call" and "New Call on Band" highlighting options on the "Settings->Col

Hi Laurie, this turns out to be a long standing defect. It is due to code in WSJT-X that avoids sending duplicate UDP datagrams, which has been in place for many versions. Disabling "Monitor" causes m

Hi Laurie, that was not an intentional change, thanks for the report, I will investigate.

OM (Jeff?), have you checked the JTAlert Settings menu option "Multicast on loopback interface"?

OM, you have probably installed the wrong version of Microsoft Windows Desktop Runtime, you need the 64-bit version if you are running the 64-bit version of JTAlert. Note also, for a short while at le

#FT8

Dave, how can that work if JTAlert does not know which calls you have worked?

OM, I am not sure if it matters, but you have checked the "Multicast on Loopback interface" option but you are not serving on a multicast address. Also check no other application is serving on port 22

#FT8