Date   

locked Re: jtalert stopped talking to wsjt-x

Chris Morrison
 

Disabling the Windows Firewall and deleting the entries in the Windows firewall rule set for JTalert and WSJT-X made no difference.
I've just reinstalled JTalert 2.50.1 leaving .Net runtime 5.0.7 installed and its working again with multicast; using 4 separate instances of WSJT-X all running with the same multicast IP (224.0.0.0) and port number (2237).

Grid Tracker is still not working with Multicast from WSJT-X. I haven't used that in a while so that might not of been working for some other reason and was a red herring. 

Another point I noticed this evening is with 2.50.2 the Help -> About JTalert did nothing. It's working for me with 2.50.1. That could be related to issue.

73
Chris
MM1PTT


locked Re: Help with JTAlert 2.50.1

Dave Garber
 

try this one,   some may be radio specific, and need google to find

Dave Garber
VE3WEJ / VE3IE


On Wed, Jun 23, 2021 at 3:17 PM <robertsimoneau1955@...> wrote:
I could not instructions to fix it. Do you remember where you seen them? Thanks in advance.

Bob


locked Re: QSL Flags ver. 2.50.2

WarrenG KC0GU
 

I apologize got 2.50.2 installed correctly and it works as expected.

Sorry about that,

Warren


locked Re: Update Help

Tom Melvin
 

See message posted yesterday - version 2.50.2 has the solution - issue with MS upgrade

Tom
GM8MJV

On 23 Jun 2021, at 15:06, George Pappayliou via groups.io <w3gp=me.com@groups.io> wrote:

Hello All

I have been running JTAlertx version 2.16.17 which has been operating flawless with WSJT and ACLog.

I recently tried to update to 2.50.1 without success.

I first installed .NET 5 on my windows NUC. I confirmed via the CMD prompt that 5.0.7 had been installed. I then installed 2.50.1 but it simply will not communicate with WSJT. After a couple minutes I get a UDP error and have tried the troubleshooting from Help without success. I cannot copy the data from Help>Info because clicking on that does not bring up the info sub-window as it did in version 2.16.17. I have not changed the UDP settings from what they were under 2.16.17–as I recall: 127.0.0.1 and port 2237. Also testing the sound card produced no sound.

I have rolled-back to 2.16.17 which continues to work fine.

I suspect there is a problem with .NET 5 Desktop Runtime but I don’t know what it is and have installed it multiple times.

Any suggestions gratefully received. If possible a direct email (w3gp@arrl.net) would be great in case I miss the post here.


73 George W3GP
------------------------------------
George S. Pappayliou






locked Re: Trojan Detection

HamApps Support (VK3AMA)
 

On 23/06/2021 10:30 pm, Hank wrote:
Is it safe to assume that there is no trojan and this is a false detection?


In my opinion it is safe. The two false-positive submissions I made to Microsoft, for versions x86 & x64, have both come back as no malware detected.

If you're worried, make your own submission to Microsoft and wait for their results.

Ultimately, the decision to use the software is in the hands of the end-user. If they are uncomfortable with running the software despite assurances from multiple sources the software is safe, then
don't use it, remove it from your system, and move on.


de Laurie VK3AMA


locked Re: Help with JTAlert 2.50.1

robertsimoneau1955@...
 

I could not instructions to fix it. Do you remember where you seen them? Thanks in advance.

Bob


locked Re: Help needed

Michael Lizzio
 

Since I was a victim of identity theft a few years back and in my work provided support for IT SCADA for a major petroleum pipeline company for many years. theaths that are identified by the tools we have at hand must be taken seriously.  

I really enjoy using JTALERT but will not assume that things can't go wrong. If an AV software flags it unsafe I will heed the warning. You know what happens when you assume.

Thank you for the use of an excellent program. 

Mike WA2TOP 

On Wed, Jun 23, 2021, 09:06 chas cartmel <chas@...> wrote:

Many AV software flag JTA as ‘suspicious’ as they have a limited user base to establish it’s veracity.
If you download to an ‘exempt’ folder then make the install folder ‘exempt’ by adding it to a white list of safe locations then all will be well for this and future installs. Laurie provides virus check data on the site by the download link.

This has been flogged to death over the years, with the same advice provided time and time again.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Chuck Adams
Sent: 23 June 2021 12:40
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Help needed

 

Sam,

 

From where did you download the latest version of JTAlert?

 

I would backtrack, delete the downloaded file, and try to re-download and re-install.

 

Chuck

KV4VT

 

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of davebacon1377
Sent: 23 June, 2021 5:26 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Help needed

 

 

Good Day,

 

