locked Re: Transmit frequency

Ernie Barnhart


Thank you for your comments.

I thought in earlier versions when ctrl-clicking a callsign in JTAlert that  it passed that key combination on to WSJT-X that changed the transmit frequency to the receive frequency. The new version only appears to be passing the click key (not ctrl combination) to WSJT-X.

Thank you again for all you do. 

de Ernie N8DVE

locked 2.50.0 not logging propagation data


2.50.0 not logging propagation data ... Item is ticked in "Logging" options.  Has been working in previous versions.

Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.3.0, JTAlert 2.50.0, HRD Deluxe v6.7
FTdx-3000, SignaLink USB

locked Re: JTAlert Will Not Install

Ed Wilson

Thanks for the link, Laurie!

Well, I downloaded the software and ran it and got the message:

"This app cannot run on  your PC".

I am running 32-bit Windows 10 updated to the most recent version. Do you have any clue as to why I am having this problem?

Ed, K0KC

locked Re: My Errors with JTAlert 2.50 32 bit Windows 10 PC

Bill Rogers

I have seen exactly that on my one 32-bit PC with windows 10 pro. All my 64-bit machines are running fine. 

Bill K2TER

On Apr 13, 2021, at 8:52 PM, William Wagaman <n3gty@...> wrote:

Hello Bill here N3GTY has anyone had this error with the new version of JTAlert:
I have 2 computers the 64bit PC windows 10 no issues ... but the errors below are on my 32bit machine. 32 Bit system because it is an older dual core with 4gb ram also windows 10 Any suggestion would be appreciated. Thanks in advance Bill

Unable to execute file:
C:\Program Files\HamApps\JTAlert\pulginsX\FrameworkChecke.exe
CreateProcess Failed; code 216
This version of %1 is not compatible with the version of 
Windows your're running. Check your computer's system
information and then contact the software publisher.

I get this when it is checking the Dot Net Version
I get this error when attempting to run JTAlert


locked JT Alert V2.5 is Awesome - many thanks

David Burden

Hi Laurie,

Thanks so much for your efforts on JT Alert, the changes in 2.5 are simply fantastic and the speed is amazing.

Thanks for all you do for us digital devotees.


locked Re: icon messaging #FT8


Thank you Laurie for the quick response

you are right, for the message alert to be visible I have to increase the size of the flag to 10 at this size the window is not fluid anymore 
your idea to add a control if it is feasible or put a badge instead

73 Denis F8NHF

locked Re: Callsigns not always decoding into Callsigns window.

Walt Flesher, W6SA

The problem seems to have resolved itself after a hard reboot of the computer after shutting everything down.  So far, so good...

Keeping my fingers crossed.

Walt, W6SA

locked Re: Thank You!!

Jacques F1VEV

Hello  agreed installed all through Win4Icomsuite latest version of WSJTX  and only HRD 6 logbook on SQL  on WIN10 no issues  grat stuff no just need to get used to new ergonomy , keep sending the mouse to the wrong part of the screen force of habit.......

Thank you Laurie 

locked Re: another dumb qusetion.... re F12

John C

excellent. thanks for that one Mike




locked Re: another dumb qusetion.... re F12

Michael Black

Right-click the gear icon....
Or use ALT+F4 for keyboard shortcut

Mike W9MDB

On Tuesday, April 13, 2021, 11:18:36 PM CDT, John C <> wrote:

OK, I pressed the F12 and enabled the 'Band Heat window'   however the only way I can close it down again is to shut down Alert. Pressinf F12 a second time does not close it...   Have I missed something ???



locked Re: Version 2.50.0 request

John C

thank you Laurie..   I did not even see this...  Adjusted and looking good.   thanks again



locked another dumb qusetion.... re F12

John C

OK, I pressed the F12 and enabled the 'Band Heat window'   however the only way I can close it down again is to shut down Alert. Pressinf F12 a second time does not close it...   Have I missed something ???



locked Re: UDP ERROR

Ed K0iL

I'm having the same issue after updating to latest version.  Everything stopped working.

73, de ed -K0iL

locked Update top version 1.50.0 gone wrong

Ed K0iL

Subject correction: Updated to version 2.50.0 gone wrong.  
Updated to JT Alert 2.50.0 and nothing works any longer.
Only the top menu line appears.  
No Sound either when testing sound.
My personal settings all seem to still be there. But it's still dead after restarting both of WSJT-X and JT Alert.
UDP Comm Failure error message states unable to communicate with WSJT-X process. Says see JT Alert Help for correct WSJT-X UDP Setup. That help page now recommends new UDP multicast addressing. So tried that. It still doesn't work.
Should I have updated WSJT-X first from 2.2.2 to latest version?
Anyone else having this problem with JTAlert's new version 2.50.0?

