OK Eric, 32 bit (x86) appears to be the common denominator. The litany of error messages I assume are "AutoIT errors" after trying to start JTAlert. That is a side-effect of trying to run JTAlert with

Per instance profiles will be coming, but likely not until all the old code and its monolithic Settings window and settings file are replaced. That is not any time soon. But, what you want with per in

#FT8

That's coming, not in the next release, but soon after. The next release has had a significant amount of internal changes to the Callsigns window to allow for varying the size of the Callers panel, wh

#FT8

What happens if you temporarily turn off monitor in wsjtx so there are no incoming decodes are being fed to JTAlert, does JTAlert still show this error? Is it always the same line number? Line numbers

Its on my list. When its coded you will see it first in the Test Team group. de Laurie VK3AMA

A screen-grab showing the JTAlert window would have been more useful. A side-by-side comparison of JTAlert and WSJT-X at the time of the error would be more useful for diagnosis. Did the Wanted Callsi

Are you saying the .NET 5 Desktop Runtime will not install due to an incompatibility error? That should not be the case, unless you're trying to install the X64 version when it needs to be the X86 ver

OM (name? Callsign?) Is this on a 32bit or 64bit system? de Laurie VK3AMA

Bill, An alternative, if you happy that JTAlert is logging the QSOs reliably without error, is to turn off the "logging success" popup but leave the "logging failure" popup enabled. See the "Window ->

See my answer to the other thread you started. https://hamapps.groups.io/g/Support/message/34571 de Laurie VK3AMA

I see your using a Flex, does that indicate you're running multiple instances of JTAlert? If so, since you're using a unicast UDP address (127.0.0.1) you will need to give each WSJT-X a unique UDP por

FYI, this change will be in the next release of JTAlert. de Laurie VK3AMA

That popup cannot be moved. Its position is fixed to the location of the parent window that presented the popup, in this case the main JTAlert window. This is behavior that as existed for many years.

The DT shown in the Callsigns window status bar is a median calculation of the DT values of the incoming decodes. It is calculated over time using a reasonable number of samples to give a meaningful r

No it is not possible to delete callsigns from the previously used list (below the callsign edit field). That list is automatically cleared when JTAlert is restarted. What is the issue you want to res

This thread is discussing Counties, the cublog lookup is for Countries <- note the "r". A subtle difference in spelling, but a significant difference in the lookup type. de Laurie VK3AMA

#FT8

Can you please send me an ADIF export from your Maria log? de Laurie VK3AMA

Denis, OK, something else is happening. Don't worry about the B4logV2 database file, it only used when there is no logger enabled in JTAlert. All your B4 checks are done against your HRD log. Have you

OM (name? callsign?) Sounds should play on all instances. Does the "Sound -> Test Sound Output" menu work on the instances? de Laurie VK3AMA

You can turn off the eqsl flag in 2.50.0. re eqsl, I reached that point a few years back. I got tired of the endless fake QSL requests, especially when I rarely get on air, indicating that people are