Date   

locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

Phil Cooper
 

Hi all,

 

From my experience, if I call (for example) CQ NA, or CQ KL7, I get responses from anyone and everyone.

It all depends on your call, and your DX location.

 

Yes, it would be wonderful to call CQ YB and only get calls from YB stations, but in reality, it simply doesn't work that way.

 

Just my perspective!

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Craig" <NZ4CWcraig@...>
Sent: Saturday, 10 April, 2021 15:11
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Enhancement suggestion/discussion - JTAlert directional/directed CQ

Andy - this is not only for us, but benefits the caller, i.e., they would not be getting inadvertent calls from stations currently not seeing / not meeting the criteria.  I think this is a good idea!
Craig
NZ4CW

On Sat, Apr 10, 2021 at 9:31 AM Andy k3wyc <a.durbin@...> wrote:
It is quite common for stations to call CQ and only want replies from stations meeting some specified condition e.g. CQ NA, CD ND, CQ EU, CQ ASIA, etc.   These CQ calls can be highlighted by a red box (default) which I take to imply "Warning - don't click me".

What if that CQ was actually directed at stations for which I'm in the wanted group?  In my case I'd want to know if someone called CQ AZ, CQ NA, or CQ USA.   Perhaps the simplest way to implement this would be to have the user specify the exact match criteria e.g.

Show all CQ (border color)
Show CQ not directed at me (border color)
Show CQ direct at me (border color)
Directed CQ match criteria - USA, US, NA, AZ

Would anyone else find this, or something similar, useful?

73,
Andy, k3wyc


locked Re: Clicking on callsign fails to initiate wsjt-x

geoff wiggins
 

Yes

73 Geoff.

On 10/04/2021 17:17, Larry Banks via groups.io wrote:
Are you clicking on stations that are calling CQ?

73 -- Larry -- W1DYJ


-----Original Message----- From: geoff wiggins via groups.io
Sent: Saturday, April 10, 2021 12:11
To: Support@HamApps.groups.io
Subject: [HamApps] Clicking on callsign fails to initiate wsjt-x

Just started to use digi modes after a few weeks break and I find that
clicking on the callsign in the JTAlert window no longer initiates a qso.

Using 2.16.17 and wsjt-x 2.3.0

Any ideas why this should be? I checked the group msgs and noted that
there was a bug that caused this a few years ago but it's not that.

73 Geoff.









locked Re: Clicking on callsign fails to initiate wsjt-x

Larry Banks
 

Are you clicking on stations that are calling CQ?

73 -- Larry -- W1DYJ

-----Original Message-----
From: geoff wiggins via groups.io
Sent: Saturday, April 10, 2021 12:11
To: Support@HamApps.groups.io
Subject: [HamApps] Clicking on callsign fails to initiate wsjt-x

Just started to use digi modes after a few weeks break and I find that
clicking on the callsign in the JTAlert window no longer initiates a qso.

Using 2.16.17 and wsjt-x 2.3.0

Any ideas why this should be? I checked the group msgs and noted that
there was a bug that caused this a few years ago but it's not that.

73 Geoff.


locked Sta te/Country #FT8

 

I forgot how I set the decode window to show the state or country.
Thanks 73
--
DAVE NU4N


locked Clicking on callsign fails to initiate wsjt-x

geoff wiggins
 

Just started to use digi modes after a few weeks break and I find that clicking on the callsign in the JTAlert window no longer initiates a qso.

Using 2.16.17 and wsjt-x 2.3.0

Any ideas why this should be? I checked the group msgs and noted that there was a bug that caused this a few years ago but it's not that.

73 Geoff.


locked Re: Important Announcement : The next release of JTAlert requires the .NET 5 desktop runtime

Antony
 
Edited

Followed your instructions Laurie and now have 5.0.5 loaded (with no problems) ready for your next offering. Many thanks, de G4CUS


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

Craig
 

Andy - this is not only for us, but benefits the caller, i.e., they would not be getting inadvertent calls from stations currently not seeing / not meeting the criteria.  I think this is a good idea!

Craig
NZ4CW

On Sat, Apr 10, 2021 at 9:31 AM Andy k3wyc <a.durbin@...> wrote:
It is quite common for stations to call CQ and only want replies from stations meeting some specified condition e.g. CQ NA, CD ND, CQ EU, CQ ASIA, etc.   These CQ calls can be highlighted by a red box (default) which I take to imply "Warning - don't click me".

What if that CQ was actually directed at stations for which I'm in the wanted group?  In my case I'd want to know if someone called CQ AZ, CQ NA, or CQ USA.   Perhaps the simplest way to implement this would be to have the user specify the exact match criteria e.g.

