Date   
locked Re: How can I start decodes history automatically?

WB8ASI Herb
 

It autostarts for me.  Try just leaving it on when you shutdown JTAlert, and I bet it will come back when you start next time.

On September 9, 2019 at 1:45 PM "Hartmut Luedtke via Groups.Io" <geohartmut@...> wrote:

Hello list,

the search did not bring unfortunately any realizations.

Unfortunately Decodes History does not start automatically with the program. How can I always start "Decodes History" (DecodesHistory.exe) automatically with JTAlert? Which parameters are required for the start?
I would like that the small tool is always started with JTAlert.

Settings -> Applications -> Auto-Start ???


vy73 Ham, DB6LL


 


 

locked New install on laptop won't run

Phil Zminda
 

 I just started using a new HP Windows 10 laptop with I5 processor, 256 Gb SSD and 8 Gb memory. When I try to start JT Alert 2.14.13, I get a message "Insufficient resources to complete this service". If I try again a couple times it appears to have disappeared from the Apps. I had no problems running JT Alert on an older Windows 10 laptop or a Dell desktop. I have not seen this with any other software. What could be going wrong?

Thanks,

Phil N3ZP

locked Re: How can I start decodes history automatically?

Ron W3RJW
 

Manage Settings, Window, Decodes History, Restore Window when JTAlert is Started .....

In Decodes History Window -  File, Settings, Startup Options you can select which records you want when you startup ...
--
73
Ron, W3RJW

locked Re: How can I start decodes history automatically?

Jim N6VH
 

On 9/9/2019 10:45 AM, Hartmut Luedtke via Groups.Io wrote:
Hello list,
the search did not bring unfortunately any realizations.
Unfortunately Decodes History does not start automatically with the program. How can I always start "Decodes History" (DecodesHistory.exe) automatically with JTAlert? Which parameters are required for the start?
I would like that the small tool is always started with JTAlert.
Settings -> Applications -> Auto-Start ???
vy73 Ham, DB6LL
_._,_._,_
------------------------------------------------------------------------
Go to Settings/Manage Settings/Window/Decodes History. Check the box "Restore Wimdow when JTAlert is started".

73,

Jim N6VH

locked Re: How to log from JTAlert to N1MM+?

Tom Ramberg
 

Sitrep from OH2K club station: Logging to N1MM+ works now. JTAlert "enable transmission of last qso" on UDP port 2333. N1MM+ set to listen (Radio 1) on port 2333. JTAlert uploads directly to eqsl.cc, qrz.com and Clublog. All is well.
--
73 de Tom OH6VDA

locked Decodes History on two streams

AH0U
 
Edited

I use a Flex 6700 and monitor two slices at a time but the Decodes History only shows the A stream... How do I get it to monitor both streams??
Tnx
Just realized it is not the slice that the Decode History cant copy its the FT4 that it cant copy

locked Re: Decodes History on two streams

HamApps Support (VK3AMA)
 

On 11/09/2019 2:39 am, AH0U wrote:
I use a Flex 6700 and monitor two slices at a time but the Decodes History only shows the A stream... How do I get it to monitor both streams??
Tnx
Just realized it is not the slice that the Decode History cant copy its the FT4 that it cant copy
OM,

The Decodes History has no concept of Flex streams/slices only sources of decodes which are provided by JTAlert instances monitoring WSJT-X instances.

Lack of FT4 decodes in the History window is a known issue affecting users with an out-dated decodes database schema. It has been discussed in the group several time. The simple fix is to use Windows File Explorer to delete the "decodes.sqlite" and "lookup.sqlite" files (all history data will be lost) which are located at %localappdata%\HamApps\JTAlert\YOUR_CALLSIGN\Decode\

de Laurie VK3AMA

locked Re: JTAlert 2.14.3 Sporadically Not Responding

HamApps Support (VK3AMA)
 

On 9/09/2019 1:41 am, wkjohn@... wrote:
After installing the newest versions of JTAlert and WSJT-X, JTAlert is sporadically non responsive and will temporarily freeze.  The program will eventually start working properly or sometimes will give me the following error message.

JTAlert WSJT-X UDP Communications Failure

Unable to communicate with the WSJT-X process.

UDP Port : 2237

IP Address : 127.0.0.1

Values read from WSJT-X config file...

C:\Users\wkjoh\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...

