Hello, I wanted to have two WSJTXs + one JTDX instance running each with its JTAlert. I can get WSJTXs+JTAlerts alone working but then trying to start JTAlert for JTDX fails, as if it's not

Well that worked... I stopped anything from going to sleep with the Devise Manager and also set the power saver to max performance in the Control Panel. JT Alert has been running now for 3 hours

Thanks Jim I will give that a try.

On 12 Nov 2021 at 14:49, vk3xl via groups.io wrote: > It is some other event created by > some software on my PC that causes > the interruption to the data > transfer. I just have no clue on how > to

Hi Laurie, fine on the lessons learnt, I should have put the version numbers in the original post. The software stops producing alerts and the alert screen is completely blank. JT Alert version 2.50.7

Hello Laurie- The Win10 system was running 2.50.7 I have gone back to the Win10 system because of long DPC/ISR over-runs on Win11. However, seeing the same 2500 usec times on the Win10 system as well.

NO I found I had clicked "don't show it" under "Highlight worked ones" within Notifications. As you said "If the original decode associated with a JTAlert callsign is no

Jorge, If you're able to create an accurate and maintained list I will look at adding support for Spanish Province Alerting into JTAlert. de Laurie VK3AMA

OM, Does JTAlert show an error message? Is this a true crash or simply that JTAlert stops producing Alerts? What versions of WSJTX and JTAlert? Please quote the

Hi all, I have seen similar posts to this problem but yet to find a solution. I have been using JT Alert for 3 years or more and this problem has occurred from the start with my setup. I have used

Is the JTDX non-response to JTAlert callsign clicks affecting all callsigns? Are you clearing decodes in JTDX? If the original decode associated with a JTAlert callsign is no

That is correct Laurie. Even restarted JTDX. DE NS9I

Are you saying that when you switched JTDX to "any messages" it still did not respond to JTAlert callsign clicks? It does in my tests. de Laurie VK3AMA

FYI, That is no longer the case. VK is now following the US model with callsign naming no longer reflect the State of operation. Eventually there will be VK9's operating from the mainland. :-( de

Well seems like nothing changes that behavior. While I like some of the features of JTDX, guess I'll just have to dump it. t u 73 Dwight NS9I

tnx Joe: Really as you mention no realistic to think on continous acces to qrz.com. Any case, I am going to work on the idea of ​​building a list, which can be posted "on a web site" and we

The information would need to be available as a downloadable database (e.g. the US FCC's License database) or directly determinable from the callsign (e.g. Canada's or Australia's systems that map

Currently the Callsigns window (not QSL window) only supports separate views for Lotw and Eqsl decodes. If you want to see both LoTW and Eqsl only Callsigns you will need to have 2

Provided you don't have JTAlert callsigns click handling disabled, JTAlert always sends the appropriate UDP message in response to a Callsign click regardless of the decode type.

Mike, If JTDX stops responding to JTAlert callsign click events when JTDX filtering is applied that indicates a defect within JTDX. JTAlert always sends a correctly