Date   

locked Re: 2.50.3 problems

chas cartmel
 

Same motherboard, Ryzen 7 2700X, 1080 GTX GPU. Using W10 21H1 all up to date, Bullguard as AV / Firewall, The JTAlert and WSJT-X folders are whitelisted.
No issues with any of the latest (or any) updates.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of CSM\(r\) Gary Huber - AB9M
Sent: 14 July 2021 12:54
To: Support@HamApps.groups.io
Subject: Re: [HamApps] 2.50.3 problems

 

This is exactly what I am seeing on my computer; ASUS B450F motherboard, AMD Ryzen 5 2600, 16 GB RAM, AMD R500/550 Graphics card, WIN 10 Pro -64 bit with the latest updates and Kaspersky Total security. I am in the process of resetting and reloading this computer because I was also seeing "Windows 10 Black Screen Of Death", which makes me think there was some file corruption in the graphics library.

 

It would be interesting to know what hardware/OS/software is working versus what is not.

 

73,

Gary ~ AB9M

 


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Wednesday, July 14, 2021 4:09 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] 2.50.3 problems

 

On 14/07/2021 6:56 pm, Dave Miller via groups.io wrote:

you are right. JTAlertV2.Manager.exe is constantly running and dropping out. I checked Kaspersky and it is set to a trusted app. Not sure what else to do but will see if there are any Windows security settings blocking it.

Dave G6AWF


JTAlertV2.Manager stopping and starting every couple of seconds indicates that the Manager process is faulting and shutting down and the main controlling JTAlert process is starting it up as it was detected not running. JTAlert has always done this and it checks for the presence of the Manger every 2 seconds.

I can make this type of fault happen at will by simply running JTAlert against in incorrect NET runtime, either the wrong bit version or having the NET Runtime installed rather than the required NET Desktop Runtime.

Open up Windows event viewer and see if there are errors recorded there under "Windows Logs -> Application". This is from my machine when I try and run 32bit JTAlert install with the 64bit NET Desktop runtime installed.

   

Let me know what you find.

de Laurie VK3AMA


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: New JTalert 2.50.3 missing callsign window

kb2m@arrl.net
 

In my last post on this subject I should of gone into more detail. Like most people who had issues, when I went to 64 bit ver .3� from 64 bit ver .2 I had no Callsign window. I tried to un� install and re install .3. I also re installed� NET 5.0.7. Still no Callsign Window. I then went back to .2 and I then had a� Callsign window.� I ran for several hours without issue. I then read Laurie's post on NET 5.0.8. I� decided to give it another try. I uninstalled .2, reinstalled .3 along with NET 5.0.8 and all is now working, I have a Callsign window.

So installing the newly released NET 5.0.8 resolved my Callsign window issue. This tells me something was wrong with NET 5.0.7?

73 Jeff kb2m


On 7/14/2021 5:19 AM, HamApps Support (VK3AMA) wrote:
On 14/07/2021 3:30 am, Greg, KM5GT wrote:
To complete the picture, this is what I am seeing.� The "stars" below the program header is my background.



73, Greg, KM5GT

If your expecting to see the Callsigns displayed under the menu bar of that window, you're out of luck. The callsigns display grid embedded in the main JTAlert window was removed starting with JTAlert 2.50.0. The callsigns are now displayed in their own dedicated window. Use the view menu to open the Callsigns window.

BTW, you image shows JTAlert displaying the Band & Mode in the titlebar, that indicates that comms with WSJT-X is working. You don't appear to have the same problem as others have been experiencing.

de Laurie VK3AMA


locked Equipment on JT alert

Tom Hone AA0GP
 

Here is equipment I’m using which was purchased about 3 months ago from Dell. All latest versions are running great here.

 

Dell Inspiron 7506 2n1

Processor  11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz   2.80 GHz

Installed RAM 16.0 GB (15.7 GB usable)

Device ID   BF4DA986-679F-4603-8405-204F100EBA72

