Date   

locked Re: JTAlert 2.50.2 About doesn't appear, no comm from WSJT-X

Gary N6DM
 

After a few minutes an About box did finally appear with "UDP Communications Failure" message.  The port and IP match what is set up in WSJT-X.

image.png


locked JTAlert 2.50.2 About doesn't appear, no comm from WSJT-X

Gary N6DM
 

I've been trying to get WSJT-X (2.4.0) to send decodes to JTAlert (2.50.2) on my Win10 box but no success.  I tried reinstalling JTAlert, but same result.  I've followed all the instructions in the JTAlert Help under WSJT-X UDP Setup without success.  And at the end of the Setup it says to open the JTAlert About window but the About window never appears.  What have I missed?  
Gary


locked Re: JTAlert 2.5.20 won't run

HamApps Support (VK3AMA)
 

On 11/07/2021 3:38 am, CSM\(r\) Gary Huber - AB9M wrote:
This morning JTAlert which had been running previously with no problems on Win 10 Pro 64 bit, would attempt to load but would not run. I've removed and reinstalled both versions online. Downloaded and installed both versions of .NET , reset the UDP address in WSJT-X I've made sure the software is "TRUSTED" by the security software... Forty years of software and computer programming experience and NO JOY after five hours of reboots and reinstalls...

Is there an error message shown? If so, post an image of the offending window, but don't include your entire desktop, just the error window is enough.

In my experience, when JTAlert stops working when it previously behaved correctly, without any change to the program, the usual suspect is the PC Protection software interfering.

Under Win10, often a PC restart is enough to restore application functionality or to correct changed behavior. This is not limited to JTAlert but can be the fix for unrelated applications that start to misbehave.

As for the NET reinstall, Make sure you're installing the "Desktop Runtime", not the non-Desktop Runtime.

de Laurie VK3AMA


locked Re: Single/double click within callsigns window not working - solved

HamApps Support (VK3AMA)
 

On 11/07/2021 10:09 pm, BOB K5HX via groups.io wrote:
Thanks to all for the assistance and offers of support. In the Application Control/Program Control Area of Zone Alarm, I attempted to set a trust level of "super" to everything that I could find that relates to either JTAlert or WSJT-X.  This did not work and then went into the Zone Alarm global settings area for application control and changed the network firewall setting from "Auto" to "Minimum" which then changed the trust settings of several programs to the super trust level.  It must have also modified some other settings which weren't readily apparent.  In any event the JTAlert single-click interaction with WSJT-X now functions properly.

Bob K5HX

Tnx for the update Bob.

Unfortunately I can't offer any informed advice on why Zone Alarm was behaving as it was or on the fix. I haven't used it for at  least a decade, probably more.

de Laurie VK3AMA


locked Re: Moving from WSJT-X to JTDX #JTDX #FT8

HamApps Support (VK3AMA)
 

On 10/07/2021 9:19 pm, David Gould wrote:
I am unsure about getting .Net5 on to a W7 Home Premium computer. 

73,  Dave G3UEG

There is no harm in installing the NET 5 Desktop Runtime, even if your version of JTAlert doesn't use it. If it installs correctly without showing an error you can be reasonably confident that you can run the new 2.50.x JTAlert. If things go pear-shaped, it is easy to downgrade JTAlert, simply run the installer for the old version. Your settings are save and the config file is compatible between the old and new versions.

de Laurie VK3AMA


locked Re: Callsign Options Symbols dropdowns not sticking - DEFECT CONFIRMED

HamApps Support (VK3AMA)
 

On 11/07/2021 12:51 am, Carey, WB4HXE wrote:

JTAlert 2.50.2. Under the Callsign Options window, Callsigns selection, the dropdowns for Lotw, Eqsl and Online don't seem to be working. I can select from the dropdown but when I release the mouse button, the item turns blank. See attached snip.

--
73, Carey, WB4HXE

Tnx Carey.

I can confirm the defect, and am seeing it here repeatedly. It went unnoticed as I am currently non-active using WSJT-X/JTAlert, haven't been for a couple of years!

Since this is reproducible in my tests, it should be painless, I hope, to identify the cause and produce a fix in time for the next public release.

de Laurie VK3AMA


locked Re: What happened to Ignore callsign option

HamApps Support (VK3AMA)
 

On 12/07/2021 12:23 am, Michael Black via groups.io wrote:
Would be nice to have that on the right-click on the call sign.


It's there! I rarely remove existing functionality. If I do it is documented. In this case, it was new functionality

The release notes...
2.50.1 (2021-May-01)

  New:

    - Callsigns window: The callsign right-click context menu can be customized.
       It can be turned off completely or individual entries can be hidden.



