JTAlert hanging when logging has been experienced by some users of HRD when using an MSAccess log. Are you using an MSAccess log type in HRD? In most cases the fix was to perform a full export of thei

JTAlert does not allow removing menus. Are you referring to JTAlert or some other application? Please post an image of the window with the missing menu. Don't post an image of your entire desktop, jus

FYI, the enabling of that option is not the problem. The problem is having that option enabled AND having the port set to match the WSJT-X UDP Server port (typically 2237). They should never match. de

JTAlert repeating decodes and logging is caused by having the "Resend WSJT-X UDP packets..." in JTAlert or "Secondary UDP Server (depreciated)" in WSJT-X enabled AND having changed the port to match t

The important bit, easily missed, at the above link is... de Laurie VK3AMA

Charlie, A file being held open produces a different error message to that reported in this thread. It is typically an access denied error. de Laurie VK3AMA

The problem is that your Protection software was interfering with the installation. The installer when extracting files creates files in a temporary location first then moves them to the install locat

There is no need to uninstall JTAlert first. This has always been the case, just run or rerun the installer is all that is needed. The same if downgrading versions, just run the old installer. de Laur

If 2.50.2 works while 2.50.4 does not that indicates to me that your PC Protection software is blocking the TCP port access to the HamSpots server (which hosts the messaging services) for the 2.50.4 v

Tnx for that. I had a brief look, but I don't know how accurate or complete is the JA data. I have always been under the impression that JA Hams outnumber other countries including the US in terms of

#Beta

Why did you change the UDP port of WSJT-X from the 2237 default to 2236? Something or someone must have prompted you to make that change. 2236 is likely being used by another application trying to wor

Buddy, Are you asking about a financial contribution? While in the past I have declined such offers, in recent times I have warmed to the idea thanks to the economic impacts of Covid-19. I have not ye

The messaging code within 2.50.4 and 2.50.2 is identical. Your switch to 2.50.2 fixing the problem is likely coincidental and occurred at a time when one of the messaging services running on the HamSp

If there is an accurate and maintained list of JA Callsigns and their Prefectures or some reasonably accurate way to programmatically determine the Prefecture perhaps from an official Callsigns databa

#Beta

If there is a link to a Callsign+RDA list please let me know and I will download and investigate its suitability. de Laurie VK3AMA

#Beta

The easiest way to test the entire Messaging infrastructure is to send a message to yourself. This will test all parts of the pipeline, Your PC -> Messaging Server -> Your PC. de Laurie VK3AMA

I replied to your previous message regarding this. See https://hamapps.groups.io/g/Support/message/36449 Unless there is a published list of Callsigns and their current RDA then it wont be possible to

#Beta

What version of WSJT-X? Do you have WSJT-X set to use multicast UDP? If not, do so. See the JTAlert 'Help -> WSJT-X UDP Setup" menu. de Laurie VK3AMA

You need to install the "DESKTOP" version of the .NET runtime. Also the architecture type needs to match that of the JTAlert installer, both need to be X64 for 64bit Windows or X86 for 32bit Windows.

Tnx for the update. de Laurie VK3AMA