Date   

locked Re: A curiosity at least

HamApps Support (VK3AMA)
 

On 14/08/2021 5:50 am, Dana Smith wrote:
So, I am running WSJTX 2.3.1, JT Alert 2.16.17 and Log4OM V2 2.16.0 and using Omnirig with an IC7410 on a Windows 10 computer. When I push Log QSO in WSJTX it used to automatically log into Log4OM Version 1. Now it won’t log into
Log4OM Version 2. (which sees the rig just fine so it recognizes the CAT op) That logging database is in the cloud as the manual suggests and all programs are seeing it and saying pass/pass when the connection is checked.

I have been through the manuals and install procedures for everything and have yet to divine why the new Log4OM isn’t automatically logged by JT Alert as things used to be.

Is there a master magician on line today who might have a clue about what the #%&&$# is going on?

Any help appreciated.
Dana   K7QH

The JTAlert help file contains instructions (with pictures) on how to correctly setup JTAlert & Log4OMV2.

A tip on logging. If you don't click the "OK" button on the WSJT-X "Log QSO" window, JTAlert will never see the logging event and will not log to LOg4OM or any of the supported loggers.

de Laurie VK3AMA


locked Re: A curiosity at least

HamApps Support (VK3AMA)
 

On 14/08/2021 6:11 am, heath calhoun - kb5vai wrote:
i get why hes using those versions tried and tested. jtalert 2.5 one bug after another.  


Thanks for your contribution.

You have exhibited the same behavior with your posting here as on the wsjtx groups.io group that got you banned there.
You are not banned here yet, but your account has now been placed under moderation.

de Laurie VK3AMA
 


locked Re: A curiosity at least

Jim Cooper
 

On 13 Aug 2021 at 15:11, heath calhoun - kb5vai wrote:

i get why hes using those versions
tried and tested. jtalert 2.5 one bug
after another. 
It's so odd that everyone else is doing quite well
with the new versions.

Keep in mind that you can always request a
FULL REFUND and use something else.

Also noted that you have not mentioned any
particular bug, or "one bug after another" ...
are you just trolling ?


locked Re: A curiosity at least

heath calhoun - kb5vai <hcalhoun@...>
 

i get why hes using those versions tried and tested. jtalert 2.5 one bug after another.  





-------- Original message --------
From: Jim Cooper <JTalert@...>
Date: 8/13/21 15:08 (GMT-06:00)
To: Dana Smith <ah6rim9@...>
Cc: Support@HamApps.groups.io
Subject: Re: [HamApps] A curiosity at least

On 13 Aug 2021 at 12:50, Dana Smith wrote:

> So, I am running WSJTX 2.3.1, JT Alert 2.16.17

Number One ...  both of those versions are
SERIOUSLY out of date ...   update your software
for both of those applications before you ask the
authors to solve problems that are probably already
solved in the new versions.

w2jc








locked Re: A curiosity at least

Michael Black
 

Read the JTAlert FAQ Log4OMV2 setup information.

Inline image



Mike W9MDB



On Friday, August 13, 2021, 02:51:04 PM CDT, Dana Smith <ah6rim9@...> wrote:


So, I am running WSJTX 2.3.1, JT Alert 2.16.17 and Log4OM V2 2.16.0 and using Omnirig with an IC7410 on a Windows 10 computer. When I push Log QSO in WSJTX it used to automatically log into Log4OM Version 1. Now it won’t log into
Log4OM Version 2. (which sees the rig just fine so it recognizes the CAT op) That logging database is in the cloud as the manual suggests and all programs are seeing it and saying pass/pass when the connection is checked.

I have been through the manuals and install procedures for everything and have yet to divine why the new Log4OM isn’t automatically logged by JT Alert as things used to be.

Is there a master magician on line today who might have a clue about what the #%&&$# is going on?

Any help appreciated.
Dana  K7QH

--
Any chance there is a version of Alert that works on a Mac or to be developed?
K7QH






locked Re: A curiosity at least

Jim Cooper
 

On 13 Aug 2021 at 12:50, Dana Smith wrote:

So, I am running WSJTX 2.3.1, JT Alert 2.16.17
Number One ... both of those versions are
SERIOUSLY out of date ... update your software
for both of those applications before you ask the
authors to solve problems that are probably already
solved in the new versions.

w2jc


locked A curiosity at least

Dana Smith
 

So, I am running WSJTX 2.3.1, JT Alert 2.16.17 and Log4OM V2 2.16.0 and using Omnirig with an IC7410 on a Windows 10 computer. When I push Log QSO in WSJTX it used to automatically log into Log4OM Version 1. Now it won’t log into
Log4OM Version 2. (which sees the rig just fine so it recognizes the CAT op) That logging database is in the cloud as the manual suggests and all programs are seeing it and saying pass/pass when the connection is checked.