Product ID 00325-82104-93042-AAOEM

System type    64-bit operating system, x64-based processor

Pen and touch Pen and touch support with 10 touch points

 

Edition Windows 10 Home

Version      21H1

Installed on     ‎05/‎13/‎2021

OS build     19043.1110

Experience       Windows Feature Experience Pack 120.2212.3530.0

 

 

AA0GP

Tom Hone

www.cowboytom.com

 


--
Tom Hone
AA0GP
tom@...


locked Re: 2.50.3 problems

CSM&#92;(r&#92;) Gary Huber - AB9M
 

This is exactly what I am seeing on my computer; ASUS B450F motherboard, AMD Ryzen 5 2600, 16 GB RAM, AMD R500/550 Graphics card, WIN 10 Pro -64 bit with the latest updates and Kaspersky Total security. I am in the process of resetting and reloading this computer because I was also seeing "Windows 10 Black Screen Of Death", which makes me think there was some file corruption in the graphics library.

It would be interesting to know what hardware/OS/software is working versus what is not.

73,
Gary ~ AB9M


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Wednesday, July 14, 2021 4:09 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] 2.50.3 problems
 
On 14/07/2021 6:56 pm, Dave Miller via groups.io wrote:
you are right. JTAlertV2.Manager.exe is constantly running and dropping out. I checked Kaspersky and it is set to a trusted app. Not sure what else to do but will see if there are any Windows security settings blocking it.

Dave G6AWF

JTAlertV2.Manager stopping and starting every couple of seconds indicates that the Manager process is faulting and shutting down and the main controlling JTAlert process is starting it up as it was detected not running. JTAlert has always done this and it checks for the presence of the Manger every 2 seconds.

I can make this type of fault happen at will by simply running JTAlert against in incorrect NET runtime, either the wrong bit version or having the NET Runtime installed rather than the required NET Desktop Runtime.

Open up Windows event viewer and see if there are errors recorded there under "Windows Logs -> Application". This is from my machine when I try and run 32bit JTAlert install with the 64bit NET Desktop runtime installed.

   

Let me know what you find.

de Laurie VK3AMA


locked Re: 2.50.3

ka5bjc@...
 

Me three.


locked New versions

Tom Hone AA0GP
 

Run time 5.08 along with JTalert version 3 is working great here.

AA0GP
Tom Hone
www.cowboytom.com



--
Tom Hone
AA0GP
tom@cowboytom.com


locked Re: CQ Color still unable to change

Dave Garber
 

black text on lime green i think is coming from wsjt not jtalert.   check color options in wsjt

Dave Garber
VE3WEJ / VE3IE


On Tue, Jul 13, 2021 at 10:49 AM Todd (N3PKJ) <n3pkj@...> wrote:
Now I'm not talking about the new directed CQ. The old CQ color will not change it's stays the lime green with black text no matter what I do. I want white text on dark green. It acts like saves the changes by changing the colors on both Text & Background then click save then click OK. Let JTAlert do its thing. Reopen settings go back to CQ it goes back to the black text & lime green background. The 3 versions have done this and this recreated on my 2 PCs my laptop & desktop.

73
Todd N3PKJ


locked Re: Problems with JTAlert latest install

JTAlert Support (VK3AMA)
 

On 14/07/2021 11:45 am, Jim Wysocki wrote:

udio and Visual Alerts ran on a consistent cycle, at about 3 seconds on and 3 seconds off, repeatedly.

Maybe this is typical behavior or not; I can't tell but you'll know the answer.

73,  Jim  W9FI


No, not normal behavior. That indicates that the Manager is faulting and JTAlert is restarting it. 3 seconds sounds about right as the process is not faulting immediately and JTAlert will likely not see that it has gone AWOL as it only polls every 2 seconds.

Both JTAlert.exe and JTAlertV2.Manager.exe should run continuously.

See my other response here.

de Laurie VK3AMA


locked Re: Problems with JTAlert latest install

JTAlert Support (VK3AMA)
 

