Date   

locked Re: JT Alert quit working after Windows 10 Update

Michael Black
 

When you installed did you see the dialog box that says if found the .Net installation?

Mike W9MDB




On Saturday, October 16, 2021, 05:39:52 PM CDT, Tommy Evans <tommysevans@...> wrote:


Program loads but is not communicating with WSJT.  All the settings look correct.  Has anyone else had this issue ?


locked JT Alert quit working after Windows 10 Update

Tommy Evans
 

Program loads but is not communicating with WSJT.  All the settings look correct.  Has anyone else had this issue ?


locked Re: JT Alert display #HamSpots

Michael Black
 

Try View/Callsign History Window

What version were you running before .7?  The call signs moved to a new window.

Mike W9MDB






On Saturday, October 16, 2021, 04:53:43 PM CDT, Neil Foster <archernf@...> wrote:


For some odd reason when I updated to the latest version all I get is the top bar showing Alerts Settings etc??
I went back to .6 and the same. What am I missing or not doing to get the additional panes showing?
Many thanks for any clue.   Neil   N4FN


locked JT Alert display #HamSpots

Neil Foster
 

For some odd reason when I updated to the latest version all I get is the top bar showing Alerts Settings etc??
I went back to .6 and the same. What am I missing or not doing to get the additional panes showing?
Many thanks for any clue.   Neil   N4FN


locked Which version of JT Alert works now with my HRD v6.7.0.391 Release

Vince Loschiavo
 

Hi Laurie,
I've been using the following as I remember that some links broke to push contacts to HRD Logbook
here is what I'm using.
HRD 6.7.0.391
Windows 10Pro OS Version 21H1
OS build 19043.1288
with Windows Feature Experience Pack 120.2212.3920.0
WSJT-X v2.4.0 c19d62
Please find the 'about' info below.
JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line   : C:\WSJT\wsjtx\bin\wsjtx.exe 
WSJT-X   --rig-name   : 
WSJT-X Config File    : C:\Users\Ham Shack\AppData\Local\WSJT-X\WSJT-X.ini
 
================================
UDP Ports used
--------------------------------
JTAlert.exe           : 57549
JTAlertV2.Manager.exe : 56966
JTAlertV2.Decodes.exe : 
 
 
================================
JTAlertV2.Manager status
(2021-10-16 19:44:35 utc)

Could you tell me which version to go to that will continue working with HRD, Win10, and WSJT-X ??

Thanks
Vince
N2AIE


locked #Announcement #NewRelease : JTAlert 2.50.7 is available #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.50.7 is now available at https://hamapps.com/JTAlert/

The new installers were examined by Microsoft and flagged as Virus/Trojan free. The MS Defender definitions files have been updated to exclude JTAlert 2.50.7 as a threat.

Full release notes are available at the end of this message. I strongly encourage all users to read these before installing this new JTAlert release.

de Laurie VK3AMA

Release Notes:

2.50.7 (2021-Oct-16)

  *** Includes Callsign database file version 2021-10-16 (2021-Oct-16)

  New:

    - Callsigns Window: Option to display the worked B4 date rather than the
       Country name. See the Options display (click the gear icon), "Callsigns"
       section, "B4 date replaces Country" checkbox.

  Changes:

    - Support: The automated file submission when using the "Help ->
       Contact Support" menu has been removed. It has been replaced with a
       help file topic which provides information on how to get support.

  Fixes:

    - Callsigns Window: Zoom level of the callsign display was scaling at a
       greater rate than all other visual elements of the window.

    - Menus: Menus not scaled when the zoom level changed. Affecting the Callsigns,
       Messaging, Activity and BandHeat windows. (2.50.0 design limitation)

    - Gear Icon: Not scaled per the zoom level value. (2.50.6 defect)


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Ronald Clanton
 

Laurie,

As mentioned, I'm using QRZ for logging and exporting the ADIF file and importing to JTAlert... then run a rebuild.  I'll check which alert HI/AK is triggered and how the import imported them to JTAlert.  I primarily (almost exclusively) work FT8 Digital... so am certain that I have matched band and mode.

When I get home, I check which alert is triggered and also check the JTAlert check boxes as filled by the rebuild.  I'll also make sure that the criteria are the same for alerting on each.

Thanks,

Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Ronald Clanton
 

Dave,

