Date   

locked Re: Is this a false positive?

KF1P Bob
 

I reported the same issue....it is a False Positive.....IOLO Phoenix 360 (what we use) blocks a lot of stuff....
The work-Around was to "disable" the Virus Protection for the two minutes it took to do the update...
Full System Scan says "No Problems Found" or some such thing.......after the update.....

It would be nice to name that part of the program something that HACKERS do NOT Use.....
However that is probably a very difficult or impossible task....

Anyway thank You for the GREAT Program.....

KF1P  Bob


locked Re: Virus ?

Michael Black
 

Almost every time a new version of JTAlert comes out several anti-virus vendors will false alarm on it.  
All the AV vendors have generic detectors in them that false alarm frequently.
As long as you are downloading it from hamapps.com don't worry about it.

de Mike W9MDB




On Friday, June 21, 2019, 11:22:33 AM CDT, Knud-Erik Kaadner <ke@...> wrote:


After having updated to Ver. 2.13.8. I got this message from my antivirus software:

The file C:\Programfiles(x86)\HamApps\JTAlert\JTAlert.exe is infected with
Gen:Suspicious.Cloud.1.Sv0@aKUrxSli
As a result, JTAlert has been blocked.

I therefore ran a scan and repair , and now JTAlert is running again, but I'm not quite happy about it, as I really don't now what happend.

Maybe someone can explain it ?


locked Virus ?

Knud-Erik Kaadner
 

After having updated to Ver. 2.13.8. I got this message from my antivirus software:

The file C:\Programfiles(x86)\HamApps\JTAlert\JTAlert.exe is infected with
Gen:Suspicious.Cloud.1.Sv0@aKUrxSli
As a result, JTAlert has been blocked.

I therefore ran a scan and repair , and now JTAlert is running again, but I'm not quite happy about it, as I really don't now what happend.

Maybe someone can explain it ?


locked Re: Is this a false positive?

neil_zampella
 

Actually AVG is pretty good.   The reporting feature usually gets back with an OK within 30 minutes, and this also updates the program to 'white list' the file.

 

Neil, KN3ILZ


locked Re: JT-Alert 2.13.8

DAVID MM0AMW
 

Laurie, regarding my last e-mail about wanted Continent alerting I noticed that the option of 'PLay alert when decoded callsign worked b4' in the Wanted Continents tab was unchecked and upon checking this then callsigns trigger alert correctly, whereas in vers 2.13.7 , worked B4 callsigns trigger the Continent alert even when this box is not checked so if anything 2.13.8 is acting correctly..

73
David
MM0AMW

On Friday, 21 June 2019, 03:23:24 BST, DAVID GILLIES via Groups.Io <david.gillies116@...> wrote:




Hi Laurie,

I installed 2.13.8 but now seem to have some anomaly with alerts, I noticed it on 6m where I have stations from the Caribbean set to alert me as a wanted Continent (NA) but in the latest version this does not happen.It seems to only affect worked B4 stations with new stations alerting properly. I also noticed this same behaviour on worked B4 Canadian stations but not on USA stations who triggered the Continent alert regardless of whether they had been worked B4 or not.  I reverted to 2.13.7 and everything worked as expected. I then re-installed 2.13.8 and the same problem re-occurred.

73
David
MM0AMW




locked Re: Is this a false positive?

chris g7ogx
 

OK thanks for your help. Dave.


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Dave NT9E <nt9e@...>
Sent: Friday, June 21, 2019 5:39:14 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Is this a false positive?
 

The reason you get those alerts is because most virus protection uses a list of how many people use the downloaded program. If the downloaded program does not correspond to most real word numbers (of downloads) it thinks its a virus.


Dave Whaley NT9E


On 6/20/2019 4:41 PM, Robert Lorenzini wrote:
AVG is the virus. Any thing that is not popular is a virus.

Bob - wd6dod

On 6/20/2019 1:50 PM, John Hart via Groups.Io wrote:
I got one Too from AVG = IDP.Generic.b8b6d31c2949.3.2. I submitted to AVG but no response yet.

73 John?? NA2NY










locked Re: New JTAlert 2.13.8 available

HamApps Support (VK3AMA)
 

On 20/06/2019 9:12 pm, David Gould wrote:

I have installed this new version, but now there seems to be a problem with the Decodes history window not doing any filtering.  All lines from WSJT-X band activity window are appearing in the decodes history window.