de Laurie VK3AMA


locked Re: Message window focus

HamApps Support (VK3AMA)
 

On 11/07/2021 2:21 am, Don AA5DE wrote:
How can I prevent message window losing focus while typing a message? Alerts or other window updates cause focus to be lost and typing suspended even though text cursor still blinking. Loses word and letters in the message.

-- 
AA5DE, Don

If the Messaging window is losing focus it will be because another window is taking focus. You need to identify the offending window and take corrective action to prevent it being focused.

If it is the WSJT-X window becoming focused, it is likely coming from the JTAlert "To Top" settings. You will need to modify or disable the setting. See the "Applications -> WSJT-X / JTDX" section of the main JTAlert window Settings (F2)

   

de Laurie VK3AMA


locked Re: Jtalert settings

HamApps Support (VK3AMA)
 

On 10/07/2021 1:28 pm, heath calhoun - kb5vai wrote:
Can I modify the settings without opening the jtalert program?

NO. The Settings widow can only be started properly from within JTAlert.

de Laurie VK3AMA


locked Re: event errors

HamApps Support (VK3AMA)
 

On 11/07/2021 11:30 am, AB8WD-Willie via groups.io wrote:
event log errors
Log Name:      Application
Source:        Application Error
Date:          7/10/2021 3:32:22 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
Faulting application name: JTAlertV2.Manager.exe, version: 2.50.2.0, time stamp: 0x609308e7
Faulting module name: coreclr.dll, version: 5.0.721.25508, time stamp: 0x609303c0
Exception code: 0xc0000005
Fault offset: 0x00000000001ca4a7
Faulting process id: 0x2294
Faulting application start time: 0x01d775c24bafaa56
Faulting application path: C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.7\coreclr.dll
Report Id: ae594e9c-23ea-4c53-b555-aaaf8f02a62a
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-10T19:32:22.4224266Z" />
    <EventRecordID>10206</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>JTAlertV2.Manager.exe</Data>
    <Data>2.50.2.0</Data>
    <Data>609308e7</Data>
    <Data>coreclr.dll</Data>
    <Data>5.0.721.25508</Data>
    <Data>609303c0</Data>
    <Data>c0000005</Data>
    <Data>00000000001ca4a7</Data>
    <Data>2294</Data>
    <Data>01d775c24bafaa56</Data>
    <Data>C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe</Data>
    <Data>C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.7\coreclr.dll</Data>
<Data>ae594e9c-23ea-4c53-b555-aaaf8f02a62a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

error 2 Log Name:      Application
Source:        .NET Runtime
Date:          7/10/2021 3:32:22 PM
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
Application: JTAlertV2.Manager.exe
CoreCLR Version: 5.0.721.25508
.NET Version: 5.0.7
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB027DA4A7 (00007FFB02610000) with exit code c0000005.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-10T19:32:22.1414233Z" />
    <EventRecordID>10205</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: JTAlertV2.Manager.exe
CoreCLR Version: 5.0.721.25508
.NET Version: 5.0.7
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB027DA4A7 (00007FFB02610000) with exit code c0000005.
</Data>
  </EventData>
</Event>
OM,

At this time, yours is the only report of this. My online searches have not revealed anything significant that identifies the cause.

My only suggestion at this time is to ensure your PC has been restarted, to ensure that any pending updates have been applied and to get Windows back to a normal state. An uninstall of the NET 5.0.x Desktop Runtime followed by a new install wont hurt and takes but a couple of minutes.

Sorry, that's the limit of the advice I can offer at this time.

de Laurie VK3AMA


locked Re: What happened to Ignore callsign option

Michael Black
 

Thanks Joe...never noticed that option.

Mike W9MDB




On Sunday, July 11, 2021, 10:18:07 AM CDT, Joe Subich, W4TV <lists@...> wrote:


On 2021-07-11 10:23 AM, Michael Black via groups.io wrote:
> Would be nice to have that on the right-click on the call sign.

It is ...  if you enable it in Callsigns Window -> Settings -> Menus

Look at "ignore Management"


73,

    ... Joe, W4TV


On 2021-07-11 10:23 AM, Michael Black via groups.io wrote:
> Would be nice to have that on the right-click on the call sign.
> Mike W9MDB
>

>
>      On Sunday, July 11, 2021, 09:11:03 AM CDT, WB5JJJ - George <wb5jjj@...> wrote:

