Date   

locked Re: : Todays Windows update and broken JTAlert audio - THE FIX

Dave Garber
 

turn off auto updates in windows, i think
Dave Garber
VE3WEJ / VE3IE


On Tue, Jun 15, 2021 at 6:36 PM richard clare <crrr@...> wrote:
my issue is that microsoft keeps reinstalling 5.0.7 every day after I have removed and installed 5.0.6. Is there a solution for this? 
Thanks, Richard wb6ewm
 


locked Re: : Todays Windows update and broken JTAlert audio - THE FIX

KD7YZ Bob
 

Hello richard,
Tuesday, June 15, 2021, 6:36:02 PM, you wrote:
----------------------------------------------------
my issue is that microsoft keeps reinstalling 5.0.7 every day after
I have removed and installed 5.0.6. Is there a solution for this?
----------------------------------------------------
Unfortunately I can't remember the steps I took with Group Policy Editor ....followed a wiser person's steps I found ... and now in order to get ANY update, I personally have to authorize it to be downloaded THEN I have to authorize my PC to install it
Note, there is NO 7-day then they do it. Updates simply do not happen unless I say so.

But I can't remember which Forum in the Ham Radio World where I got the instruction.



--
Best regards,
Bob KD7YZ


locked Re: : Todays Windows update and broken JTAlert audio - THE FIX

richard clare
 

my issue is that microsoft keeps reinstalling 5.0.7 every day after I have removed and installed 5.0.6. Is there a solution for this? 
Thanks, Richard wb6ewm
 


locked Re: Callsign window in v2.50.0 #FT8

HamApps Support (VK3AMA)
 

On 15/06/2021 3:57 pm, Chris Levingston wrote:
I am using WSJT-X v2.4.0 and JTAlert v2.16.4.

I recently upgraded to JTAlert v2.50.0 but I can't see the Callsigns window, which is really frustrating.

Clicking on the View menu brings up the View menu but then but clicking on the stars for F3, F5, F11 and F12 does not work, nor does pressing the function keys.
The others work.  
I have gone back to 2.16.4 until I can find a fix.

This has gone back a page so Laurie may not have seen it after suggesting a fix that I had already done (and we had a long weekend since I posted), so I have re-posted.

73s,

Chris    VK5SA

Why did you rollback so far to 2.16.4? You only needed to go back to 2.16.17 to avoid the current issues with the new .NET 5.0.7 runtime security patch.

Al the windows you listed as non-opening are handled by the JTAlertV2.Manager.exe process. If it is not running you will not be able to see those windows. The Manager process for JTAlert 2.50.x is closing due to memory violation errors as a result of the recent .NET 5.0.7 runtime security patch. The fix is to uninstall 5.0.7 and reinstall 5.0.6 of the runtime.

de Laurie VK3AMA


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 16/06/2021 6:15 am, William Osborne wrote:
So for old brain like mine, there is currently no way to see only DX spot, i.e, not USA spots?

Thanks for great program,
Bill---K5ZQ

There is, but you will need to wait until the next public release.

The next release has as options a "Local Decodes" display and a "DX Decodes" display. The "DX Decodes" which will restrict the callsigns displayed to those originating from Countries other than your own. The Callsigns window will allow you to view both these filtered views concurrently in separate display panels on the Callsigns window. ;-)

The next release is imminent, I have delayed it while I monitor the Microsoft developer activity regarding the current NET 5.0.7 runtime defect that breaks the sound output. I am hoping they release a fix within the next couple of days so I don't have to release the new JTAlert which has workaround for the defect but it means JTAlert will be restricted to playing audio on the default Windows device only rather than a user-settable device.

de Laurie VK3AMA


locked Re: Filters - A feature request

William Osborne
 

So for old brain like mine, there is currently no way to see only DX spot, i.e, not USA spots?

Thanks for great program,
Bill---K5ZQ


locked Re: WSJT talks to N3FJP directly

Dave Garber
 

i would try using multicast, and tell jtalert no log, but as stated, what is it going to alert you of, if you have no log

Dave Garber
VE3WEJ / VE3IE


On Mon, Jun 14, 2021 at 12:25 PM Dave NT9E <nt9e@...> wrote:
The same way WSJT sends data to N3FJP for logging. JTAlert only has to listen to WSJT data while sending it to N3FJP. I'm sure it's possible but only a programmer would know how.