This has stopped me from being able to download the new version. My knowledge on computers is limited.  Do you have any idea how I can get rid of this problem?

I am using Windows Defender.

Thank you in advance for your help.

 

73,

 

Sam Bacon

KD2T

Oriental NC

USA

 

 

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Update Help

George Pappayliou
 

Hello All

I have been running JTAlertx version 2.16.17 which has been operating flawless with WSJT and ACLog.

I recently tried to update to 2.50.1 without success.

I first installed .NET 5 on my windows NUC. I confirmed via the CMD prompt that 5.0.7 had been installed. I then installed 2.50.1 but it simply will not communicate with WSJT. After a couple minutes I get a UDP error and have tried the troubleshooting from Help without success. I cannot copy the data from Help>Info because clicking on that does not bring up the info sub-window as it did in version 2.16.17. I have not changed the UDP settings from what they were under 2.16.17–as I recall: 127.0.0.1 and port 2237. Also testing the sound card produced no sound.

I have rolled-back to 2.16.17 which continues to work fine.

I suspect there is a problem with .NET 5 Desktop Runtime but I don’t know what it is and have installed it multiple times.

Any suggestions gratefully received. If possible a direct email (w3gp@arrl.net) would be great in case I miss the post here.


73 George W3GP
------------------------------------
George S. Pappayliou


locked Trojan Detection

Hank
 

Hello all.  I managed to turn off virus protection and download the latest JTAlert.  Installed and no issues.  This morning Windows 10, Windows security believes it detected Trojan:Win32/Hynamer.A!ml in file: C:\JTAlert\plugins\JTAlertSettings.exe.  I was able to restore the file from quarantine and include it as an exclusion in Windows Security under Virus and Threat Protection Settings, Exclusions, Add or Remove Exclusions.

Is it safe to assume that there is no trojan and this is a false detection?

73!


locked Re: Help needed

Michael Lizzio
 

I experienced the same problem and reported the problem to support@hamapps with a screen shot yesterday.. In my case I downloaded the latest version from https://hamapps.com/.

Regards... Mike WA2TOP

On Wed, Jun 23, 2021 at 6:40 AM Chuck Adams <cfadams@...> wrote:

Sam,

 

From where did you download the latest version of JTAlert?

 

I would backtrack, delete the downloaded file, and try to re-download and re-install.

 

Chuck

KV4VT

 

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of davebacon1377
Sent: 23 June, 2021 5:26 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Help needed

 

 

Good Day,

 

This has stopped me from being able to download the new version. My knowledge on computers is limited.  Do you have any idea how I can get rid of this problem?

I am using Windows Defender.

Thank you in advance for your help.

 

73,

 

Sam Bacon

KD2T

Oriental NC

USA

 

 




locked Re: jtalert stopped talking to wsjt-x

Joe Subich, W4TV
 

