Date   

locked Re: JTAlert Issue

rob neff
 

Okay, I tried running the shortcut on the desktop as Admin and it runs now. I will make that permanent.

Sorry for the trouble.

Rob KW2E

On May 11, 2021, at 7:50 PM, rob neff via groups.io <rob=houseofneff.com@groups.io> wrote:


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 module.

The issue is that under my windows 10 profile, which is the profile the app was installed under, JTAlert 2.50.1 runs fine. When I sign out and sign in as my wife the app will display but I get no call sign window, it does not read the band I am on and will eventually error out saying it cannot talk to wsjtx on the ip and port (which is correct according to the ini file). Reinstalling the app, rebooting, nothing helped. Even the program updates option in manage settings says error downloading data until I click check for updates.

Then a few moments ago I saw Laurie’s reply about jtalertv2.manager doing a number of those functions so I signed in as my wife and sure enough, that app is not running. On my profile I see a CMD instance as well as the manager app but on her profile, nothing. Attempting to run the manager executable just immediately closes. Executing it from a command prompt says it is expecting -I, init string.

Is there something I can do at this point to troubleshoot further? I don’t see anything strange in the debug log files.

Thanks,

Rob KW2E





locked JTAlert Issue

rob neff
 

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 module.

The issue is that under my windows 10 profile, which is the profile the app was installed under, JTAlert 2.50.1 runs fine. When I sign out and sign in as my wife the app will display but I get no call sign window, it does not read the band I am on and will eventually error out saying it cannot talk to wsjtx on the ip and port (which is correct according to the ini file). Reinstalling the app, rebooting, nothing helped. Even the program updates option in manage settings says error downloading data until I click check for updates.

Then a few moments ago I saw Laurie’s reply about jtalertv2.manager doing a number of those functions so I signed in as my wife and sure enough, that app is not running. On my profile I see a CMD instance as well as the manager app but on her profile, nothing. Attempting to run the manager executable just immediately closes. Executing it from a command prompt says it is expecting -I, init string.

Is there something I can do at this point to troubleshoot further? I don’t see anything strange in the debug log files.

Thanks,

Rob KW2E


locked Version 2.13.10 functions, mostly -

W Ramsey <km4jok@...>
 

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 x64 computers – they just crash with error messages. 

 

I’ve requested help on this group, but the input I received has not resolved my issue.  No, the cause is NOT Windows Defender.  So I’ll no longer waste any more of my valuable time trying to make the latest version(s) functional.

 

I’m delighted to say that Version 2.13.10 functions fabulously on both my computers with one exception, there’s no data (blank) in the Band Activity Display, it just says “pending”.   I’m okay with this because I ONLY use JTAlert to post WSTJ-X QSOs to ACLog which v2.13.10 does magnificently.   If WSTJ-X would build an QSO interface to ACLog I wouldn’t need to use JTAlert at all.

 

73s

William

 

 

 

 


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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 the JTALERT instances and I told the program to always ignore them.  I closed everything down, rebooted and lit everything up again.

Malwarebytes has saved my butt several times when my Norton Antivirus did not find an offender.  So, if it stays running I will keep Malwarebytes.

Thanks much for the help Laurie. 
Steve - AD4K

On Tue, May 11, 2021 at 8:21 PM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
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 by telling MalwareBytes to ignore the entire HamApps folder in the Program Files (X86) directory but it did not load the large, new decode window.

Anyway, thanks for the help.  It really stumped me.  Windows updates always cause something to change but this was new this time.

I will be able to figure it out eventually now that I have the program running as it was.  If I figure it out I will let you know.

Again, thanks for the help.  Regards, Steve AD4K

On Tue, May 11, 2021 at 8:03 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 12/05/2021 9:55 am, Steve Roth - AD4K wrote:
Okay, things getting worse.  Now the old style decode window is not working.

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 your PC Protection software and allowing it to permit JTAlert (and its child processes) to run without interference.

de Laurie VK3AMA


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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 by telling MalwareBytes to ignore the entire HamApps folder in the Program Files (X86) directory but it did not load the large, new decode window.

Anyway, thanks for the help.  It really stumped me.  Windows updates always cause something to change but this was new this time.

I will be able to figure it out eventually now that I have the program running as it was.  If I figure it out I will let you know.

Again, thanks for the help.  Regards, Steve AD4K


On Tue, May 11, 2021 at 8:03 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 12/05/2021 9:55 am, Steve Roth - AD4K wrote:
Okay, things getting worse.  Now the old style decode window is not working.

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 your PC Protection software and allowing it to permit JTAlert (and its child processes) to run without interference.

de Laurie VK3AMA


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

HamApps Support (VK3AMA)
 

On 12/05/2021 9:55 am, Steve Roth - AD4K wrote:
Okay, things getting worse.  Now the old style decode window is not working.

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 your PC Protection software and allowing it to permit JTAlert (and its child processes) to run without interference.