Show all CQ (border color)
Show CQ not directed at me (border color)
Show CQ direct at me (border color)
Directed CQ match criteria - USA, US, NA, AZ

Would anyone else find this, or something similar, useful?

73,
Andy, k3wyc


locked Enhancement suggestion/discussion - JTAlert directional/directed CQ

Andy k3wyc
 

It is quite common for stations to call CQ and only want replies from stations meeting some specified condition e.g. CQ NA, CD ND, CQ EU, CQ ASIA, etc.   These CQ calls can be highlighted by a red box (default) which I take to imply "Warning - don't click me".

What if that CQ was actually directed at stations for which I'm in the wanted group?  In my case I'd want to know if someone called CQ AZ, CQ NA, or CQ USA.   Perhaps the simplest way to implement this would be to have the user specify the exact match criteria e.g.

Show all CQ (border color)
Show CQ not directed at me (border color)
Show CQ direct at me (border color)
Directed CQ match criteria - USA, US, NA, AZ

Would anyone else find this, or something similar, useful?

73,
Andy, k3wyc


locked Re: JT Alert not showing any FT8 Stations in the 3 boxes at all. I need to have 3 software programs & radio IC7300 all on on 3 how?

Glyn
 

Hi Geoff
Thanks for reply yes it is set for OMNI 1
this is the fault report


locked Re: OK what happened to .net 4.7.2

neil_zampella
 

Frankly, I would not worry about it for now, you're going to need the .NET 5.x for the future versions.  

 

Neil, KN3ILZ


locked Re: Small Dot

Michael Black
 

Inline image

Mike W9MDB




On Saturday, April 10, 2021, 07:05:58 AM CDT, Jonathan <wd6bny@...> wrote:


What did you find out about the two triangles in opposite corners? I've been searching off and on in the docs & web for a year! I learned of the small square and underline on this forum.
Jonathan WD6BNY


locked Re: Small Dot

Larry Banks
 

Hi Jonathan,
 
From the release notes:
Callsign QSL Indicators: Striped QSL indicators have been removed.
       Only flag style indicators are used. The position of the indicators is
       now fixed, Lotw in the top-left corner and Eqsl in the bottom-right corner
       of the Callsign display. This change is for both the main JTAlert window
       and the Decodes window.

73 -- Larry -- W1DYJ

 

From: Jonathan
Sent: Saturday, April 10, 2021 8:05
Subject: Re: [HamApps] Small Dot
 
What did you find out about the two triangles in opposite corners? I've been searching off and on in the docs & web for a year! I learned of the small square and underline on this forum.
Jonathan WD6BNY


locked Re: Small Dot

Jonathan
 

What did you find out about the two triangles in opposite corners? I've been searching off and on in the docs & web for a year! I learned of the small square and underline on this forum.
Jonathan WD6BNY


locked Keywords Alert does not function #FT8

asobel@...
 

Laurie

I am trying to get JTAlert respond to "CQ TEST X1Xx" produced by WSJT-X FT8 contest modes. I did tick Enable Keywords Alert, inserted keywords CQ, CQ TEST, TEST and DX. Gave it blue color and Testing.wav and saved it. It does not respond for CQ which is not rare and very rarely gives  any responce. It did respond to HL2ZN, RD4HR, CQ MI0OBC and PY2XC. PY2XC was displayed in blue on the WSJT-X board and DX was displayed in blue on the JTAlert board.

What's wrong here? How do I get it working?
This is quite urgent. I need it for a contest next Saturday

Amos 4X4MF


locked Re: OK what happened to .net 4.7.2

HamApps Support (VK3AMA)
 

On 10/04/2021 9:54 am, Jim wrote:
 .NET  4.7.2 is required for Ham Apps to run correctly 

Jim K3ybn

FYI,

The only component of JTAlert, starting with the pending new 2.50.0 release, that requires 4.7.2 is the Decodes window. All other 4.7.2 specific code has been migrated to .NET 5 upon which JTAlert 2.50.0 is dependent.

As a result of this change, the JTAlert installer for 2.50.0 does not check that 4.7.2 is installed.

If you cant get .NET 4.7.2 installed, I suggest waiting a couple of days for the JTAlert 2.50.0 release. While that won't fix your 4.7.2 problem, it will not warn of the missing framework. Naturally the Decodes will not function correctly.

de Laurie VK3AMA



locked Re: OK what happened to .net 4.7.2

HamApps Support (VK3AMA)
 

On 10/04/2021 9:38 am, Jim wrote:
Laurie,
Ok thanks for info .... somehow I thought it had been.  In any event when I try to install the specified .net off the Microsoft web site I get an error and no where can I find out how to fix it.. thats why I had asked the original question. 

The error I get is found in my log entry below:

Package Name = Microsoft .NET Framework 4.7.2 Setup
Package Version = 4.7.03081
User Experience Data Collection Policy: AlwaysUploaded
 
 
 