Process Window Title : WSJT-X   v2.1.0   by K1JT

Process Command Line :

Decode alerts and logging will be unavailable until corrected.

See the JTAlert Help file for correct WSJT-X UDP setup.

I have attempted to make changes to my virus software, which is Norton, but that has not corrected the problem.  All software was working properly before the latest update.  Coincidentally, Windows 10 performed a major update around this time, so I guess it could have something to do with that.

Thanks in advance for your help.

73,
Keith
WW5G

Keith,

That "WSJT-X UDP Communications Failure" message is shown when JTAlert fails to receive a UDP packet from WSJT-X within the first 2 minutes after starting. The longest that JTAlert should have to wait is approx 15 seconds.

Typically this is shown when a user has an incorrectly configured WSJT-X setup and it will show all the time after each JTAlert start, not intermittently like you experiencing. Your getting this message due to whatever is causing JTAlert to hang (not responding in Windows terminology).

It is very likely it is your Virus protection that is interfering in JTAlert operation. Blocking Registry or file access, preventing spawning of plugins or blocking internet connections are typically the activities that will cause JTAlert to hang.

Sorry, I can't provide Norton specific setup instructions to white-list JTAlert.

de Laurie VK3AMA



locked Re: New install on laptop won't run

HamApps Support (VK3AMA)
 

On 9/09/2019 10:30 pm, Phil Zminda wrote:
 I just started using a new HP Windows 10 laptop with I5 processor, 256 Gb SSD and 8 Gb memory. When I try to start JT Alert 2.14.13, I get a message "Insufficient resources to complete this service". If I try again a couple times it appears to have disappeared from the Apps. I had no problems running JT Alert on an older Windows 10 laptop or a Dell desktop. I have not seen this with any other software. What could be going wrong?

Thanks,

Phil N3ZP

Phil,

On a new Windows install with your laptop specs, it wont be a lack of resources to run JTAlert. That message is a generic catch-all message from Windows that embraces a number of error conditions.

The disappearance of the JTAlert application suggests that it is your virus/malware protection that is the root cause.

If your using Windows Defender and still running the default settings that come with a new Window install, check the "Controlled folder access" setting, under the "Ransomware protection" section. This has been know to cause problems for many Ham applications, not just JTAlert.

Let us know how you get on.

de Laurie VK3AMA

locked Re: JTAlert debugging

HamApps Support (VK3AMA)
 

On 9/09/2019 5:52 pm, ido1990@... wrote:

I use JTAlert for long time to log my QSO's to HRD5.
I'm not sure when but JTAlert just stopped showing callsigns and log QSO's.
The UDP seems ok as shown in the about window and I tried to reset the configuration for JTAlert as well as WSJT-X but nothing solved the issue.
Both updated to the last version (JTAlert 2.14.3 and WSJT-X 2.1.0)
My firewall software is COMODO and disabling the protection didn't help.

Any ideas how to debug it?

Thanks!

Ido
4X5MG

Ido,

Are you running any other software that might be accessing the WSJT-X UDP traffic?

Run JTAlert for at least 3 minutes then use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Re: Decoded call signs not showing in JTAlert

HamApps Support (VK3AMA)
 

On 10/09/2019 12:32 am, Frode Igland wrote:
I was asked yesterday by a friend to help him get the decoded callsigns to show in JTAlert again, like they have been since he started to use JTAlert a long while ago until a couple of days ago. He is running WSJT-X 2.1.0 and JTAlert 2.14.3 and HRD 6.6.0.237. Logging from WSJT-X to HRD Logbook ran smoothly, so obviously WSJT-X broadcast were working as it should.  As no call signs appeared in JTAlert, we thought the port numbers in WSJT-X and JTAlert might not comply, but they were all correct. We made a fresh install of JTAlert, to no avail. We kept trying other approaches, but made no progress. After all of this, we noticed that a vertical roller field had appeared to the left of the JTAlert call sign fields. We clicked the arrow on top of the roller field, but still no call signs to see. We then changed the number of call sign display lines from 3 to 2 lines, and suddenly the decoded call signs appeared, with everything working as normal. The roller field disappeared, not to be seen again. From WSJT-X we saw that there were certainly enough stations decoded that they would fill more than one or two lines.