>  Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently.  This was really useful when you start to get annoyed by an alert for a certain callsign and want to just mute him for the duration.  I could drill down the menu system and set their call to ignore, but the click was so much easier and didn't take but a second.  I miss that.
>
> This is most prevalent when an "Alaska" or "Hawaii" call keeps being announced on 6m, but they are actually now in AZ or CA.  They just don't realize the grief (but probably do and enjoy it) they cause by not changing their call from a most wanted one to where they now permanently reside.  But they do get a lot of "hits", but no confirmation of any real value to the uninformed.
>






locked Re: What happened to Ignore callsign option

Joe Subich, W4TV
 

On 2021-07-11 10:23 AM, Michael Black via groups.io wrote:
Would be nice to have that on the right-click on the call sign.
It is ... if you enable it in Callsigns Window -> Settings -> Menus

Look at "ignore Management"


73,

... Joe, W4TV


On 2021-07-11 10:23 AM, Michael Black via groups.io wrote:
Would be nice to have that on the right-click on the call sign.
Mike W9MDB
On Sunday, July 11, 2021, 09:11:03 AM CDT, WB5JJJ - George <wb5jjj@gmail.com> wrote:
Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently.  This was really useful when you start to get annoyed by an alert for a certain callsign and want to just mute him for the duration.  I could drill down the menu system and set their call to ignore, but the click was so much easier and didn't take but a second.  I miss that.
This is most prevalent when an "Alaska" or "Hawaii" call keeps being announced on 6m, but they are actually now in AZ or CA.  They just don't realize the grief (but probably do and enjoy it) they cause by not changing their call from a most wanted one to where they now permanently reside.  But they do get a lot of "hits", but no confirmation of any real value to the uninformed.


locked Re: What happened to Ignore callsign option

Michael Black
 

Would be nice to have that on the right-click on the call sign.

Mike W9MDB




On Sunday, July 11, 2021, 09:11:03 AM CDT, WB5JJJ - George <wb5jjj@...> wrote:


Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently.  This was really useful when you start to get annoyed by an alert for a certain callsign and want to just mute him for the duration.  I could drill down the menu system and set their call to ignore, but the click was so much easier and didn't take but a second.  I miss that.  

This is most prevalent when an "Alaska" or "Hawaii" call keeps being announced on 6m, but they are actually now in AZ or CA.  They just don't realize the grief (but probably do and enjoy it) they cause by not changing their call from a most wanted one to where they now permanently reside.  But they do get a lot of "hits", but no confirmation of any real value to the uninformed.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: What happened to Ignore callsign option

Dave (NK7Z)
 

Look under Misc, second option down... In version 2.50.2.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 7/11/21 7:10 AM, WB5JJJ - George wrote:
Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently.  This was really useful when you start to get annoyed by an alert for a certain callsign and want to just mute him for the duration.  I could drill down the menu system and set their call to ignore, but the click was so much easier and didn't take but a second.  I miss that.
This is most prevalent when an "Alaska" or "Hawaii" call keeps being announced on 6m, but they are actually now in AZ or CA.  They just don't realize the grief (but probably do and enjoy it) they cause by not changing their call from a most wanted one to where they now permanently reside.  But they do get a lot of "hits", but no confirmation of any real value to the uninformed.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked What happened to Ignore callsign option

WB5JJJ - George
 

Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently.  This was really useful when you start to get annoyed by an alert for a certain callsign and want to just mute him for the duration.  I could drill down the menu system and set their call to ignore, but the click was so much easier and didn't take but a second.  I miss that.  

This is most prevalent when an "Alaska" or "Hawaii" call keeps being announced on 6m, but they are actually now in AZ or CA.  They just don't realize the grief (but probably do and enjoy it) they cause by not changing their call from a most wanted one to where they now permanently reside.  But they do get a lot of "hits", but no confirmation of any real value to the uninformed.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: Single/double click within callsigns window not working - solved

BOB K5HX
 

Thanks to all for the assistance and offers of support. In the Application Control/Program Control Area of Zone Alarm, I attempted to set a trust level of "super" to everything that I could find that relates to either JTAlert or WSJT-X.  This did not work and then went into the Zone Alarm global settings area for application control and changed the network firewall setting from "Auto" to "Minimum" which then changed the trust settings of several programs to the super trust level.  It must have also modified some other settings which weren't readily apparent.  In any event the JTAlert single-click interaction with WSJT-X now functions properly.

Bob K5HX


locked Re: Callsign Options Symbols dropdowns not sticking

Mike - W1MI
 

I'm having the same issue here on 2 different pcs.  73, Mike - W1MI


On Sat, Jul 10, 2021 at 02:51 PM, Carey, WB4HXE wrote:
Hi Laurie,

