Date   

locked Re: JTAlert 2.16.5

KF1P Bob
 

No Problem here.....can ya say "False Positive"  ??

We run Iolo System Mechanic and all the "Toys" that come with it.....

remember what you are paying for JTAlert software.....and it IS Virus FREE ! ! !
Says something about the Author.... and we as a community should Thank Him....

BoB  KF1P 


locked 2.16..5 & Defender

Jim Denneny
 

Opened Defender to override blocked setup file.  No blocked setup file in Defender folder.  I went to Downloads and clicked on a tiny symbol at the left edge of the setup entry.  It was only then the Microsoft override option appeared.  I am amazed that opening Defender did not disclose a blocked item.

73 Jim K7EG


locked 2.16.5 download blocked

Jim Denneny
 

Nothing new about that but this time there is a twist. I opened Defender and there was no blocked item.  I had to go to Downloads and click on a small symbol at the left edge of the setup entry.  That caused the Microsoft block notice to pop up and it was only then that I could override and open setup.

Jim K7EG


locked Re: JTAlert does strangle my computer again and again / Final

David De Coons
 

My friend was having intermittent issues with JTAlert 2.16.4. He is running on a Lenovo T430 laptop with 12 GB ram and 50” TV as external monitor.

When I asked him for details about the connections he said itwent HDMI from TV the an HDMI to USB adapter plugged in the laptop. I told him to replace the cable and adapter with a mini display port to HDMI cable since the laptop has a mini display port. Now his CPU usage is around 30%

Point is, check your CPU, memory, and disk usage for any potential bottlenecks in performance.

Dave wo2x



On May 9, 2020, at 7:48 AM, Larry Knain <w6nws@...> wrote:



I have seen AutoIt errors from time to time over the past year or maybe more. I have JTAlert up 24/7 usually and see an AutoIt failure maybe once in 3 to 5 weeks. I just kill JTAlert via TaskManager and restart JTAlert. My machine has 16GB memory usually running about 60% used according to TaskManager. The machine is normally only running WSJT-X, JTAlert, and part of the DXLab logging (rig control, cluster connection, and logging). Running a browser occasionally with the "usual" items does not seem to affect the failure rate.

I don't know how much load the activity seen by WSJT-X generates for JTAlert. I often see about 135K items in WSJT-X's ALL.TXT a day.

73, Larry W6NWS


On 5/9/2020 4:10 AM, asobel@... wrote:

Larry

 

I did suffer from this fault ever since. I had to restart JTAlert few times a day until last week. I did increase my computer’s RAM from 8GB to 24 GB and the fault did almost disappear. Not fully, it does show maybe once a day.

Any ideas?

 

Thanks for caring for us HAMs

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, March 20, 2020 1:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert does strangle my computer again and again 2

 

On 20/03/2020 6:54 am, asobel@... wrote:

In the last few days, JTalert did fail my computer few times a day. I was using V2.16.1 reverting to V2.16.0 and V2.15.11, Win10 version 1909, I7 and 8GB ram. Upon failure, the computer did show the message "Autolt, Error allocating memory", see the attached picture. I am using JTalert and WSJT-X in 4 instances and it is always the first instance which fail. I did find that the processor was slowly increasing it's temperature to 70C so I did re-install the fan with no results and set computer power to "power saver". Processor temperature was reduced but the computer continues to fail. Using  the Task Manager, I did finally discover that the JTalert task(Audio &…) is slowly increasing the CPU load and memory consumption close to 100% and strangulation, see the attached picture.

Your kind help is requested.

 

Amos Sobel 4X4MF.

Amos,

Sorry I don't have an explanation or fix for your problem. Yours is the only report I have seen of this.

The AutoIt memory error is not coming from the JTAlert code as such but from the embedded code interpreter that is part of the executable created by the AutoIt compiler and that is not something I can control.

Once this cascading windows of memory errors is thrown then JTAlert is unusable and the CPU/Memory usage reported by taskmanager is a reflection of the non-functional (failed) state of JTAlert not that JTAlert is a high CPU/Memory usage application. JTAlert has entered a runaway state for some unknown reason

My only suggestion is that you may have a physical memory issue (this is only a guess) and to run a comprehensive memory test.

Sorry, I can't provide a solution.

de Laurie VK3AMA


locked Re: New Marathon visual alert fault

Michael Black
 

What version of WSJT-X are you using?  If not 2.1.2 please upgrade.

