> Hey all, > > I sent a support request through the app so I apologize if this is a duplicate for some. However I have more information based on Laurie’s response about the jtalertv2.manager

I greatly appreciate Laurie’s hard work and effort making JTAlert a valuable tool to many of us. However, JTAlert versions 2.50.1, 2.50.0, 2.16.17 and 2.16.16 will not run on my two Windows 10

Okay, got JTALERT running normally along with Malwarebytes. I deleted Malwarebytes and got everything working with HRD, WSJT-X and JTALERT. Then I downloaded Malwarebytes and ran it. It found all

Okay, I deleted MalwareBytes and got the program working as usual. Funny, this is the first time that I had this problem EVER with old and new JTALERT programs. I got JTALERT program mostly running

Since you had a Windows update, the simplest fault-resolution task you can perform is a Windows restart. If that doesn't resolve your newly experienced issues then move onto managing

I could bring up the help windos but it will not close. I am gonna delete the MalwareBytes program and start over. Will advise. Thanks

If the new Callsigns window is not showing, the likely culprit is your PC Protection software interfering with the JTAlertV2.Manager.exe process. All the new 2.50.0 introduced windows

Okay, things getting worse. Now the old style decode window is not working.

Oh, found that the old version of the "callsign blocks" window is running and not the new style. Strange.

I did a Windows 10 update today. When running JTALERT my Malware blocker quarantined the JTALERT.EXE file. I gave the blocker permission to ignore the entire Hamapps folder. After that, I brought up

Cool... but what if you want to highlight above -10dB? ("Strong" is relative!) -- 73, Marlo KA2IRQ

Hi Laurie. I really like some of the new features of ver 2.50.1. Very nice work. Are you still planning for a Lilnux version down the road? Of special interest for me would be one for the Raspberry

Sorry, no. Not at this time. The width of the main JTAlert window is constrained by the width of the display area of the Log Fields and the Confirmed Bands/Modes.

Laurie, Is is possible to have the options line (Alerts, Settings, etc) made as a variable width, maybe with a fixed minimum width so it doesn't get "lost"? When I reduce the size of the JTDX window

Hello I confirm that the beta has solved for the moment the problem of <submode: 3> FT4, now they upload the qsos to clublog livestream in the correct mode. Thanks Laurie for your help, very

Have you tried WSJT-X V2.4.0-rc4? I'm using that one with JTAlerts 2.50.1 and all seems to be working fine so far. 73. Carl - WC4H

Thanks Laurie. You have just solved another mystery related to my recent attempts to participate in this group. Although I had no idea, it turns out that my subscription to this group is under a

That image was taken from the Moderators area of the Group settings. It shows the default email delivery options for the group that gets applied to all new memberships. To find

Tnx Mike. Stay with the Beta until the next public release. The Beta is good until 6-July-2021 after which it will cease functioning. I expect the next public release to be in 3 to 4

Highlighting high db decodes is already available. Unfortunately it didn't get documented in the help file when I made the change. After a bit of searching, I found the relevant entry