I have been through the manuals and install procedures for everything and have yet to divine why the new Log4OM isn’t automatically logged by JT Alert as things used to be.

Is there a master magician on line today who might have a clue about what the #%&&$# is going on?

Any help appreciated.
Dana K7QH

--
Any chance there is a version of Alert that works on a Mac or to be developed?
K7QH


locked Re: Lost alert audio after updating to 2.50.5

Joe Subich, W4TV
 

Did you try resetting the sound card and wave files after
installing 2.50.5? Windows has a habit of changing sound
card selections and level settings when applications are
upgraded (Windows considers them "new" applications).

73,

... Joe, W4TV

On 2021-08-13 2:27 AM, Walt Flesher, W6SA wrote:
I reinstalled 2.50.4 and audio returned.
Did I overlook something?
--
*73 de W6SA
Walt Flesher
Tel: 702-568-8440
Cell: 702-523-8528
http://www.qrz.com/db/W6SA***


locked Re: JTAlert 2.50.5 is available

Hasan Schiers N0AN
 

Watch the download carefully, at the end it 'may' get trapped by your virus checker. Simply hit the 3 dots and choose "keep"....then keep anyway and it will work.. (If using Windows Defender)
73, N0AN
Hasan


On Fri, Aug 13, 2021 at 12:29 AM Radio K0HB <kzerohb@...> wrote:

 

Microsoft Defender Smartscreen will NOT allow me to install (Win 10 PRO OS)

 

73, de Hans, KØHB

“Just a Boy and his Radio”™

 

 

From: HamApps Support (VK3AMA)
Sent: Thursday, August 12, 2021 20:25
To: Support@hamapps.groups.io
Subject: [Special] [HamApps] #Announcement #NewRelease : JTAlert 2.50.5 is available

 

The latest JTAlert version 2.50.5 is now available at

https://hamapps.com/JTAlert/

 

The new installers have been examined by Microsoft and flagged as

Virus/Trojan free. The MS Defender definitions files have been updated

to exclude JTAlert 2.50.5 as a threat.

 

*** IMPORTANT *** If you use the Ignore Date setting for Worked B4

alerting the existing setting may have been reset or changed. You will

need to go into the JTAlert Settings window, "Alerts -> Worked B4"

section and ensure the Date is set per your requirements.

 

Full release notes are available at the end of this message. I strongly

encourage all users read these before installing this new JTAlert release.

 

de Laurie VK3AMA

 

Release Notes:

> 2.50.5 (2021-Aug-11)

> 

>   *** Includes Callsign database file version 2021-08-?? (2021-Aug-11)

> 

>   New:

> 

>     - Worked B4 Alert: Ignoreing the B4 status based on the age of

> QSOs in the Log.

>        Selectable in Monthly increments, 1, 2, 3, 6, 9, 12, 24 and 36

> Months. The age

>        is determinined by the utc Date when the current JTAlert

> session is started.

>        See the Alerts -> Worked B4 section of the main JTAlert window

> Settings.

> 

>     - User Defined Alert: New %JTAlert_IsFFMAGrid% environment

> variable has been

>        added for use within the Alert script/batch file. This

> environment variable will

>        indicated "Yes" or "No" if the Grid of the Alerted decode is an

> FFMA grid.

> 

>     - Activity Window: WSJTX/JTDX active Band and Mode now displayed

> in status bar.