Number of applicable items: 10
 
 
 
Final Result: Installation failed with error code: (0x800B0109), "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. " (Elapsed time: 0 00:00:32).
C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi - Signature verification for file netfx_Full_x64.msi (C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi) failed with error 0x800b0109 (A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)
 
No FileHash provided. Cannot perform FileHash verification for netfx_Full_x64.msi
File netfx_Full_x64.msi (C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi), failed authentication. (Error = -2146762487). It is recommended that you delete this file and retry setup again.
Exe (C:\2ab92d49205972a6ad5f1c\SetupUtility.exe) succeeded.
Exe Log File: dd_SetupUtility.txt
ServiceControl operation succeeded!
ServiceControl operation succeeded!
Exe (C:\2ab92d49205972a6ad5f1c\SetupUtility.exe) succeeded.
Exe Log File: dd_SetupUtility.txt
Final Result: Installation failed with error code: (0x800B0109), "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. " (Elapsed time: 0 00:00:32).

So I have an issue with a certificate that is not trusted. Have you ever seen this before or know someone that has had this problem and resolved it?

Jim K3YBN

A quick Google search indicates this is a common wide-spread problem. Interesting that most of the results are quite old, several years.

It appears, based on my quick perusal of the Google results. that your Win7 has not been getting updated with security patches.

I am loath to suggest a solution for something I have not encountered or tested.

Try installing NET Framework 4.8

If that doesn't work try applying the
KB2813430 update. It cropped up several times as a solution. Download from here...
https://www.catalog.update.microsoft.com/Search.aspx?q=kb2813430

I note that that security update was released in 2013.

Several possible solutions involved file deletions/modifications or Registry hacks. I will not publish those, I leave that to you to try if the official Microsoft patch fails.

That's the limit of the support I can provide on this.

de Laurie VK3AMA


locked Re: OK what happened to .net 4.7.2

Jim
 

Willie, this version also gives error with certificate.. see below in my reply to Laurie for the full error message from the attempted installation.. 

Jim K3YBN

OH and in case I forget again.. thanks to all you guys for the help.  This type of microsoft message drives me nuts


locked Re: OK what happened to .net 4.7.2

Jim
 

Neil, 
 .NET  4.7.2 is required for Ham Apps to run correctly 

Jim K3ybn


locked Re: OK what happened to .net 4.7.2

Jim
 

Laurie,
Ok thanks for info .... somehow I thought it had been.  In any event when I try to install the specified .net off the Microsoft web site I get an error and no where can I find out how to fix it.. thats why I had asked the original question. 

The error I get is found in my log entry below:

Package Name = Microsoft .NET Framework 4.7.2 Setup
Package Version = 4.7.03081
User Experience Data Collection Policy: AlwaysUploaded
 
 
 
Number of applicable items: 10
 
 
 
Final Result: Installation failed with error code: (0x800B0109), "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. " (Elapsed time: 0 00:00:32).
C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi - Signature verification for file netfx_Full_x64.msi (C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi) failed with error 0x800b0109 (A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)
 
No FileHash provided. Cannot perform FileHash verification for netfx_Full_x64.msi
File netfx_Full_x64.msi (C:\2ab92d49205972a6ad5f1c\netfx_Full_x64.msi), failed authentication. (Error = -2146762487). It is recommended that you delete this file and retry setup again.
Exe (C:\2ab92d49205972a6ad5f1c\SetupUtility.exe) succeeded.
Exe Log File: dd_SetupUtility.txt
ServiceControl operation succeeded!
ServiceControl operation succeeded!
Exe (C:\2ab92d49205972a6ad5f1c\SetupUtility.exe) succeeded.
Exe Log File: dd_SetupUtility.txt
Final Result: Installation failed with error code: (0x800B0109), "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. " (Elapsed time: 0 00:00:32).

So I have an issue with a certificate that is not trusted. Have you ever seen this before or know someone that has had this problem and resolved it?

Jim K3YBN


locked Re: Unable to move the "decodes" window

Robert Rosenfelder
 

Hi Laurie

Yes, the problem still exists.  The decodes box is about 4 inches wide and 6 inches high and is centered on top of the JTDX screen.

Tried rebooting PC as well... everything is working...the fields are populating the decodes screen.

I had a decode window issue in the past... and you sent me the email below.. In that case, deleting the decodes history file resolved the issue.

If the normal techniques for recovering off-screen windows (eg. https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/) don't work,
try shutting down JTAlert and the Decodes window and delete the "Decodes History V3.config" file at %localappdata%\HamApps\JTAlert\WE8R\Config\

de Laurie VK3AMA


73, Bob / WE8R

3241 - 3260 of 36910