Thanks!  The contacts/goals for AK and HI were all digital and band specific.  You hit on something... I need to see why they're yellow... is it due to "state" or "country" alert.  I'll check when I get home on Sunday.  I import my log via ADIF from QRZ.com.  Perhaps the import isn't checking the right marks in the worked alerts.

On the B4 issue... perhaps this is the first time I noticed it happening, but what you say makes sense.  If they didn't confirm the first time, why alert when for country/state when they're on the next time?

Thanks,


Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Dave Garber
 

Like Joe says, check your reason the alert is not popping as b4.  you may have worked the state before, but new alert might be for a grid in alaska you have not worked ( maybe the op is remoting)

my b4 come up as grey ( my color choice) in wsjt, whether confirmed or not.



Dave Garber
VE3WEJ / VE3IE


On Thu, Oct 14, 2021 at 10:18 PM Ronald Clanton <ronaldnc55@...> wrote:

Dave,

Thanks for the reply!  I've confirmed the filename.  Interesting that the HI and AK issue has been there since I started using JTAlert over a year ago.  The B4 issue is brand new with this version... as far as I can tell.

I take it that you don't have any issue with HI and AK showing as needed in JTAlert when you have had confirmed contacts?

Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

HamApps Support (VK3AMA)
 

On 15/10/2021 1:18 pm, Ronald Clanton wrote:
I take it that you don't have any issue with HI and AK showing as needed in JTAlert when you have had confirmed contacts?

How have you set JTAlert for the Wanted State and Wanted Country Alerts with respect to Band & Mode tracking? If they are not set the same, than it is normal to see AK or HI stations generating a State Alert while not generating a Country Alert.

In my case I have Country alerting set for "by individual band" and "by any digital mode" but have the State alerting set for "by individual band" and "by individual mode". Example, in the case of a log confirmed entry for HI on 20m JT65, a HI station decoded on 20m FT8 will not generate a HI Country alert but will generate a HI State alert as I am tracking States by individual mode, but Countries by any digital mode and HI has already been confirmed on JT65.

de Laurie VK3AMA
 


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

HamApps Support (VK3AMA)
 

On 9/10/2021 1:45 am, Ronald Clanton wrote:

I continue to see AK and HI as a wanted DXCC/State in the decode box (marked by yellow) despite having many confirmed log entries.  Is there a setting that I'm missing?

Also, I thought in the past that a contact was only marked "B4" when confirmed?  I have a situation where it indicated it as B4, but isn't a confirmed contact.  Additionally, in the decode box, it doesn't flag it as a wanted DXCC (only grey)... even though that unconfirmed contact is the only one for that DXCC entry.

Thanks,

Ron


H'mm, I don't know what happened to my last reply. I distinctly remember composing the email, but It never got posted to the group.

Questions...
  • What log type are you using with JTAlert?

  • How are you maintaining your Wanted Entities, is it by manually applying changes or by running the automated "Rebuild Alert Database" operation? The rebuild operation is what you should be performing if running with a log enabled in JTAlert.
Keep in mind, that for AK & HI they have the distinction of being both a State and Country. Having say HI marked as no longer needed as a Country does not automatically mark HI as no longer needed as a State. If manually maintaining the needs lists you need to keep that in mind. Especially if your need requirements for States is different from you need requirements for Countries.

All Alerts types behave independently with respect to the needs tracking, by Band, Mode etc, so you could as example have Countries being tracked by Band only without regard to Mode, while at the same time have States tracked by both Band and Mode. The choice is yours and will impact how a State & Country is flagged as no longer needed. All of this is handled automatically by JTAlert when running the rebuild operation.

The State & Country alerts, by default have the same Yellow background coloring (yellow), with the text color being different to distinguish between the State & Country alerts. My guess is that your seeing a State Alert and misinterpreting as a Country Alert. You can tell which Alerts were triggered by examining the Callsign Tooltip of the alerted callsigns and observe which of the location details are highlighted.

An alternative to the Callsigns window and the Callsign tooltip to determine what alerts were triggered by a decode, you can use the Decodes window. It will display all the triggered Alert types for a Callsign within their own dedicated columns so you can quickly see what alerts were triggered.

de Laurie VK3AMA


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Joe Subich, W4TV
 

On 2021-10-14 10:18 PM, Ronald Clanton wrote:

I take it that you don't have any issue with HI and AK showing as needed in JTAlert when you have had confirmed contacts?
None at all. Are they color coded as wanted states or wanted countries?
What are your respective state/country goals - any/individual bands?
Any Mode, Individual mode, Any Digital Mode, Any WSTX Mode? Are your
goals the same for state/country?

Hover your mouse over the tile in the All Decodes display and see
what is highlighted in blue - that will tell you what is
triggering the "need".

Also, I thought in the past that a contact was only marked "B4" when confirmed?
No, B4 are marked as such when worked, not when confirmed.

Additionally, in the decode box, it doesn't flag it as a wanted DXCC (only grey)... even though that unconfirmed contact is the only one for that DXCC entry.
B4 will take precedence. "Reworking" a given station on the same band
does not "advance" one's progress. If you have given up on receiving
confirmation for the previous contact, mark it "invalid" in your logging
program and JTAlert will ignore the previous QSO.

73,

... Joe, W4TV


On 2021-10-14 10:18 PM, Ronald Clanton wrote:
Dave,
Thanks for the reply!  I've confirmed the filename.  Interesting that the HI and AK issue has been there since I started using JTAlert over a year ago.  The B4 issue is brand new with this version... as far as I can tell.
I take it that you don't have any issue with HI and AK showing as needed in JTAlert when you have had confirmed contacts?
Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Ronald Clanton
 

Dave,

Thanks for the reply!  I've confirmed the filename.  Interesting that the HI and AK issue has been there since I started using JTAlert over a year ago.  The B4 issue is brand new with this version... as far as I can tell.

I take it that you don't have any issue with HI and AK showing as needed in JTAlert when you have had confirmed contacts?

Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Dave Garber
 

if you doing a rescan of the log, confirm the filename is correct.    you may be scanning an old log, but updating a new one??


Dave Garber
VE3WEJ / VE3IE


On Thu, Oct 14, 2021 at 2:25 PM Ronald Clanton <ronaldnc55@...> wrote:

Okay... no replies.  Am I the only one experiencing this issue?

 

Ron
KE7NJ


locked Re: JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Ronald Clanton
 

Okay... no replies.  Am I the only one experiencing this issue?

 

Ron
KE7NJ


locked Re: New Install #TIP - CORRECTED #TIP

k9bo@...
 

Laurie, my bad as I spent over 3 hours trying to get the new version to run properly.  At age 78 three hours of wasted time are getting close to being a great loss.  I simply thought that following the “click here” buttons on the links you provided and downloaded what Microsoft gave me.  I do pretty well with the hardware end of things but I don’t have to get very far under the bonnet to get lost pretty quickly.  The main reason for my post was to warn others of what can be an issue. I agree with your comments relative to the Console vs. the Desktop version.  I was thinking that for the rest of my unwashed brethren out there some kind of caution or admonishment might be in order as one starts to follow the link over to Microsoft.  By the way in playing with the new version it truly was worth the three hours...

 

Thanks for listening to this old goat who is still into valves, tubes and high SWRs. 

 

73,

 

Bill, K9BO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Tuesday, October 12, 2021 3:28 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] New Install #TIP - CORRECTED

 

On 13/10/2021 5:02 am, k9bo via groups.io wrote:

Tried to install the latest version of JT-Alert and couldn't get it to recognize my fresh installation of .NET  After circling the drain for several hours I came to the conclusion that the problem is that if one goes to Microsoft to install it you get the newest version 5.0.11 not 5.0.0.  The 5.0.11 is not recognized by JT-Alert.  Solved the problem by going deeper on the Microsoft download site to old versions and got .NET 5.0.0 and all is now working.  Not sure how difficult it would be to fix this on JT-Alert, but in the meantime, perhaps a warning or tip on the JT-Alert  might be in order.  Love the new version, great job

Bill, K9BO  


Sorry Bill, you're incorrect. JTAlert works fine with the .NET 5.0.11 Desktop Runtime. There is no specific version required by JTAlert except that is 5.0.0 or later.

I have the 5.0.11 Desktop Runtime on all my PCs, JTAlert installed on the Ham dedicated PC and the JTAlert development PC both behave correctly with the latest .NET 5.0.11 Desktop Runtime.
 
 
Your issue with the new install of JTAlert not recognizing your .NET install would be due to installing the non-desktop version (the console version). You have to install the Desktop Runtime. JTAlert is a Desktop app, not a Console app, it requires the Desktop Runtime