>        Note: This is for the first JTAlert instance only (#1).

> 

>     - Activity Window: The Band matching the WSJTX/JTDX active Band

> now has a user-

>        settable colored indicator to the left of the Band title. The

> tx and rx count

>        numbers of the active Band are displayed with an increased font

> weight.

>        Note: This is for the first JTAlert instance only (#1).

> 

> 

>   Changes:

> 

>     - WSJTX/JTDX UDP Resend: If the UDP resend is enabled and the port

> is set to

>        match the WSJTX/JTDX UDP Server port, the port is reset to the

> default 2334

>        and the resend option is disabled. This is to prevent resent

> data being sent

>        back to the port that JTAlert is listening too for UDP messages

> from WSJTX/JTDX

>        and creating a feedback loop causing endless duplicated decodes

> and logging

> 

>     - Sample User Alert script: The script has been updated to use the

> CMail freeware

>        command-line SMTP mailer. CMail supports SSL/TLS connections to

> SMTP accounts

>        something that was not possible with the previously used Blat

> mailer.

> 

> 

>   Fixes:

> 

>     - Callsigns Window: Band and Mode shown in status bar not visible

> after

>        closing and reopening the window.

> 

>     - Logging: "QSO_DATE_OFF" not being sent in logging instruction

> sent to all

>        supported logs when there was not a date change during the

> length of a QSO.

>        The lastqso.adi file was also not getting this data. Note: the

> QSO End Date

>        is not sent to ACLog as it has no support for this data in its

> logging API.

> 

>     - Activity Window: Last display line, Band or Total depending on

> display

>        options not visible when window is first shown after startup

> requiring

>        a manual window resizing to bring the missing line back into view.

 

 

 

 

 

 


--

 

73, de Hans, KØHB
"Just a boy and his radio"™


locked Re: JTAlert 2.50.5 is available

neil_zampella
 

Did you try to download the latest Defender update?

Neil, KN3ILZ


locked Lost alert audio after updating to 2.50.5

Walt Flesher, W6SA
 

I reinstalled 2.50.4 and audio returned.

Did I overlook something?

--
73 de W6SA

Walt Flesher
Tel: 702-568-8440
Cell: 702-523-8528

http://www.qrz.com/db/W6SA


locked Re: JTAlert 2.50.5 is available

Radio K0HB
 

 

Microsoft Defender Smartscreen will NOT allow me to install (Win 10 PRO OS)

 

73, de Hans, KØHB

“Just a Boy and his Radio”™

 

 

From: HamApps Support (VK3AMA)
Sent: Thursday, August 12, 2021 20:25
To: Support@hamapps.groups.io
Subject: [Special] [HamApps] #Announcement #NewRelease : JTAlert 2.50.5 is available

 

The latest JTAlert version 2.50.5 is now available at

https://hamapps.com/JTAlert/

 

The new installers have been examined by Microsoft and flagged as

Virus/Trojan free. The MS Defender definitions files have been updated

to exclude JTAlert 2.50.5 as a threat.

 

*** IMPORTANT *** If you use the Ignore Date setting for Worked B4

alerting the existing setting may have been reset or changed. You will

need to go into the JTAlert Settings window, "Alerts -> Worked B4"

section and ensure the Date is set per your requirements.

 

Full release notes are available at the end of this message. I strongly

encourage all users read these before installing this new JTAlert release.

 

de Laurie VK3AMA

 

Release Notes:

> 2.50.5 (2021-Aug-11)

>   *** Includes Callsign database file version 2021-08-?? (2021-Aug-11)

>   New:

>     - Worked B4 Alert: Ignoreing the B4 status based on the age of

> QSOs in the Log.

>        Selectable in Monthly increments, 1, 2, 3, 6, 9, 12, 24 and 36

> Months. The age

>        is determinined by the utc Date when the current JTAlert

> session is started.

>        See the Alerts -> Worked B4 section of the main JTAlert window

> Settings.

>     - User Defined Alert: New %JTAlert_IsFFMAGrid% environment

> variable has been

>        added for use within the Alert script/batch file. This

> environment variable will

>        indicated "Yes" or "No" if the Grid of the Alerted decode is an

> FFMA grid.

>     - Activity Window: WSJTX/JTDX active Band and Mode now displayed

> in status bar.

>        Note: This is for the first JTAlert instance only (#1).

>     - Activity Window: The Band matching the WSJTX/JTDX active Band

> now has a user-

>        settable colored indicator to the left of the Band title. The

> tx and rx count

>        numbers of the active Band are displayed with an increased font

> weight.

>        Note: This is for the first JTAlert instance only (#1).

>   Changes:

>     - WSJTX/JTDX UDP Resend: If the UDP resend is enabled and the port

> is set to

>        match the WSJTX/JTDX UDP Server port, the port is reset to the

> default 2334

>        and the resend option is disabled. This is to prevent resent

> data being sent

>        back to the port that JTAlert is listening too for UDP messages

> from WSJTX/JTDX

>        and creating a feedback loop causing endless duplicated decodes

> and logging

>     - Sample User Alert script: The script has been updated to use the

> CMail freeware

>        command-line SMTP mailer. CMail supports SSL/TLS connections to

> SMTP accounts

>        something that was not possible with the previously used Blat

> mailer.

>   Fixes:

>     - Callsigns Window: Band and Mode shown in status bar not visible

> after

>        closing and reopening the window.

>     - Logging: "QSO_DATE_OFF" not being sent in logging instruction

> sent to all

>        supported logs when there was not a date change during the

> length of a QSO.

>        The lastqso.adi file was also not getting this data. Note: the

> QSO End Date

>        is not sent to ACLog as it has no support for this data in its

> logging API.

>     - Activity Window: Last display line, Band or Total depending on

> display

>        options not visible when window is first shown after startup

> requiring

>        a manual window resizing to bring the missing line back into view.

 

 

 

 

 

 


--

 

73, de Hans, KØHB
"Just a boy and his radio"™


locked Re: 2 meter wanted grid bug?

John P
 

DxKeeper records the propagation mode as SAT. Other choices would be things like ES, MS, ION, TR, etc. The main mode indicates the transmission type; MSK155, FT8, SSB, etc.

The satellite QSOs have SSB in the main mode and SAT in the propagation mode.
--
John P.
WA2FZW


locked Re: Error in new 2.50.5

Jamie GOLLY
 

I just downloaded 2.50.5 with no issues.

LOL, my issues on the TS 2000 was I had the radio set to sub band not main band, I felt pretty lame. But I caught it.






On Thursday, August 12, 2021, 04:50:36 PM PDT, Barry <barry@...> wrote:


Turned off AVG and installed, works, hope all is good?


locked Re: Error in new 2.50.5

Barry
 

Turned off AVG and installed, works, hope all is good?


locked Error in new 2.50.5

Barry
 

I downloaded 2.50.5 windows 64 and my AVG will not let me install, it keeps coming up saying it has a virus (IDP.Generic.a7c3e8cfc07e.3.2)


locked Re: Worked B4

HamApps Support (VK3AMA)
 

On 13/08/2021 7:15 am, Don Melcher wrote:
Can we get a 1 day setting in Worked B4 for POTA use?
--
Don
W6CZ

What about 24 hours instead?

Just joking. The problem with the B4 checks is that it is not directly tied to specific Alert types, it is a global setting, applied to all decodes and Alerts, so a one Day setting for one Alert type will not be suitable for another. I will need to think on this some more, but at this time, I don't see it getting implemented anytime soon, if ever.

Since you want a one day limit on B4 checks for your POTA chasing suggests to me that you are likely chasing individual Callsigns who are frequency activating new parks, likely on a daily or less basis. If it was me, I would be adding those activator Callsigns to the "Wanted Callsign" Alert and set that Alert to ignore the B4 status.

de Laurie VK3AMA


locked Worked B4

Don Melcher
 

Can we get a 1 day setting in Worked B4 for POTA use?
--
Don
W6CZ
DM07


locked Re: 2021-08 .NET 5.0.9 Security Update for x64 Client (KB5005419),,Download size: 52.3 MB

Bob Frostholm
 

Thank you Laurie,

Actually, I have WIN 7 Ultimate and I have the ability to view all updates in advance and deselect any I do want to install... Admittedly, I do have to remember to do this each day when new security updates arrive... leave them auto checked and manually uncheck the one(s) I don't want to install

or not install...


73

Bob

Ko6Lu
On 8/12/2021 1:51 PM, HamApps Support (VK3AMA) via groups.io wrote:

On 13/08/2021 6:41 am, Bob Frostholm wrote:
Google wants to install NET 5.0.9 Security Update for x64 on my win 7 PC

I recall there were many issues with an earlier version a couple of months ago. Before I do something stupid, I want to know if anyone else has installed this and if so, is it problem free?

-- 
73

Bob

Ko6Lu

Bob,

With most MS Security updates, they tend to be non-optional, they will eventually get installed regardless of your actions in preventing it, in my experience. The past problem you referred to was due to the NET 5.0.7 Desktop Runtime containing a defect that directly affected many applications not just JTAlert. Despite not installing that NET version it would get reapplied, typically when the Defender updates were applied, and would cause JTAlert to break again. There was no fool-proof way to force the non-install of NET 5.0.7.

After that brief history lesson, I can confirm that you should be OK with updating to .NET 5.0.9 Desktop Runtime. I am running that version here without issue.

de Laurie VK3AMA


--
Bob
KO6LU


locked Re: 2021-08 .NET 5.0.9 Security Update for x64 Client (KB5005419),,Download size: 52.3 MB

HamApps Support (VK3AMA)
 

On 13/08/2021 6:41 am, Bob Frostholm wrote:
Google wants to install NET 5.0.9 Security Update for x64 on my win 7 PC

I recall there were many issues with an earlier version a couple of months ago. Before I do something stupid, I want to know if anyone else has installed this and if so, is it problem free?

-- 
73

Bob

Ko6Lu

Bob,

With most MS Security updates, they tend to be non-optional, they will eventually get installed regardless of your actions in preventing it, in my experience. The past problem you referred to was due to the NET 5.0.7 Desktop Runtime containing a defect that directly affected many applications not just JTAlert. Despite not installing that NET version it would get reapplied, typically when the Defender updates were applied, and would cause JTAlert to break again. There was no fool-proof way to force the non-install of NET 5.0.7.

After that brief history lesson, I can confirm that you should be OK with updating to .NET 5.0.9 Desktop Runtime. I am running that version here without issue.

de Laurie VK3AMA

1241 - 1260 of 37782