I really have no idea why the number of displayed call sign lines made the call signs disappear, and why the change from 3 to 2 display lines made them appear again. Nor do I know if this is a bug, or if it was something we should know. I've never experienced vanished call signs in JTAlert before, nor has my friend. Our experience with JTAlert has been pretty close to flawless. I just thought I'd let the Laurie and the user group know, and maybe someone can offer an explanation or get a hint to search for any possible issue.

Frode LA6VQ

Frode,

Like you, I have no idea why changing the number of display lines appeared to correct the non-display of callsigns. I am unable to reproduce that effect here in testing. I typically run with 2 callsign lines and have never seen this effect.

While you were testing, did you also play with the JTAlert Alert Filter settings? The only way I can reproduce the non-display of Callsigns is to set one of the QSL Filters (eQSL, LoTW) and not have the HamApps Callsign database installed. It is that database that provides JTAlert with the QSL membership status of each decoded callsign and without the data JTAlert treats each callsign has having no QSL service membership causing the callsign to not pass an active LoTW or eQSL filter.

de Laurie VK3AMA

locked Re: New install on laptop won't run

Phil Zminda
 

Hi Laurie,

Thanks for getting back to me. Windows Defender does seem to be the problem. I have tried various settings under "Controlled Folder Access" but nothing seems to resolve the problem. Windows Defender is deleting the JTAleret.exe file. This is with the Folder as a protected folder and JTAlert as protected app.

The laptop does have McAfee Antivirus also but not using it yet. Does McAfee have settings that might allow running JTAlert?

Thanks,

Phil N3ZP

locked Re: New install on laptop won't run

Michael Black
 

Just google "McAfee exclusions"

If I were you I'd uninstall McAfee....they give it to you for free so you can pay later.

Defender and Malwarebytes(free) will do you fine....and don't click on weblinks that you don't recognize and expect...that's where 90+% of infections come from.

de Mike W9MDB




On Wednesday, September 11, 2019, 07:15:32 AM CDT, Phil Zminda <phil-z@...> wrote:


Hi Laurie,

Thanks for getting back to me. Windows Defender does seem to be the problem. I have tried various settings under "Controlled Folder Access" but nothing seems to resolve the problem. Windows Defender is deleting the JTAleret.exe file. This is with the Folder as a protected folder and JTAlert as protected app.

The laptop does have McAfee Antivirus also but not using it yet. Does McAfee have settings that might allow running JTAlert?

Thanks,

Phil N3ZP

locked Re: How can I start decodes history automatically?

Hartmut Luedtke
 

"Restore Window when JTAlert ist startet" was the solution. Thanks a lot Group :-)

vy73 Ham, DB6LL

locked Re: New install on laptop won't run

John Petrocelli
 

Just adding my 2 cents ....

Yes infections are the problem.

I one is running Windows and using the Chrome browser my 2 favorite "Extensions" for Chrome are:
     AddBlockPlus
          &
     ScriptSafe

With ScriptSafe you need to "train" it to permit scrips on each page that you frequently visit.  "Training" is simple and easy and it can help with avoiding infections from scripts.

Thanks for letting me add my 2 cents.
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 9/11/2019 12:36 PM, Michael Black via Groups.Io wrote:
Just google "McAfee exclusions"

If I were you I'd uninstall McAfee....they give it to you for free so you can pay later.

Defender and Malwarebytes(free) will do you fine....and don't click on weblinks that you don't recognize and expect...that's where 90+% of infections come from.

de Mike W9MDB




On Wednesday, September 11, 2019, 07:15:32 AM CDT, Phil Zminda <phil-z@...> wrote:


Hi Laurie,

Thanks for getting back to me. Windows Defender does seem to be the problem. I have tried various settings under "Controlled Folder Access" but nothing seems to resolve the problem. Windows Defender is deleting the JTAleret.exe file. This is with the Folder as a protected folder and JTAlert as protected app.

The laptop does have McAfee Antivirus also but not using it yet. Does McAfee have settings that might allow running JTAlert?

Thanks,

Phil N3ZP



Virus-free. www.avast.com

locked Re: Decoded call signs not showing in JTAlert

Frode Igland
 

Laurie,
We did indeed install the call sign database for the first time on the new computer, but the "no-shows" still didn't show. I am not aware that we made any filter settings that would exclude all call signs after installing the database. My friend is an LoTW user and has the visual flags set to show LoTW users among the decoded signals (mark in upper left corner), but there is no filter set that would exclude any or all call signs. In any case I would believe that no matter which filter setting was in use, there would be some signals over one hour or more that would meet the filter criteria and appear in the decoded fields. Only when we changed to two lines of decoded call signs, the decoded call signs appeared.