locked Re: New install

Dave Garber
 

is the waterfall in wsjt showing signals?  is you clock time set right?  and  are you selecting the right sound input, and do you not have dotnet 5.0.7 installed 

any one of these or all can cause no decodes

Dave Garber
VE3WEJ / VE3IE


On Mon, Jun 14, 2021 at 8:57 PM KS0JD-Jeff-913-558-0388 <darbyj16@...> wrote:
Nothing comes up in that window either


locked Re: Logging with HRD Log V6 (Submode) #HRD

Jim - N4ST
 

Monty,

You have to run the Beta version to avoid the FT4 submode problem with FT8

___________

73,

Jim – N4ST

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Monty Wilson, NR0A
Sent: Monday, June 14, 2021 23:34
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Logging with HRD Log V6 (Submode) #HRD

 

Laurie

 

On more piece of Data.  On the two entires I had in my HRD logbook with Mode FT8 and submode FT4, I last previous contact I had with both station was using FT4.  Of course the MODE is MFSK and submode was FT4.  Is HRD sometimes (occasionally) pulling data contact data from its own file and including submode since using FT8 submode is NUL?

 

Hope this is another piece of data to help you out.

 

Monty Wilson, NR0A

nr0a.monty@...

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, June 14, 2021 04:55 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Logging with HRD Log V6 (Submode) #HRD

 

On 14/06/2021 10:24 am, Morris WA4MIT via groups.io wrote:

Thanks Laurie will give this a try.
73 Morris WA4MIT


Morris,

Please can you test this asap. I have just received a report that it is not working. Please if you log a qso to HRD  with an incorrect mode or submode, send me a support request. I don't want to push the new build to public if this defect still exists. I am unable to test HRD inter-operation so have to rely on end-user reports.

Thanks
de Laurie VK3AMA


--
____________________
73,
Jim - N4ST


locked Re: After latest Win (or .Net) Update, JTAlert crashes when emitting any sounds.

Ron W3RJW
 

Tom,

There are literally dozens of postings in this Forum on this subject. Help yourself and read please.
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: After latest Win (or .Net) Update, JTAlert crashes when emitting any sounds.

TomK
 

DETAIL:
Around the time of my last Windows system updates, circa, June 11th, any
time JTA emitted sounds, there were only short scratchy bursts of
unintelligible noise.
After a minute, JTA crashed. Windows opened "app crashed" popup, asked to
Cancel, did so, then JTA restarts and continues until the next sound.
Turning off sound stopped the crashing but, of course, then there was no
sound to alert me.
Not sure if this is due to the updated Windows binaries or .Net - both of
which had updates on June 8th.
Never thought I'd miss the JT sounds so much.

Here are the specific updates that occurred circa the JT crashing around
June 11th.
1. June 8, 2021- KB5003637 (OS Builds 19041.1052, 19042.1052, and
19043.1052)
2. June 8, 2021 -.Net 5.0.7
Although dated June 8th, they were only installed around June 11th when JTA
audio started blowing up.

I have not found any other Win apps that are similarly affected.
I tried changing JTA's output device among several I have (Motu phones,
RealTek speakers, virtual mixers, etc.)
Nothing changed. JTA crashes on audio no matter the device or its type.

I'm only guessing it might be an incompatibility between JTA's output device
selection and/or audio formatting with latest .Net 5.0.7 version.

Hope that helps.
TomK / KT1TK / 73

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of
Laurie, VK3AMA
Sent: Tuesday, June 15, 2021 4:54 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Screen disappearded



On 15/06/2021 5:54 pm, Paul F6EXV wrote:
It is greyed out... I cannot activate it...
If its greyed out it is because you don't have a log enabled. There is no
point showing the log fields if there is no logger to log to. You will note
the titlebar will be displaying "NO Log"

de Laurie VK3AMA


locked Re: Journalisation avec HRD Log V6 (Submode) #HRD

f8nhf
 

Hello to all
I confirm that with the BETA version everything is ok
Thanks Laurie 



locked Re: Screen disappearded

Paul F6EXV
 

That was it ! Problem solved !
Thanks Laurie !
73
Paul F6EXV