On 14/07/2021 10:55 am, Jim Wysocki wrote:

I've seen "Decodes" but not "Call Signs".  Hopefully that situation will change soon.

I was running version 2.16.14 before the 2.50.3 install.

I hope these clues help in the problem solving process.

73,  Jim  W9FI


The Decodes window, which BTW is currently being rewritten, uses the old .NET Framework runtime technology. The Callsigns window, which is part of the JTAlertV2.Manager uses the newer .NET (formally .NET Core) Desktop Runtime.

My guess is that the Manager process is faulting which will cause most of the JTAlert functionality to cease working, including opening any of the "yellow stared" windows under the View menu.

Please check the Windows Event Viewer and see if there are any errors recorded there.
eg. this is from my test PC where I have deliberately installed the wrong NET Desktop Runtime causing the Manager process to fault.

   

Let me know what you find.

de Laurie VK3AMA


locked Re: New JTalert 2.50.3 missing callsign window

JTAlert Support (VK3AMA)
 

On 14/07/2021 3:30 am, Greg, KM5GT wrote:
To complete the picture, this is what I am seeing.  The "stars" below the program header is my background.



73, Greg, KM5GT

If your expecting to see the Callsigns displayed under the menu bar of that window, you're out of luck. The callsigns display grid embedded in the main JTAlert window was removed starting with JTAlert 2.50.0. The callsigns are now displayed in their own dedicated window. Use the view menu to open the Callsigns window.

BTW, you image shows JTAlert displaying the Band & Mode in the titlebar, that indicates that comms with WSJT-X is working. You don't appear to have the same problem as others have been experiencing.

de Laurie VK3AMA


locked Re: CQ Color still unable to change

JTAlert Support (VK3AMA)
 

On 14/07/2021 12:49 am, Todd (N3PKJ) wrote:
Now I'm not talking about the new directed CQ. The old CQ color will not change it's stays the lime green with black text no matter what I do. I want white text on dark green. It acts like saves the changes by changing the colors on both Text & Background then click save then click OK. Let JTAlert do its thing. Reopen settings go back to CQ it goes back to the black text & lime green background. The 3 versions have done this and this recreated on my 2 PCs my laptop & desktop.

73
Todd N3PKJ

If settings changes are not being remembered after making a change than likely you have a corrupt config file. See the Help -> Troubleshooting" menu. When the help file opens look to the third entry titled "Setting Changes Not Remembered".

de Laurie VK3AMA


locked Re: 2.50.3 problems

JTAlert Support (VK3AMA)
 

On 14/07/2021 6:56 pm, Dave Miller via groups.io wrote:
you are right. JTAlertV2.Manager.exe is constantly running and dropping out. I checked Kaspersky and it is set to a trusted app. Not sure what else to do but will see if there are any Windows security settings blocking it.

Dave G6AWF

JTAlertV2.Manager stopping and starting every couple of seconds indicates that the Manager process is faulting and shutting down and the main controlling JTAlert process is starting it up as it was detected not running. JTAlert has always done this and it checks for the presence of the Manger every 2 seconds.

I can make this type of fault happen at will by simply running JTAlert against in incorrect NET runtime, either the wrong bit version or having the NET Runtime installed rather than the required NET Desktop Runtime.

Open up Windows event viewer and see if there are errors recorded there under "Windows Logs -> Application". This is from my machine when I try and run 32bit JTAlert install with the 64bit NET Desktop runtime installed.

   

Let me know what you find.

de Laurie VK3AMA


locked Re: 2.50.3 problems

Dave Miller
 

Thanks Bill, you are right. JTAlertV2.Manager.exe is constantly running and dropping out. I checked Kaspersky and it is set to a trusted app. Not sure what else to do but will see if there are any Windows security settings blocking it.

Dave G6AWF


locked Re: .NET v 5.0.8 x64

Jacques F1VEV
 
Edited

Likewise 5.0.8 64 Bit no issues Thanks F1VEV