I still have no idea what happened, but you can store it at the back of the head if something similar  should show up from others.

No matter what, many thanks for the work you do to improve the user friendliness of the weak signal mode softwares.

73 Frode LA6VQ

locked Re: JTAlert debugging

ido1990@...
 

Thank you.

When I use port 2237 I get an error so I'm using 2238 and this is the output of JTAlert:

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.1.0   by K1JT
WSJT-X Command Line   :
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\INP\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version        : 2.1.0
WSJT-X Revision       : 24fcd1
WSJT-X Spec Op Mode   : None
WSJT-X UDP ID         : WSJT-X
WSJT-X UDP Port       : 2238
WSJT-X UDP Server     : 127.0.0.1
WSJT-X UDP Max Schema : 3

As far as I understand, this means that it's connected but still doesn't show any callsigns...

locked Still more apparent JTALert virus issues

Rick Boswell
 

 

I continue to have difficulty getting HamApps_JTAlert_AL_2.14.3_Setup.exe (the Alternative Layout version) past my malware/virus scanners. Microsoft SafeWeb wont even download the file. Bells ring, sirens sound, and lights flash! On the other hand, HamApps_JTAlert_2.14.3_Setup.exe (the Traditional version) downloads and installs without an issue. I note that VirusTotal shows 24 engines detecting problems with the Alternative Layout version vs only 5 engines detecting problems with the Traditional version. Not clear why this is the case. In any event, I need the Alternative Layout version. I have gone back to 2.13.10 Alternative Layout, which downloads, installs, and runs without apparent virus issues until I have a better handle on what is happening and devise a workaround. 

I hear those here who say not to be concerned and that there is no virus contamination in this software. Maybe I’ll get over it and forge ahead. Because I have never encountered anything like this in any other software in 30+ years of PC experience, I am cautious, as a serious virus/malware infection could prove painful.

locked Re: Still more apparent JTALert virus issues

David Levy
 

Rick,

 

While I share your concerns, these false positive reports are not uncommon with boutique software.  There may be a code snippet that your scanner identifies as malicious. 

 

One possible solution is to submit the file to your AV provider for them to examine and whitelist it.

 

What is your security suite comprised of?

 

David

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Rick Boswell
Sent: Thursday, September 12, 2019 4:49 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Still more apparent JTALert virus issues

 

 

I continue to have difficulty getting HamApps_JTAlert_AL_2.14.3_Setup.exe (the Alternative Layout version) past my malware/virus scanners. Microsoft SafeWeb wont even download the file. Bells ring, sirens sound, and lights flash! On the other hand, HamApps_JTAlert_2.14.3_Setup.exe (the Traditional version) downloads and installs without an issue. I note that VirusTotal shows 24 engines detecting problems with the Alternative Layout version vs only 5 engines detecting problems with the Traditional version. Not clear why this is the case. In any event, I need the Alternative Layout version. I have gone back to 2.13.10 Alternative Layout, which downloads, installs, and runs without apparent virus issues until I have a better handle on what is happening and devise a workaround. 

I hear those here who say not to be concerned and that there is no virus contamination in this software. Maybe I’ll get over it and forge ahead. Because I have never encountered anything like this in any other software in 30+ years of PC experience, I am cautious, as a serious virus/malware infection could prove painful.

locked Re: JTAlert debugging

HamApps Support (VK3AMA)
 

On 12/09/2019 7:01 pm, ido1990@... wrote:
When I use port 2237 I get an error so I'm using 2238 and this is the output of JTAlert:

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.1.0   by K1JT
WSJT-X Command Line   :
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\INP\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version        : 2.1.0
WSJT-X Revision       : 24fcd1
WSJT-X Spec Op Mode   : None
WSJT-X UDP ID         : WSJT-X
WSJT-X UDP Port       : 2238
WSJT-X UDP Server     : 127.0.0.1
WSJT-X UDP Max Schema : 3

As far as I understand, this means that it's connected but still doesn't show any callsigns...
What is the error message when you set WSJT-X to use port 2237?

Regardless, 2237 should work.

Send me a support request as mentioned in my last message.

de Laurie VK3AMA