Le 15/06/2021 à 10:53, Laurie, VK3AMA a écrit :


On 15/06/2021 5:54 pm, Paul F6EXV wrote:
It is greyed out... I cannot activate it...
If its greyed out it is because you don't have a log enabled. There is no point showing the log fields if there is no logger to log to. You will note the titlebar will be displaying "NO Log"

de Laurie VK3AMA





locked Re: Screen disappearded

Laurie, VK3AMA
 

On 15/06/2021 5:54 pm, Paul F6EXV wrote:
It is greyed out... I cannot activate it...
If its greyed out it is because you don't have a log enabled. There is no point showing the log fields if there is no logger to log to. You will note the titlebar will be displaying "NO Log"

de Laurie VK3AMA


locked Re: Screen disappearded

Paul F6EXV
 

It is greyed out... I cannot activate it...

Le 15/06/2021 à 09:32, DAVID GILLIES via groups.io a écrit :
View and then Show Log Fields in menu.


73

David

MM0AMW


------ Original Message ------ From: "Paul F6EXV" <f6exv@...> To: Support@HamApps.groups.io Sent: Tuesday, 15 Jun, 21 At 08:11 Subject: [HamApps] Screen disappearded Hi all Just launched JTDX and then JTAlert (v 2.50.1) Ther first window now only shows the title with tyhe version number, callsign, current band..., and the menu line. It used to have a section where you could enter name, grid, and you could see the bands where you had made QSO with the current station. That part of the screen is gone... How can I get it back ? Thanks + 73 Paul F6EXV


locked Re: Screen disappearded

DAVID MM0AMW
 

View and then Show Log Fields in menu.


73

David

MM0AMW




------ Original Message ------
From: "Paul F6EXV" <f6exv@...>
To: Support@HamApps.groups.io
Sent: Tuesday, 15 Jun, 21 At 08:11
Subject: [HamApps] Screen disappearded

Hi all
Just launched JTDX and then JTAlert (v 2.50.1)
Ther first window now only shows the title with tyhe version number, callsign, current band..., and the menu line.
It used to have a section where you could enter name, grid, and you could see the bands where you had made QSO with the current station.
That part of the screen is gone...
How can I get it back ?

Thanks + 73
Paul F6EXV






locked Re: Logging with HRD Log V6 (Submode) #HRD

Mike G0LQI
 

Hi Laurie,
Just to say, I log with HRD6 and  since I installed your beta about a month ago I have had no instances of false FT4 submode on FT8 QSOs.
73 Mike G0LQI


locked Screen disappearded

Paul F6EXV
 

Hi all
Just launched JTDX and then JTAlert (v 2.50.1)
Ther first window now only shows the title with tyhe version number, callsign, current band..., and the menu line.
It used to have a section where you could enter name, grid, and you could see the bands where you had made QSO with the current station.
That part of the screen is gone...
How can I get it back ?

Thanks + 73
Paul F6EXV


locked Callsign window in v2.50.0 #FT8

Chris Levingston
 

I am using WSJT-X v2.4.0 and JTAlert v2.16.4.

I recently upgraded to JTAlert v2.50.0 but I can't see the Callsigns window, which is really frustrating.

Clicking on the View menu brings up the View menu but then but clicking on the stars for F3, F5, F11 and F12 does not work, nor does pressing the function keys.
The others work.  
I have gone back to 2.16.4 until I can find a fix.

This has gone back a page so Laurie may not have seen it after suggesting a fix that I had already done (and we had a long weekend since I posted), so I have re-posted.

73s,

Chris    VK5SA

PS Many thanks to Laurie for all of his work on a great program!


locked Re: Logging with HRD Log V6 (Submode) #HRD

Laurie, VK3AMA
 

On 15/06/2021 1:19 pm, f6eqz@sfr.fr wrote:
Hello Laury I am using the beta version since it was released no more problem with HRD. This verified at several OMs in my region. Thank you for everything. 73 John
Tnx John,

It was my understanding based on feedback from users of the Beta that the HRD logging was fixed. Then today I received an email indicating that is not the case, I really don't know as I am still waiting for that user to send me a support request so I can examine his JTAlert session data.

de Laurie VK3AMA

2281 - 2300 of 37666