5.0.11 is a security update so Windows will be automatically installing it for as part of its automated updates process.

de Laurie VK3AMA


locked Re: New Install #TIP - CORRECTED #TIP

HamApps Support (VK3AMA)
 

On 13/10/2021 5:02 am, k9bo via groups.io wrote:
Tried to install the latest version of JT-Alert and couldn't get it to recognize my fresh installation of .NET  After circling the drain for several hours I came to the conclusion that the problem is that if one goes to Microsoft to install it you get the newest version 5.0.11 not 5.0.0.  The 5.0.11 is not recognized by JT-Alert.  Solved the problem by going deeper on the Microsoft download site to old versions and got .NET 5.0.0 and all is now working.  Not sure how difficult it would be to fix this on JT-Alert, but in the meantime, perhaps a warning or tip on the JT-Alert  might be in order.  Love the new version, great job

Bill, K9BO  

Sorry Bill, you're incorrect. JTAlert works fine with the .NET 5.0.11 Desktop Runtime. There is no specific version required by JTAlert except that is 5.0.0 or later.

I have the 5.0.11 Desktop Runtime on all my PCs, JTAlert installed on the Ham dedicated PC and the JTAlert development PC both behave correctly with the latest .NET 5.0.11 Desktop Runtime.
 
 
Your issue with the new install of JTAlert not recognizing your .NET install would be due to installing the non-desktop version (the console version). You have to install the Desktop Runtime. JTAlert is a Desktop app, not a Console app, it requires the Desktop Runtime


5.0.11 is a security update so Windows will be automatically installing it for as part of its automated updates process.

de Laurie VK3AMA


locked Re: New Install #TIP

Joe Subich, W4TV
 

On 2021-10-12 2:02 PM, k9bo via groups.io wrote:
After circling the drain for several hours I came to the conclusion that the problem is that if one goes to Microsoft to install it you
get the newest version 5.0.11 not 5.0.0. The 5.0.11 is not recognized
by JT-Alert.
More likely you downloaded the wrong version of dotNET 5.0.11. The
Microsoft web site is confusing - you *MUST* download the dotNET
*DESKTOP* Runtime 5.0.11 and not dotNET Runtime 5.0.11.

From the Microsoft website:

The .NET Runtime contains just the components needed to run a
*console* app. Typically, you'd also install either the ASP.NET
Core Runtime or .NET Desktop Runtime.
Here is what Microsoft says about the *DESKTOP* Runtime:

The .NET Desktop Runtime enables you to run existing Windows desktop
applications. *THIS RELEASE INCLUDES THE .NET RUNTIME; YOU DON'T*
*NEED TO INSTALL IT SEPARATELY.*
In other words, dotNET (console) Runtime 5.0.11 lacks certain components
that JTAlert requires in order to operate.

I have downloaded and installed the dotNET *DESKTOP* Runtime 5.0.11 and
JTAlert works properly with the correct version of the Runtime.

73,

... Joe, W4TV


On 2021-10-12 2:02 PM, k9bo via groups.io wrote:
Tried to install the latest version of JT-Alert and couldn't get it to recognize my fresh installation of .NET  After circling the drain for several hours I came to the conclusion that the problem is that if one goes to Microsoft to install it you get the newest version 5.0.11 not 5.0.0.  The 5.0.11 is not recognized by JT-Alert.  Solved the problem by going deeper on the Microsoft download site to old versions and got .NET 5.0.0 and all is now working.  Not sure how difficult it would be to fix this on JT-Alert, but in the meantime, perhaps a warning or tip on the JT-Alert  might be in order.  Love the new version, great job
Bill, K9BO


locked Re: New Install #TIP

AB8WD-Willie
 

No problem here running .11 it saw it and moved on


locked New Install #TIP

k9bo@...
 

Tried to install the latest version of JT-Alert and couldn't get it to recognize my fresh installation of .NET  After circling the drain for several hours I came to the conclusion that the problem is that if one goes to Microsoft to install it you get the newest version 5.0.11 not 5.0.0.  The 5.0.11 is not recognized by JT-Alert.  Solved the problem by going deeper on the Microsoft download site to old versions and got .NET 5.0.0 and all is now working.  Not sure how difficult it would be to fix this on JT-Alert, but in the meantime, perhaps a warning or tip on the JT-Alert  might be in order.  Love the new version, great job

Bill, K9BO  

1301 - 1320 of 38444