de Mike W9MDB




On Saturday, May 9, 2020, 02:53:01 AM CDT, <asobel@...> wrote:


I am using the CQ Marathon alert on JTAlert  2.16.5 and earlier. The CQ
Marathon is producing a lot of verbal alerts but most of the time the visual
alert on both the WSJT-X and JTAlert displays are missing wich makes the
alert quite useless.

For your information, I am using 4 instances of WSJT-X anf JTAlert.

Please fix it ASAP.

Amos Sobel 4X4MF







locked Re: JTAlert does strangle my computer again and again / Final

Larry Knain
 

I have seen AutoIt errors from time to time over the past year or maybe more. I have JTAlert up 24/7 usually and see an AutoIt failure maybe once in 3 to 5 weeks. I just kill JTAlert via TaskManager and restart JTAlert. My machine has 16GB memory usually running about 60% used according to TaskManager. The machine is normally only running WSJT-X, JTAlert, and part of the DXLab logging (rig control, cluster connection, and logging). Running a browser occasionally with the "usual" items does not seem to affect the failure rate.

I don't know how much load the activity seen by WSJT-X generates for JTAlert. I often see about 135K items in WSJT-X's ALL.TXT a day.

73, Larry W6NWS


On 5/9/2020 4:10 AM, asobel@... wrote:

Larry

 

I did suffer from this fault ever since. I had to restart JTAlert few times a day until last week. I did increase my computer’s RAM from 8GB to 24 GB and the fault did almost disappear. Not fully, it does show maybe once a day.

Any ideas?

 

Thanks for caring for us HAMs

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, March 20, 2020 1:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert does strangle my computer again and again 2

 

On 20/03/2020 6:54 am, asobel@... wrote:

In the last few days, JTalert did fail my computer few times a day. I was using V2.16.1 reverting to V2.16.0 and V2.15.11, Win10 version 1909, I7 and 8GB ram. Upon failure, the computer did show the message "Autolt, Error allocating memory", see the attached picture. I am using JTalert and WSJT-X in 4 instances and it is always the first instance which fail. I did find that the processor was slowly increasing it's temperature to 70C so I did re-install the fan with no results and set computer power to "power saver". Processor temperature was reduced but the computer continues to fail. Using  the Task Manager, I did finally discover that the JTalert task(Audio &…) is slowly increasing the CPU load and memory consumption close to 100% and strangulation, see the attached picture.

Your kind help is requested.

 

Amos Sobel 4X4MF.

Amos,

Sorry I don't have an explanation or fix for your problem. Yours is the only report I have seen of this.

The AutoIt memory error is not coming from the JTAlert code as such but from the embedded code interpreter that is part of the executable created by the AutoIt compiler and that is not something I can control.

Once this cascading windows of memory errors is thrown then JTAlert is unusable and the CPU/Memory usage reported by taskmanager is a reflection of the non-functional (failed) state of JTAlert not that JTAlert is a high CPU/Memory usage application. JTAlert has entered a runaway state for some unknown reason

My only suggestion is that you may have a physical memory issue (this is only a guess) and to run a comprehensive memory test.

Sorry, I can't provide a solution.

de Laurie VK3AMA


locked Re: JTAlert does strangle my computer again and again / Final

asobel@...
 

Larry

 

I did suffer from this fault ever since. I had to restart JTAlert few times a day until last week. I did increase my computer’s RAM from 8GB to 24 GB and the fault did almost disappear. Not fully, it does show maybe once a day.

Any ideas?

 

Thanks for caring for us HAMs

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, March 20, 2020 1:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert does strangle my computer again and again 2

 

On 20/03/2020 6:54 am, asobel@... wrote:

In the last few days, JTalert did fail my computer few times a day. I was using V2.16.1 reverting to V2.16.0 and V2.15.11, Win10 version 1909, I7 and 8GB ram. Upon failure, the computer did show the message "Autolt, Error allocating memory", see the attached picture. I am using JTalert and WSJT-X in 4 instances and it is always the first instance which fail. I did find that the processor was slowly increasing it's temperature to 70C so I did re-install the fan with no results and set computer power to "power saver". Processor temperature was reduced but the computer continues to fail. Using  the Task Manager, I did finally discover that the JTalert task(Audio &…) is slowly increasing the CPU load and memory consumption close to 100% and strangulation, see the attached picture.

Your kind help is requested.

 

Amos Sobel 4X4MF.

Amos,