de Laurie VK3AMA


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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

On Tue, May 11, 2021 at 7:57 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 12/05/2021 9:32 am, Steve Roth - AD4K wrote:
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 my rig, then HRD, the WSJT-X the JTALERT.  WSJT-X is working as it should.   JTALERT came up normally but the new style window showing the callsign blocks won't come up.  This is the first difficulty I have had with the new updated JTALERT program.

Windows update usually make be make some adjustments but this one has me stymied. 

Any suggestions?

Steve  AD4K

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 are controlled by that Manager process.

Are you able to bring up the "Help -> About" window from the main JTAlert window? If not that too is also controlled by the Manager process.

de Laurie VK3AMA


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

HamApps Support (VK3AMA)
 

On 12/05/2021 9:32 am, Steve Roth - AD4K wrote:
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 my rig, then HRD, the WSJT-X the JTALERT.  WSJT-X is working as it should.   JTALERT came up normally but the new style window showing the callsign blocks won't come up.  This is the first difficulty I have had with the new updated JTALERT program.

Windows update usually make be make some adjustments but this one has me stymied. 

Any suggestions?

Steve  AD4K

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 are controlled by that Manager process.

Are you able to bring up the "Help -> About" window from the main JTAlert window? If not that too is also controlled by the Manager process.

de Laurie VK3AMA


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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


locked Re: Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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


locked Windows Update - JTALERT Lost the large callsign "block window"

Steve Roth - AD4K
 

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 my rig, then HRD, the WSJT-X the JTALERT.  WSJT-X is working as it should.   JTALERT came up normally but the new style window showing the callsign blocks won't come up.  This is the first difficulty I have had with the new updated JTALERT program.

Windows update usually make be make some adjustments but this one has me stymied. 

Any suggestions?

Steve  AD4K


locked Re: Some New Feature Ideas/Requests

Marlo Montanaro - KA2IRQ
 

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

--
73,
Marlo
KA2IRQ


locked JTAlerts V2.50.1 Kudos

Carl - WC4H
 

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 Pi 4 (armhf or arm64).  A deb package would be nice but compile instructions work also.

Thank you for your efforts.
Carl - WC4H


locked Re: Variable width of options line?

HamApps Support (VK3AMA)
 

On 12/05/2021 6:51 am, John Holmes W9ILY wrote:
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 I'd think it would be good to be able to reduce the size of the JTAlert window as well. Just an idea...
John W9IL

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.
   

Eventually, when those two displays are moved over to the new .NET 5 code-base (introduced with JTAlert 2.50.0), the main window becomes irrelevant, at which time it will be replaced with either a small floating toolbar or an icon in the Windows notification area (or both), I haven't decided how that will play-out.

de Laurie VK3AMA


locked Variable width of options line?

John Holmes W9ILY
 

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 I'd think it would be good to be able to reduce the size of the JTAlert window as well. Just an idea...
John W9ILY


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed

Jorge EA8TL
 

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 kind.

EA8TL
73


locked Re: JT 2.50.01 with WSJT-X 2.3.1

Carl - WC4H
 

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


locked Re: JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

Paul
 

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 different account than the one I have been using during this confusing time.  That account must have been created when I first started to get involved with digital modes a couple of years ago.

 

Now that I realize what has happened, I can hopefully amalgamate all my groups under one account (the one that includes this group, of course) and eliminate the other account!

 

Thanks again.

 

73…  Paul (VE3PS)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: May 10, 2021 21:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

 

On 10/05/2021 2:34 pm, Paul wrote:

I have never seen the screen you captured and included below.

 

Perhaps you could point me in the right direction.

 

Thanks…  Paul (VE3PS)


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 the settings for your self, simply click the "Your Subscription" link that is shown at the bottom of all group emails.

This is what I see at the bottom of all emails...



de Laurie VK3AMA
 


locked Re: JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

HamApps Support (VK3AMA)
 

On 10/05/2021 2:34 pm, Paul wrote:

I have never seen the screen you captured and included below.

 

Perhaps you could point me in the right direction.

 

Thanks…  Paul (VE3PS)


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 the settings for your self, simply click the "Your Subscription" link that is shown at the bottom of all group emails.

This is what I see at the bottom of all emails...



de Laurie VK3AMA
 


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed

HamApps Support (VK3AMA)
 

On 10/05/2021 7:49 pm, Mike G0LQI via groups.io wrote:
Hi Laurie,
I have been testing the May 2nd beta with HRD6 for several days now and have had no instances of FT4 sub-group logging. Previously I was getting one instance every seven QSOs on average. Thanks for all your work.
73 Mike G0LQI

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 weeks time.

de Laurie VK3AMA
  

2201 - 2220 of 36987