Have you checked your Windows Firewall? Sounds like WSJTX is not
being allowed access to the network (*or* it is set to "Run as
Administrator" for some reason).

73,

... Joe, W4TV

On 2021-06-23 2:23 PM, Chris Morrison wrote:
I've had the same problem today, but I've been looking at WSJT-X as the source of the problem, with no success, as Grid tracker stopped working too. Its like WSJT-X multicast has stopped working.
Last night I turned off the laptop with everything work. This morning, on a fresh boot up, I installed JTalert 2.50.2 along with .NET runtime 5.0.7. From then JTalert started complaining that it cant communicate with WSJT-X.
I then tried launching Grid tracker (I cant remember when I last used it, but was already setup for multicast) and it has a similar problem. I then uninstalled JTalert and .NET and it still didn't fix the issue with Grid Tracker. I then installed WSJT-X v2.5.0 rc-1 but got the same issue.
So I started adjusting the IP addresses and ports in the WSJT-X config with no success.
Going back to unicast (127.0.0.1) with individual port number per WSJT-X instance allowed Grid Tracker to communicate with each instance when I set the correct port number in Grid Tracker, but JTalert is displaying the same error regardless if its unicast or multicast. The error is showing that its detecting the correct port and IP address to listen to from the WSJT-X config but no traffic is being passed in either unicast or mullticast mode for JTalert. Grid Tracker on working in unicast.
Below is sample Jtalert error when trying to use multicast:
Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 224.0.0.0
  Values read from WSJT-X config file...
    C:\Users\chris\AppData\Local\WSJT-X - SliceB\WSJT-X - SliceB.ini
WSJT-X Detected Instance...
  Process Window Title : WSJT-X - SliceB   v2.5.0-rc1   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line : "C:\Radio\wsjtx\bin\wsjtx.exe" --rig-name=SliceB
Decode alerts and logging will be unavailable until corrected.
I've also tried disabling the Windows Firewall, deleting the entries in the firewall rule set for JTalert and WSJT-X but no success so far.
73,
Chris
MM1PTT


locked Re: JTAlert version 2.50.2

Ronald Ford
 

Thanks took your advice…installed and working great…
--
73
Ronald, W4RJF


locked Re: jtalert stopped talking to wsjt-x

Chris Morrison
 

I've had the same problem today, but I've been looking at WSJT-X as the source of the problem, with no success, as Grid tracker stopped working too. Its like WSJT-X multicast has stopped working. 

Last night I turned off the laptop with everything work. This morning, on a fresh boot up, I installed JTalert 2.50.2 along with .NET runtime 5.0.7. From then JTalert started complaining that it cant communicate with WSJT-X.
I then tried launching Grid tracker (I cant remember when I last used it, but was already setup for multicast) and it has a similar problem. I then uninstalled JTalert and .NET and it still didn't fix the issue with Grid Tracker. I then installed WSJT-X v2.5.0 rc-1 but got the same issue.

So I started adjusting the IP addresses and ports in the WSJT-X config with no success. 
Going back to unicast (127.0.0.1) with individual port number per WSJT-X instance allowed Grid Tracker to communicate with each instance when I set the correct port number in Grid Tracker, but JTalert is displaying the same error regardless if its unicast or multicast. The error is showing that its detecting the correct port and IP address to listen to from the WSJT-X config but no traffic is being passed in either unicast or mullticast mode for JTalert. Grid Tracker on working in unicast. 

Below is sample Jtalert error when trying to use multicast:

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 224.0.0.0
  Values read from WSJT-X config file...
    C:\Users\chris\AppData\Local\WSJT-X - SliceB\WSJT-X - SliceB.ini
 
WSJT-X Detected Instance...
  Process Window Title : WSJT-X - SliceB   v2.5.0-rc1   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line : "C:\Radio\wsjtx\bin\wsjtx.exe" --rig-name=SliceB
 
Decode alerts and logging will be unavailable until corrected.


I've also tried disabling the Windows Firewall, deleting the entries in the firewall rule set for JTalert and WSJT-X but no success so far.

73,
Chris
MM1PTT
 


locked {SPAMFILTER} [HamApps] wont talk to wsjt

Anthony W. DePrato
 

Jim and Tom
thank you as you can see below i have changed the reporting also
i did left the loopback at 0 as the dropdown did not have a 4. i will try to change it manualy
still nothing
73 Tony





[]  

[]  Virus-free. www.avg.com



locked ARRL Contest Update for June 23, 2021 wrote:

Jim Cooper
 

On 23 Jun 2021,

The ARRL Contest Update for June 23, 2021 wrote:


Be a Good Ham Radio Software "Customer"

Much of the software that we use in amateur radio is free to download and use. The program authors were generous enough to devote their time and energy to create something that they've shared with others. Some popular ham radio software is downloaded and used by literally tens of thousands of people. Inevitably, someone will have difficulty with the operation of the program, and need "support." For most, dare I say all, program authors, the "support" part is not the most fun part of writing software. For a number of years now, the support model for free software consists of an email reflector or user group (e.g. groups.io) where the software developers, software enthusiasts, and people using the software communicate to discuss features and future functionality and address support issues. The people answering the questions are also volunteers. Support groups usually have guidelines about what information to include in a support issue, how to label the message, and general support forum etiquette.

Support volunteers appreciate it when issue reports have as much relevant information about the problem as possible, and demonstrate that the reporter has diligently attempted to solve their issue after reading appropriate documentation and searching the support group for messages from others who have had the issue.

A comprehensive report includes whatever the program authors require , which likely includes the software version (it should be the latest version of the software), the operating system type and version, type of computer, whether this is a new installation, and the steps required to reproduce the issue. Most amateur radio software works with other software or hardware, so sometimes the details of the related pieces will be necessary too. If an issue reporter has done the research on their issue by reading other solved issue reports, they will probably have a good idea of the information that should be included.

If you need to file an issue, here are some tips that can get your issue to stand out in a good way:

  • Provide quality screenshots, if they are relevant. Don't use cell phone pictures. Use the built-in capabilities of your computer to provide the best pictures possible. On Windows 10, this is the Snipping Tool , or its successor, Snip & Sketch .
  • Make a screencast (video) demonstrating the issue if it involves multiple steps. Again, don't use your cell phone for this. On Windows 10, you can use the capture feature of the XBOX Game Bar built-in app .
  • Store your screenshots and/or videos online where they can be reviewed by the support team. There are a multitude of (free) services that can do this. One example is GetCloudApp.com, which is free and provides links you can embed in your issue report.
  • Please don't use ALL CAPS to describe your issue. This is the equivalent of yelling.
  • When your issue gets resolved, mark it as Solved, so others researching an issue like yours in the future can find your solution.
  • Remember that there may be thousands of people who monitor messages in the support forums so keep the "Signal to Noise Ratio" high in your communications.

Sometimes it turns out that just following the guidelines for reporting an issue can help you find the solution yourself, saving both you and volunteers on the other end both time and effort.

  


locked Re: jtalert stopped talking to wsjt-x

Tom Melvin
 

The IP address is set in WSJTX - Settings - Reporting Tab.

JTAlert gets the details from wsjtx

Tom
GM8MJV



On 23 Jun 2021, at 16:25, Anthony W. DePrato <wa4jqs@...> wrote:



I am sure this has been gone over many times but i could use some help please

I DL the newest version of WSJT-X

I DL and installed the needed .NET

I DL and installed the newest version of jtalert

Now i am getting the following message that jtalert can not talk to wsjt-x i looked in the settings and and checked the UDP on Muiltcast and restarted everything still nothing
I am running wins 7 pro with 8 gig of ram. i looked in the help file and found the following

1.

UDP Server must be a valid multicast IP address. 224.0.0.1 is recommended. Addresses in the 224.0.0.1 to 224.0.0.255 range or 239.0.0.1 to 239.255.255.255 range are supported.

2.

Accept UDP requests must be enabled.

3.

A loopback interface needs to be selected in the "Outgoing interfaces" selector.

4.

JTAlert needs the "Settings -> WSJT-X UDP Multicast on Loopback" menu ticked. This is checked but can not find the box to set up the ip address ect.
thanks for any help
73 Tony WA4JQS ..

 

Wsjtx_Udp_Setup

 

JTAlert_Udp_Setup






















Emacs!


locked wont talk to wsjt

Anthony W. DePrato
 

Found settings in wsjt-x  and set as follows only difference is loopback is 0 instead of 4
still nothing
73 Tony





[]


locked jtalert stopped talking to wsjt-x

Anthony W. DePrato
 



I am sure this has been gone over many times but i could use some help please

I DL the newest version of WSJT-X

I DL and installed the needed .NET

I DL and installed the newest version of jtalert

Now i am getting the following message that jtalert can not talk to wsjt-x i looked in the settings and and checked the UDP on Muiltcast and restarted everything still nothing
I am running wins 7 pro with 8 gig of ram. i looked in the help file and found the following

1.

UDP Server must be a valid multicast IP address. 224.0.0.1 is recommended. Addresses in the 224.0.0.1 to 224.0.0.255 range or 239.0.0.1 to 239.255.255.255 range are supported.

2.

Accept UDP requests must be enabled.

3.

A loopback interface needs to be selected in the "Outgoing interfaces" selector.

4.

JTAlert needs the "Settings -> WSJT-X UDP Multicast on Loopback" menu ticked. This is checked but can not find the box to set up the ip address ect.
thanks for any help
73 Tony WA4JQS ..

 

Wsjtx_Udp_Setup

 

JTAlert_Udp_Setup






















Emacs!


locked Re: JTAlert 2.50.2 install on Windows 10 Edge #FT8

neil_zampella
 

Jim,

I'm fairly sure that M$ has integrated Edge with Defender.  When I use Firefox I can download, but if there's an issue AVG will let me know once its downloaded and it checks it.      Edge won't even get you that far.

 

Neil, KN3ILZ


locked Re: Help needed

chas cartmel
 

Many AV software flag JTA as ‘suspicious’ as they have a limited user base to establish it’s veracity.
If you download to an ‘exempt’ folder then make the install folder ‘exempt’ by adding it to a white list of safe locations then all will be well for this and future installs. Laurie provides virus check data on the site by the download link.

This has been flogged to death over the years, with the same advice provided time and time again.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Chuck Adams
Sent: 23 June 2021 12:40
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Help needed

 

Sam,

 

From where did you download the latest version of JTAlert?

 

I would backtrack, delete the downloaded file, and try to re-download and re-install.

 

Chuck

KV4VT

 

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of davebacon1377
Sent: 23 June, 2021 5:26 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Help needed

 

 

Good Day,

 

This has stopped me from being able to download the new version. My knowledge on computers is limited.  Do you have any idea how I can get rid of this problem?

I am using Windows Defender.

Thank you in advance for your help.

 

73,

 

Sam Bacon

KD2T

Oriental NC

USA

 

 

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

2161 - 2180 of 37666