locked Re: 2nd instance Callsign window not following JTAlert main window on minimize - Defect Confirmed.

Gary Yarbrough, KE5TD

On Tuesday, April 13, 2021, 07:31:12 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 14/04/2021 5:45 am, Gary Yarbrough via wrote:
>From the settings window in the Callsign window I have ticked the box for the Callsign window to follow the JTAlert main window and it works on the 1st instance.  On the 2nd instance I also ticked the box  but the Callsign window does not minimize when I minimize the JTAlert main window. Anyone else having this issue ?

Gary / KE5TD


Thanks for the report. I can confirm this is a defect.

I'll correct it for the next release.

de Laurie VK3AMA


Also the Callsign window on 2nd instance is auto closing after about 5 minutes..  The 1st instance is running normal with no issues.

Thanks for the new version I really like it !

73, Gary

locked V 2.50.x Observations

John Petrocelli


  I installed 2.50.x on a spare laptop running Windows 10 and I offer some observations.
  All are intended to be constructive and I welcome any input & critique

  I do like the new release although the new window structure will require a bit of adjustment in my thinking - not too much though.

  The callsign window seems to have some limitation on its text size.
  For someone who is visually challenged, this could be an issue.

  The Main Window used to be attached to the callsign window along with the Menu.
  It would be nice if the Menu would be also available on the callsign window or an option to put (attach) the Main Window on the Callsign Window.

  As others have observed, (I use an ADIF file) the ADIF reading seems very much longer.
  My ADIF file has about 182,000 records Version 2.17.x took about 15 seconds to read it.
  Version 2.50.x takes about 95 seconds.
  As someone mentioned, this may be due to the .NET but I am not sure.
  The above numbers were on the same machine under Windows 10

  I did successfully make 1 QSO with the new version before going back to version 2.17.x/
  Note that I an running 2.17.x on a Windows 7 machine but I may try to get the .NET 5.0 working on that machine.
  If not, I shall clone my Win 10 machine so I can work with the new version without adversely impacting my primary desktop.

  Thank you Laurie for all your great efforts !!!


John R. Petrocelli - WA2HIP
Primary Home Page:


locked Callsigns not always decoding into Callsigns window.

Walt Flesher, W6SA

I upgrade to the newest version yesterday.  I already had Net 5.0 installed.

After the upgrade it took a while before I had any decoding.  No idea what I may have done to start it.

There is no persistence to my callsigns window.  I am presented with a blank window.  After clicking on different menus brought up by the settings icon in the lower right of the callsign screen it will suddenly start to decode for a short time and then present me with a blank screen again.  It seems to work whenever it wants to.

This happens over and over.  I cannot consistently make a contact without the screen going blank while I am transmitting and does not always come back with any calls.  It has been like this since I upgraded.  What am I missing here?  

Great looking program and features if I could only decode consistently it would be a pleasure.

Walt, W6SA

locked Re: api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

HamApps Support (VK3AMA)

On 14/04/2021 11:15 am, Jim wrote:
after installing JTAlert 2.50.0 on my windows 7 computer I get this message.  What did I do incorrectly and how do I fix it?   

Yes I know reinstall it, but I have done that multiple times and it didnt install the file needed.  What do I do now?

Jim K3ybn

Reinstall the NET 5 Desktop Runtime. That particular file is not bundled with the JTAlert installer, it is part of the Runtime.

If reinstalling the Runtime doesn't work, it could mean that your WIn7 PC wont work with the new version.

As it is now, WIn7 SP1 is not officially supported without a paid ESU being installed. That may or may not be your problem. Several Win7 SP1 users have reported success without having the ESU installed. I believe they were all Win7 Pro, are you perhaps running Win7 Home or never updated to SP1?

de Laurie VK3AMA

locked Re: Can't find call sign window

HamApps Support (VK3AMA)

On 14/04/2021 11:11 am, HamApps Support (VK3AMA) via wrote:
For your callsign the are located at %localappdata\HamApps\KF0CUD\config\
Sorry missing an "%" The correct location is %localappdata%\HamApps\KF0CUD\config\

de Laurie VK3AMA

locked Re: Ver 2.50.0 issues

HamApps Support (VK3AMA)

On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.

de Laurie VK3AMA

3761 - 3780 of 37662