I have re-instated the log adif file, closed and restarted JTAlert, and done a scan and rebuild, but the same problem exists.

Is there something else I have missed, or is there a bug?

Can I revert to the previous version? If so how?

JTAlert V 2.13.8   Decodes history V3 0.1.9

73,

Dave G3UEG

Dave,

The Decodes History (a component of the unreleased JTAlertV3) has independent Filtering options, it does not obey the Filters applied in the main JTAlert window. You will need to set the appropriate filters in the Decodes History if you want it to match JTAlert with respect to decodes shown.

de Laurie VK3AMA


locked Re: JT-Alert 2.13.8

HamApps Support (VK3AMA)
 

On 21/06/2019 5:08 am, DAVID GILLIES via Groups.Io wrote:
I installed 2.13.8 but now seem to have some anomaly with alerts, I noticed it on 6m where I have stations from the Caribbean set to alert me as a wanted Continent (NA) but in the latest version this does not happen.It seems to only affect worked B4 stations with new stations alerting properly. I also noticed this same behaviour on worked B4 Canadian stations but not on USA stations who triggered the Continent alert regardless of whether they had been worked B4 or not.  I reverted to 2.13.7 and everything worked as expected. I then re-installed 2.13.8 and the same problem re-occurred.

73
David
MM0AMW
David,

Not sure what is happening as the B4 colouring fix introduced with 2.13.8 didn't affect alerting, just the visual display of the B4 and its color. Comparing 2.13.7 with 2.13.8 will indeed produce different results because of the fix.

The best way for me to diagnose what is happening is to examine some JTAlert debug data in association with some examples (callsigns & times) that you feel are incorrect. Please do the following...
  • Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  • Restart JTAlert.
  • Operate as normal.
  • Once you encounter a couple examples of the incorrect alerting, take note of the Callsigns and the utc times, then use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis. Include in that support request your previously noted Callsigns/Times.
  • Turn off debug recording.
de Laurie VK3AMA



locked Re: Is this a false positive?

Dave NT9E
 

The reason you get those alerts is because most virus protection uses a list of how many people use the downloaded program. If the downloaded program does not correspond to most real word numbers (of downloads) it thinks its a virus.


Dave Whaley NT9E


On 6/20/2019 4:41 PM, Robert Lorenzini wrote:
AVG is the virus. Any thing that is not popular is a virus.

Bob - wd6dod

On 6/20/2019 1:50 PM, John Hart via Groups.Io wrote:
I got one Too from AVG = IDP.Generic.b8b6d31c2949.3.2. I submitted to AVG but no response yet.

73 John?? NA2NY










locked JT-Alert 2.13.8

DAVID MM0AMW
 



Hi Laurie,

I installed 2.13.8 but now seem to have some anomaly with alerts, I noticed it on 6m where I have stations from the Caribbean set to alert me as a wanted Continent (NA) but in the latest version this does not happen.It seems to only affect worked B4 stations with new stations alerting properly. I also noticed this same behaviour on worked B4 Canadian stations but not on USA stations who triggered the Continent alert regardless of whether they had been worked B4 or not.  I reverted to 2.13.7 and everything worked as expected. I then re-installed 2.13.8 and the same problem re-occurred.

73
David
MM0AMW




locked Re: Is this a false positive?

Randy Reynard
 

I also got a warning from Avast.  Had to override it.


locked Re: Is this a false positive?

Robert Lorenzini
 

AVG is the virus. Any thing that is not popular is a virus.

Bob - wd6dod

On 6/20/2019 1:50 PM, John Hart via Groups.Io wrote:
I got one Too from AVG = IDP.Generic.b8b6d31c2949.3.2. I submitted to AVG but no response yet.

73 John?? NA2NY




locked Re: Is this a false positive?

NA2NY - John Hart
 

I got one Too from AVG = IDP.Generic.b8b6d31c2949.3.2. I submitted to AVG but no response yet.

73 John?? NA2NY


locked Re: JTAlert Settings window will not appear

Mark
 

Thank you, Laurie.

 

The keyboard trick cured the problem.

 

73,

 

Mark, K6FG

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, June 20, 2019 12:50 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert Settings window will not appear

 

On 20/06/2019 10:03 pm, Mark via Groups.Io wrote:

I installed JTAlert 2.13.8.  WSJT-X and JTAlert seem to work properly, but can’t get the JTAlert Settings window to display.  I had the same problem with earlier JTAlert versions in this Windows 10 machine.

 