JTAlert 2.50.2. Under the Callsign Options window, Callsigns selection, the dropdowns for Lotw, Eqsl and Online don't seem to be working. I can select from the dropdown but when I release the mouse button, the item turns blank. See attached snip.

--
73, Carey, WB4HXE


locked Re: Moving from WSJT-X to JTDX #JTDX #FT8

David Gould
 

Thanks for the  help and advice.

73,
Dave G3UEG


locked event errors

AB8WD-Willie
 

event log errors 
Log Name:      Application
Source:        Application Error
Date:          7/10/2021 3:32:22 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
Faulting application name: JTAlertV2.Manager.exe, version: 2.50.2.0, time stamp: 0x609308e7
Faulting module name: coreclr.dll, version: 5.0.721.25508, time stamp: 0x609303c0
Exception code: 0xc0000005
Fault offset: 0x00000000001ca4a7
Faulting process id: 0x2294
Faulting application start time: 0x01d775c24bafaa56
Faulting application path: C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.7\coreclr.dll
Report Id: ae594e9c-23ea-4c53-b555-aaaf8f02a62a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-10T19:32:22.4224266Z" />
    <EventRecordID>10206</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>JTAlertV2.Manager.exe</Data>
    <Data>2.50.2.0</Data>
    <Data>609308e7</Data>
    <Data>coreclr.dll</Data>
    <Data>5.0.721.25508</Data>
    <Data>609303c0</Data>
    <Data>c0000005</Data>
    <Data>00000000001ca4a7</Data>
    <Data>2294</Data>
    <Data>01d775c24bafaa56</Data>
    <Data>C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe</Data>
    <Data>C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.7\coreclr.dll</Data>
    <Data>ae594e9c-23ea-4c53-b555-aaaf8f02a62a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

error 2 Log Name:      Application
Source:        .NET Runtime
Date:          7/10/2021 3:32:22 PM
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
Application: JTAlertV2.Manager.exe
CoreCLR Version: 5.0.721.25508
.NET Version: 5.0.7
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB027DA4A7 (00007FFB02610000) with exit code c0000005.
 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-10T19:32:22.1414233Z" />
    <EventRecordID>10205</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: JTAlertV2.Manager.exe
CoreCLR Version: 5.0.721.25508
.NET Version: 5.0.7
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB027DA4A7 (00007FFB02610000) with exit code c0000005.
</Data>
  </EventData>
</Event>





locked Re: JTAlert Settings

heath calhoun - kb5vai <hcalhoun@...>
 

Just seeing so many issues onto of issues.





-------- Original message --------
From: Trev <Trev@...>
Date: 7/10/21 02:27 (GMT-06:00)
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JTAlert Settings

Heath ???


On Sat, Jul 10, 2021 at 1:39 AM heath calhoun - kb5vai <hcalhoun@...> wrote:
So what I'm seeing.
Run away run away as monty python and the search for the holy grail.





-------- Original message --------
From: Trev <Trev@...>
Date: 7/9/21 15:58 (GMT-06:00)
Subject: Re: [HamApps] JTAlert Settings

Many thanks for that explanation Laurie, I shall hopefully get to grips with it in the morning. I'll let you know how I get on.

Thanks again,
Trev EA5ISZ 

On Fri, 9 Jul 2021, 22:07 HamApps Support (VK3AMA), <vk3ama.ham.apps@...> wrote:
On 9/07/2021 8:25 pm, Trev wrote:
I have just downloaded JTAlert (yesterday) and spent some time connecting to HRD and trying to get to know the software.  Apart from the main page showing decodes and the alerts, the settings bar appeared as a separate page.  I noticed that it had an option that appeared to append the bar to JTDX so I opted for that however, the bar just disappeared from the screen and I now have no access to setting to change alerts etc.  I guess I've done something stupid, but how do I recover short of completely re-installing?  If its useful I'm running Win10 64bit and JTDX v 2.2.156.  By the way, this isn't due to a Windows upgrade as the problem occurred immediately I selected to append the settings bar.
Any help much appreciated,
Thanks, Trev EA5ISZ

You enabled JTAlert docking to JTDX and now the main JTAlert window is no longer visible so have lost access to the menu to turn off docking. Simple fix, either move the JTDX window away from the screen edge will automatically drag JTAlert back into view or resize the JTDX window, reducing its vertical height, will bring JTAlert back into view as the height changes and shrinks away from the screen edge.

The problem is that you have the JTDX window size or position
set such that its top or bottom edge, depending on the docking position set in JTAlert, up against the desktop edge forcing the docked JTAlert window to be positioned off screen.

de Laurie VK3AMA
 



--
Trevor Day

1801 - 1820 of 37662