Sorry I don't have an explanation or fix for your problem. Yours is the only report I have seen of this.

The AutoIt memory error is not coming from the JTAlert code as such but from the embedded code interpreter that is part of the executable created by the AutoIt compiler and that is not something I can control.

Once this cascading windows of memory errors is thrown then JTAlert is unusable and the CPU/Memory usage reported by taskmanager is a reflection of the non-functional (failed) state of JTAlert not that JTAlert is a high CPU/Memory usage application. JTAlert has entered a runaway state for some unknown reason

My only suggestion is that you may have a physical memory issue (this is only a guess) and to run a comprehensive memory test.

Sorry, I can't provide a solution.

de Laurie VK3AMA


locked Re: JTAlert 2.16.5

on5po
 



Hello,
For my part, it is when I open HRD that I have the problem, this alert does not seem to be the problem, it is not yet open,
Before, I managed to exclude, control via kaspersky; now impossible

73

ON5PO,Janny


De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de Alfred Reeves <areeves18@...>
Envoyé : vendredi 8 mai 2020 22:32
À : Support@HamApps.groups.io <Support@HamApps.groups.io>
Objet : Re: [HamApps] JTAlert 2.16.5
 
Same thing happened to me.  Here's what I did for Windows 10 OS.  Go to Settings..Update & Security..Windows Security..Virus & threat protection..Manage settings.. turn OFF all 4 protection buttons.  Close out and reboot your computer (important).  Once rebooted you should be able to download the JTAlert file.  After you download the file go through the previous settings (don't change anything) and add the new JTAlert file to an exclusion list.  Then run and install the new JTAlert file.  Following a successful installation you have to go back and turn on all the protection again.  Don't turn it on until you have successfully installed the new JTAlert update. Finally reboot you computer to have the Security settings back to their original settings.  Good luck.

Al
W1JHU


locked New Marathon visual alert fault

asobel@...
 

I am using the CQ Marathon alert on JTAlert 2.16.5 and earlier. The CQ
Marathon is producing a lot of verbal alerts but most of the time the visual
alert on both the WSJT-X and JTAlert displays are missing wich makes the
alert quite useless.

For your information, I am using 4 instances of WSJT-X anf JTAlert.

Please fix it ASAP.

Amos Sobel 4X4MF


locked Re: JTAlert 2.16.5

 

My scenario is a little different.  I’m running ESET NOD32.  It insists there is a virus in JTAlert.exe.  This is even after I have excluded it from detection.  I have been able to totally disable NOD32 long enough to submit the file to ESET.  They do not make it easy.  My subscription is coming up for renewal in July, and they are on the verge of loosing me.

 

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of neil_zampella
Sent: Friday, May 8, 2020 11:27 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.5

 

Well, you're one of the few Defender hasn't done it to.

As was pointed out ... exclude the JT-Alert directory in Defender

Neil, KN3ILZ


On Fri, May 8, 2020 at 03:17 PM, n4qwf . wrote:

Windows defender has blocked the version 2.16.5 as containing a trojan virus on my Windows 10 pro computer. Never done this before.

73<<John


--
Dan - K4SHQ


locked Re: JTAlert 2.16.5

neil_zampella
 

Well, you're one of the few Defender hasn't done it to.

As was pointed out ... exclude the JT-Alert directory in Defender

Neil, KN3ILZ


On Fri, May 8, 2020 at 03:17 PM, n4qwf . wrote:

Windows defender has blocked the version 2.16.5 as containing a trojan virus on my Windows 10 pro computer. Never done this before.

73<<John


locked Re: JTI Suspect

Tom Job
 

Likewise....Avast Security Premium scanned the download file when I tried to execute it and called home to have it checked.  After about 2 minutes, Avast replied that it is safe to install and I did. 

I guess the take-away from all of this is not to get flustered when you antivirus reports JTAlert as a virus.  We all know it's not true.  JTAlert is hobby software and is not a mainstream package so it will get flagged.  Read the documentation for your particular AV and know what to do so that you can create an exception and move on.

73....Tom


locked Re: JTI Suspect

neil_zampella
 

FWIW ... AVG Internet Security just did a quick 15 second scan of the install program, then allowed me to install.

Neil, KN3ILZ


locked Welcome Back Laurie

WB8ASI Herb
 

Can't imagine your backlog.  Hope you had a good getaway.  Bet you're ready to start your next vacation.  73 Herb WB8ASI