When I launch settings, the taskbar shows the Red “X” with a blue star a little to the left and below the icon’s center.  When I run the cursor over that icon, I see a small image of the settings window.  I also see the window when I alt-tab to that image.

 

But I can’t get the settings window to appear on the monitor to enable me to change the settings.

 

What do you suggest is the problem and the fix?

 

Tnx & 73,

 

Mark, K6FG

Sounds like the Settings window is off screen, a common problem with Windows. Google is your friend for finding a solution.
Just one example... https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/

To avoid upsetting your other Window placements, I use the Keyboard trick (shown in that refernece) rather than the Cascade Windows technique.

de Laurie VK3AMA


locked Re: Multiple HRD Log Entries #HRD

Tom Crites
 

Under JTAlert, Settings, Logging -> Last QSO section...  I unchecked 'Enable transmission of last QSO.

And under WSJT-X, Settings, Reporting tab I don't see anything regarding Secondary UDP Server (see below).

Anyway, I made the one change above and now only get one HRD logbook entry.... but it doesn't include the 'Name'.  Previously one of the three entries include the name, and before installing JTAlert my single FT8 log entries always included the QSO Name.


locked Re: JTAlert Settings window will not appear

HamApps Support (VK3AMA)
 

On 20/06/2019 10:03 pm, Mark via Groups.Io wrote:

I installed JTAlert 2.13.8.  WSJT-X and JTAlert seem to work properly, but can’t get the JTAlert Settings window to display.  I had the same problem with earlier JTAlert versions in this Windows 10 machine.

 

When I launch settings, the taskbar shows the Red “X” with a blue star a little to the left and below the icon’s center.  When I run the cursor over that icon, I see a small image of the settings window.  I also see the window when I alt-tab to that image.

 

But I can’t get the settings window to appear on the monitor to enable me to change the settings.

 

What do you suggest is the problem and the fix?

 

Tnx & 73,

 

Mark, K6FG

Sounds like the Settings window is off screen, a common problem with Windows. Google is your friend for finding a solution.
Just one example... https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/

To avoid upsetting your other Window placements, I use the Keyboard trick (shown in that refernece) rather than the Cascade Windows technique.

de Laurie VK3AMA


locked Re: Multiple HRD Log Entries #HRD

HamApps Support (VK3AMA)
 

On 21/06/2019 2:00 am, Tom Crites wrote:
I just installed JTAlertX (v2.13.8) per a Youtube from AE4VJ (https://www.youtube.com/watch?v=QTWlFsxdEVU).  This is a very cool program! 

I'm sure this is some type of configuration issue but I am getting 3 Ham Radio Deluxe logbook entries every time I log a contact with WSJJT-X (v2.0.1).  I'm running HRD logbook version 6.5.0.207.
You need to disable the logged QSO adif broadcasts of both WSJT-X and JTAlert. Recent versions of HRD by default is now listening for these broadcasts.

Under WSJT-X, Settings, Reporting tab...

   

Under JTAlert, Settings, Logging -> Last QSO section...

   

de Laurie VK3AMA


locked Is this a false positive?

chris g7ogx
 

Sorry, I forgot to attach the message I received.Hello all, what great software we have thank you.  While trying to load the latest version 2.13.8 over 2.13.7 I received the above Virus warning from AVG.  73 Chris G7OGX


locked Is this a false positive?

chris g7ogx
 

Hello all, what great software we have thank you.  While trying to load the latest version 2.13.8 over 2.13.7 I received the above Virus warning from AVG.  73 Chris G7OGX


locked Re: Multiple HRD Log Entries #HRD

Michael Black
 

If you're not running N1MM turn that off.




On Thursday, June 20, 2019, 12:35:06 PM CDT, Tom Crites <crites57@...> wrote:


WSJT-X File/Settings/Reporting - has no "Secondary UDP Server" setting.  Under Logging, Propte me to log QSO and Clear DX call and grid after logging is checked.  Network Service 'Enable PSK Reporter spotting' is checked.  Under UDP Server, Accept UDP requests is checkedn.  And under N1MM Logger + Broadcasts, Enable logged contact ADIF broadcast is checked.

JTAlert - Rebroadcast SWJT-X UDP packets is NOT checked.

de Tom KC8SES

12761 - 12780 of 37225