locked Re: JTDX issues with latest JTAlert release. #JTDX

Alan Sorum WL7CG
 

I backed off to 2.50.2 and it's working fine.

73 Alan WL7CG


locked Re: New JTalert 2.50.3 missing callsign window

Robie - AJ4F
 

I installed today's windows update as well as the NET5 Desktop Runtime 5.0.8 X64 and still am not able to open the Callsigns Window.  Task Manager shows that  JTAlertV2.manager.exe is not running on my system.    I have set up an exclusion in windows defender for the HAMAPS folder.  This change did not result in the callsigns window becoming visible nor JTAlertV2.manager.exe running.

I'll provide any additional information requested to assist in resolving this issue.

Robie - AJ4F



On Tue, Jul 13, 2021 at 2:55 PM Dan K2IE via groups.io <dan=islenet.com@groups.io> wrote:
Same here...20.50.3 64 bit installed today and I no longer have the callsign window.


locked Re: 2.50.3 problems

Andy k3wyc
 

I finally got back to a what appears to be a usable and stable configuration by using a restore point prior to 2.50.0 installation and re-installing Net framework 5.0.5.  2.50.5 would not run with Net framework 5.0.7 and 2.50.0 was unstable with it.  Just installing 5.0.5 over 5.0.7 didn't fix the problem.  Had to go back to a restore point before the computer ever saw 5.0.7.

Andy, k3wyc


locked Re: Problems with JTAlert latest install

Jim Wysocki
 

Laurie, here's one more item that was buried in my notes to myself.  Task Manager saw that HamApps "Decoder" was running consistently, but that HamApps "Audio and Visual Alerts for WSJT-X (32 bit)" was appearing and disappearing from the its list of active apps.  Audio and Visual Alerts ran on a consistent cycle, at about 3 seconds on and 3 seconds off, repeatedly.

Maybe this is typical behavior or not; I can't tell but you'll know the answer.

73,  Jim  W9FI

On 7/13/2021 6:18 PM, Jim Wysocki wrote:

I'll hold off on making this change and instead see how version 2.50.2 behaves.

Jim  W9FI

On 7/13/2021 4:49 PM, HamApps Support (VK3AMA) wrote:
On 14/07/2021 9:34 am, Joe Subich, W4TV wrote:
If you are using multicast ("WSJTX UDP Multicast on Loopback" checked),
you need to use a Multicast address in WSJTX -> Settings -> Reporting ->
Network Services.  See: Help -> WSJT-X UDP Setup in JTAlert.

Joe,

That is not the case. The "multicast on loopback" setting can be left enabled when running unicast WSJT-X.
JTAlert ignores the setting if WSJT-X is detected not running multicast.

de Laurie VK3AMA



locked Re: Problems with JTAlert latest install

Jim Wysocki
 

I'll hold off on making this change and instead see how version 2.50.2 behaves.

Jim  W9FI

On 7/13/2021 4:49 PM, HamApps Support (VK3AMA) wrote:
On 14/07/2021 9:34 am, Joe Subich, W4TV wrote:
If you are using multicast ("WSJTX UDP Multicast on Loopback" checked),
you need to use a Multicast address in WSJTX -> Settings -> Reporting ->
Network Services.  See: Help -> WSJT-X UDP Setup in JTAlert.

Joe,

That is not the case. The "multicast on loopback" setting can be left enabled when running unicast WSJT-X.
JTAlert ignores the setting if WSJT-X is detected not running multicast.

de Laurie VK3AMA



locked Re: Problems with JTAlert latest install

Jim Wysocki
 

Thanks for your reply, Joe, and hello again on a different forum.

I tried changing the UDP address to 224.0.0.1 without success, but that was before I turned off Windows Defender and got it out of the way.  I'll change the UDP address accordingly and report back tomorrow on the results.  The reconfiguration will have to wait until the morning because the local weather won't cooperate with the testing process.  It's  going to be an active night of continuing rain, lightning and thunder.  The station has been disconnected until the WX clears up early tomorrow morning.

