Date   

locked Re: Problems with JTAlert latest install

rsagun
 

I had the same problems as Jim W9FI.  I did several restarts and was upgrading from 2.50.2.  No success.  Also I noticed that sound wasn't working either.

Thanks,

Ross W6RSS


locked Re: Decodes window: View->Clear Display has no effect

Paul
 

HI, I noticed the online message icon was not showing on Version 2.50.3.On checking all my setting all seemed fine.
Rolling back to 2.50.2 all is working fine.Thanks again for all your good hard work.
Sorry to add to your problems.
Paul G4YKQ.

On Wednesday, 14 July 2021, 17:02:35 BST, Ken B <kb7who@...> wrote:


I have had the same thing happen. If I clear all of the activity in WSJTX, then clear the screen in Decodes, it seems to work.
Ken


locked Re: Decodes window: View->Clear Display has no effect

Ken B
 

I have had the same thing happen. If I clear all of the activity in WSJTX, then clear the screen in Decodes, it seems to work.
Ken


locked Re: Callsign window #1 actions and display contradictions

Jim Cary
 

Laurie and Bill

These tips did the job.  Thanks ever so much.

Question - have you given any thought to the idea of enabling "TX Enable" on WSJT-X when clicking on a call in the call box that shows a "73"?  Just like it works on a "CQ".  I think that would be a  nice enhancement if technically feasible.

73 and tnx for all the good work.

Jim


locked Re: 2.50.3 problems

Phil Cooper
 

Hi all,

Rather than what hardware/OS works, or doesn't, it may be more pertinent to see where JTAlert and WSJTx are installed.

My WSJTx is installed at C:\WSJT\wsjtx\bin\wsjtx.exe
And JTAlert is installed at C:\HamApps\JTAlert2.5\JTAlert\

It may well be that some programs installed into the Program Files folder are causing issues due to OneDrive saving copies.
This was exactly what my problem was with N1MM+, and meant I had to relocate it to a directory outside the Program Files area.

So, who has one or both installed in the Program files directory?

73 de Phil GU0SUP


locked Re: New JTalert 2.50.3 missing callsign window

Michael Black
 

Just did this with another user and it didn't solve the missing callsign window.
#1 Uninstalled 5.0.8
#2 Reboot
#3 Install 5.0.8
#4 Install 2.50.3
No joy.

We renamed his HamApps directory to start a new config and everything is working now.

So there's a corruption in the config.

Laurie -- do you want this information?

Mike W9MDB




On Wednesday, July 14, 2021, 08:44:16 AM CDT, kb2m@... <kb2mjeff@...> wrote:


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 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\(r\) 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

HamApps 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

HamApps 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

HamApps 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

HamApps 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

HamApps 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

2501 - 2520 of 38526