locked Re: JT Alert stops populating from WSJT-X - looking for fix

Laurie, VK3AMA
 

On 9/05/2020 1:49 am, Raymond Kasprzak wrote:
Does not cure the problem. I  am using the latest version of WSJTX.
Your not running the latest version  of WSJT-X. Your still at 2.1.0 which is the problem.

Your HamSpots spots data, as of 21:45utc today, clearly shows me that your still at 2.1.0 ("WSJT-X v2.1.0 by K1JT" reported in the spots data header) which is not the latest despite your claims.

de Laurie VK3AMA


locked Re: JT Alert stops populating from WSJT-X - looking for fix

HamApps Support (VK3AMA)
 

On 9/05/2020 1:49 am, Raymond Kasprzak wrote:
Does not cure the problem. I  am using the latest version of WSJTX. 
What is the version number? Please quote the version number. If it is not 2.1.2 than you are not running the latest version.

Everyone who has reported this problem and subsequently upgraded their WSJT-X version reported the problem was resolved.

Also, please sign your messages with a name and callsign.

de Laurie VK3AMA


locked Re: JTAlert 2.16.5

Alfred Reeves
 

Same thing happened to me.  Here's what I did for Windows 10 OS.  Go to Settings..Update & Security..Windows Security..Virus & threat protection..Manage settings.. turn OFF all 4 protection buttons.  Close out and reboot your computer (important).  Once rebooted you should be able to download the JTAlert file.  After you download the file go through the previous settings (don't change anything) and add the new JTAlert file to an exclusion list.  Then run and install the new JTAlert file.  Following a successful installation you have to go back and turn on all the protection again.  Don't turn it on until you have successfully installed the new JTAlert update. Finally reboot you computer to have the Security settings back to their original settings.  Good luck.

Al
W1JHU


locked Re: JTAlert 2.16.5

n4qwf .
 

Windows defender has blocked the version 2.16.5 as containing a trojan virus on my Windows 10 pro computer. Never done this before.

73<<John


locked Re: JTAlert 2.16.5

Michael Black
 

People....this false alert happens all the time....there's no virus in the thing.

Just submit it to your virus vendor and they will whitelist it.

Version 2 is written in autoit which is a scripting program that is really quite powerful...and apparently some virus writers must've used it at some time.  Very few programs other than JTAlert use it.

de Mike W9MDB




On Friday, May 8, 2020, 01:44:04 PM CDT, Dan Malcolm <k4shq@...> wrote:


Very odd.  I never get a virus alert from the JTAlert downloads……until today.  Esets NOD32 has repeatedly given me this error:



C:\Users\k4shq\Downloads\JTAlert.2.16.5.Setup.exe » INNO » {app}\JTAlert.exe - Win32/PSW.Delf.OSF trojan - cleaned by deleting [1]

 

NOD32 is not known to be false positive prone.  My latest update was about 3 hours ago and is automatic.  Until I see something to indicate this is false, or perhaps, inexplicably there is an infection on Laurie’s website, I’m going to treat this as a valid threat.  I will also run an additional update just in case Eset made an error.

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jim AF5FH
Sent: Friday, May 8, 2020 1:16 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.5

 

[Edited Message Follows]

Same experience here, latest version works fine as before. Also reported JTAlert as safe to MS Smart Screen. Will try with WSJT-X 2.2.0-rc1 when that becomes available May 11.
Jim AF5FH


--
Dan - K4SHQ


locked Re: JTAlert 2.16.5

 

Very odd.  I never get a virus alert from the JTAlert downloads……until today.  Esets NOD32 has repeatedly given me this error:



C:\Users\k4shq\Downloads\JTAlert.2.16.5.Setup.exe » INNO » {app}\JTAlert.exe - Win32/PSW.Delf.OSF trojan - cleaned by deleting [1]

 

NOD32 is not known to be false positive prone.  My latest update was about 3 hours ago and is automatic.  Until I see something to indicate this is false, or perhaps, inexplicably there is an infection on Laurie’s website, I’m going to treat this as a valid threat.  I will also run an additional update just in case Eset made an error.

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jim AF5FH
Sent: Friday, May 8, 2020 1:16 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.5

 

[Edited Message Follows]

Same experience here, latest version works fine as before. Also reported JTAlert as safe to MS Smart Screen. Will try with WSJT-X 2.2.0-rc1 when that becomes available May 11.
Jim AF5FH


--
Dan - K4SHQ