73,  Jim  W9FI

On 7/13/2021 4:34 PM, Joe Subich, W4TV wrote:

> WSHJT's UDP server address is 127.0.0.1. Its UDP server port is 2237.
> Its secondary server is disabled.  The "Accept UDP addresses", "Notify
> on accepted UPD Request", and "Accept UDP Request Restores Window"
> options are all checked.
>
On JTAlert, the Select menu's "WSJT-X  UDP Multicast on Loopback"
option is checked.  In its Settings/Applications/WSJT-X / JTDX"
section, all of the options are selected except for "Resend WSJT-X
UDP Packets..."

If you are using multicast ("WSJTX UDP Multicast on Loopback" checked),
you need to use a Multicast address in WSJTX -> Settings -> Reporting ->
Network Services.  See: Help -> WSJT-X UDP Setup in JTAlert.

Multicast address ranges are: 224.0.0.1 to 224.0.0.255  and
239.255.0.1 to 239.255.255.255.  The recommended address is
224.0.0.1

73,

   ... Joe, W4TV


On 2021-07-13 6:27 PM, Jim Wysocki wrote:
I've been using JTAlert with WSJT-X for several years without any problems at all, until last night when I updated to version 2.50.3, 64 bit.  Several problems now have appeared.

There is a general sluggishness to JTAlert's main window.  In contrast to all of the others on the desktop, when this one is grabbed and moved around, there is a 1 or 2 second delay in its response.  The same is true of when it has focus and the mouse is scanned across the tabs from Alerts to Help.

The call signs windows that was immediately below the main window in the old version has disappeared, and pressing F3 will not make it show up. The Decodes window can be made to appear by clicking on its option off of the View tab, but it has problems.  The decoded transactions that come to it from WSJT-X appear late and at intermittent times.  Every once in a while it will partially synch with WSJT-X, generally showing up to four of the latest callsigns that WSJT just decoded.  Occasionally JTAlert will grab more of them.  Most of the time it runs between one and six time slices behind WSJT.  Then it will grab about four of the latest transactions before locking up again. It cannot respond in real time with the data feed from WSJT-X.

Here is some background information for the problem analysis.

I am running a fully-updated Windows 10 Professional (64-bit) machine, an i5 with four processors at around a 3.3 gig speed and 16 gb of memory.  Task manager shows no memory or processor bottlenecks.  Windows desktop Dotnet runtime version 5.0.7 64 bit has been installed without any problems.  The JTAlert Framework Check displayed the "Good News" screen at the time that version 2.50.3 was installed.

Both WSJT-X and JTAlert have been whitelisted on PCMatic SuperShield. The Windows Defender firewall has been directed to allow the HamApps software apps to pass through it. Just to make sure I've also disabled Defender from running on the computer's private network.

WSHJT's UDP server address is 127.0.0.1. Its UDP server port is 2237. Its secondary server is disabled.  The "Accept UDP addresses", "Notify on accepted UPD Request", and "Accept UDP Request Restores Window" options are all checked.

On JTAlert, the Select menu's "WSJT-X  UDP Multicast on Loopback" option is checked.  In its Settings/Applications/WSJT-X / JTDX" section, all of the options are selected except for "Resend WSJT-X UDP Packets..." . The value in the greyed-out IP address is 127.0.0.1, and the greyed-out UDP port's value is 2233.  None of these six checked options appears to control information in the Decodes screen. As mentioned before, the Callsigns Window is no where to be seen.

Since this latest version was installed over the previous one, I used the Windows "Add or Remove Programs" utility to remove JTAlert, and then installed it again via

It appears to be that the transaction flow from WSJT and JTAlert is getting disrupted in some way, but I can't determine how this is happening.  I'm at a loss as to where to proceed from here so I need some advice.  What can be done next to diagnose and resolve this problem?

Thanks and 73,  Jim  W9FI









3801 - 3820 of 39820