Date   

locked JTAlert 2.16.0 is available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

he Latest JTAlert version 2.16.0 is now available @ https://hamapps.com/JTAlert/

Please review the Release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.16.0 (05-MAR-2020)

  New Features:

    - New Alert Type: Wanted Canadian (VE) Province Alert. Full support with Province
       2 character indicator, individual voiced Province sounds, and updating of
       needed Provinces via a "Scan Log and Rebuild" or manual setting. Individual
       voiced Province alert files are included in the 2.5.2 Sound files package.

    - Clear B4 Cache Menu: A user can now force a clearing of the internal worked
       B4 cache via the "Alerts -> Clear B4 Cache" menu. Clearing the cache will force
       all new decodes to get a new B4 status via a Log lookup that is then cached.

  Changes:

    - Callsigns Cleared: Callsigns display is now automatically cleared after logging
       a new QSO. This is not optional.

    - State Dropdown: The log fields display State dropdown list now automatically
       adjusts the list of 2 character codes to show only US State (and KL7, KH6)
       or VE Province codes depending on the Country of your current QSO partners.
       The dropdown is cleared for non VE or US callsigns.

    - Wanted State Alert: US State Alerts now consider "DC" for alerting and Scanning.
       If you don't want to chase "DC" as a separate alert-able State you don't need to
       take any action. If you do want to chase "DC" then un-tick the "Consider DC as MD"
       checkbox on the Wanted States Scan Log section, then run a Scan. A voiced alert
       wave file for "District of Columbia" is included in the 2.5.2 Sound files package.

  Fix:

    - B4 indicator: Newly logged Callsigns not displaying the "B4" indicator when the
       Callsign is next decoded after logging. (2.15.11 defect)

    - Fatal Error: Line 11057 or 11247 error when the Wanted State Alert is set to use
      individual State Name announcments and the Alert is triggered. (2.15.11 defect)



locked Re: Voices not working with HamApps.Sounds 2.5.3.(en-US)

HamApps Support (VK3AMA)
 

On 7/03/2020 11:27 am, Ernie Barnhart wrote:
Downloaded new version (US) this morning before executing JTAlert 2.15.11. Old version (2.5.2) was working fine yesterday. When checking sound output with "Test Sound Output" got tones instead of voice! Saw a new grid displayed, but no sound.

This evening removed sound program with Windows 10 Control Panel and installed 2.5.2 from before. Upon executing still had only tones when using "Test Sound Output". It had voices before. Sound Output Device is Speakers / Headphones (IDT High Definition Audio CODEC). Windows 10 Sound Output says the same. Completely shutdown computer before booting and starting programs.

Tried installing 2.5.3 (UK) still only tones.

Any suggestions to get the voices back?

Thank you.
From your description it would appear that the sounds were not installed correctly and starting JTAlert will remove the sound file paths for each Alert if they are no longer valid.

Using Windows File Explorer check this directory "C:\ProgramData\HamApps\Sounds", it should contain ~88 .wav files.

If the above directory does have files, open the JTAlert Settings window and visit each Alert type and use the "Default" button to set the wav file path.

de Laurie VK3AMA


locked Voices not working with HamApps.Sounds 2.5.3.(en-US)

Ernie Barnhart
 

Downloaded new version (US) this morning before executing JTAlert 2.15.11. Old version (2.5.2) was working fine yesterday. When checking sound output with "Test Sound Output" got tones instead of voice! Saw a new grid displayed, but no sound.

This evening removed sound program with Windows 10 Control Panel and installed 2.5.2 from before. Upon executing still had only tones when using "Test Sound Output". It had voices before. Sound Output Device is Speakers / Headphones (IDT High Definition Audio CODEC). Windows 10 Sound Output says the same. Completely shutdown computer before booting and starting programs.

Tried installing 2.5.3 (UK) still only tones.

Any suggestions to get the voices back?

Thank you.


locked Re: JTALERT Logging

HamApps Support (VK3AMA)
 

On 5/03/2020 8:17 am, Bill via Groups.Io wrote:
It uploads to DXKEEPER perfectly but will not upload to QRZ or HRDLog.net.  No idea what is wrong.

73,
Bill KO4NR 
Have a look at the JTAlert Help -> About and scroll down to the "JTAlertV2.Manager status" and check that all the modules are initialized. If they are not try a JTAlert restart.

If the JTAlertV2.Manager modules for "QRZ Log" and "HRDLog Log" are correctly initialized then the problem lies elsewhere. Likely your PC protection software is blocking or interfering with the SSL connections to both services.

If you send me your session files I could tell more. Use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: JTALERT Logging

HamApps Support (VK3AMA)
 

On 5/03/2020 10:02 am, Bill via Groups.Io wrote:
Do you have to remove the dashes in the QRZ.com API Key?

My buddy is a QRZ subscriber so that isn’t the issue.

73,
Bill KO4NR 
NO, you don't need to remove the dashes. You enter the key exactly as shown on QRZ.com

de Laurie VK3AMA


locked Re: Wanted VE Province Alert

HamApps Support (VK3AMA)
 

On 7/03/2020 3:02 am, WB8ASI Herb wrote:
Hi Laurie,   I'm using 2.15.11 Beta Build 0010.  It appears that the new VE Province Alert is not using the LOTW confirmation filter.  It is showing worked, but not yet confirmed, as no longer Wanted.  Thanks. 73, Herb WB8ASI
Herb,

I'm confused by what your describing. The Alerts LoTW Filter only affects what Callsigns are displayed, it has no influence over Worked/Confirmed statuses. Please rephrase. What is not working?

I have retested and the Scan Log is correctly picking up LoTW confirmed Provinces, the Callsign QSO history is correctly showing the worked/confirmed status as is the Confirmed
Bands display which is showing confirmed correctly.

de Laurie VK3AMA



locked Re: array variable error

HamApps Support (VK3AMA)
 

On 7/03/2020 8:56 am, Joseph Hurd wrote:
Today, I downloaded and installed the latest US English and call sign databases. When a new [wanted] stae is detected, JTA shuts down and this message appears:

"Line 11247 error - array variable has incorrect number of sub scripts or sub script dimension range exceeded".

Anyone else with this problem?
See https://hamapps.groups.io/g/Support/message/28014 for the temporary fix until the next release.

de Laurie VK3AMA


locked array variable error

Joseph Hurd
 

Today, I downloaded and installed the latest US English and call sign databases. When a new [wanted] stae is detected, JTA shuts down and this message appears:

"Line 11247 error - array variable has incorrect number of sub scripts or sub script dimension range exceeded".

Anyone else with this problem?


locked Re: JTAlert 2.15.9, 2.15.10, 2.15.11 Callsign Setup Window Not Accessible on Initial Execution after Install on Win10 Laptop

Bill Franzen
 

Mike - I did try all of the off screen fixes and could not get to it at all. 

Laurie - I used the regedit approach, successfully.

Thanks for the quick response.

Bill

73 de N0NYH


On Fri, Mar 6, 2020 at 12:07 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 7/03/2020 4:58 am, HamApps Support (VK3AMA) via Groups.Io wrote:
Bill,

You have a couple of options, a command line parameter or a Registry entry.
  • Add this parameter to the command-line used to start JTAlert, /callsign=N0NYH

  • Add a Registry string (REG_SZ) under "HKEY_CURRENT_USER\Software\HamApps", with a name of "callsign" and a value of "N0NYH"

I neglected to add to the above (it has just gone 5:00am here and I'm still on my first coffee)...

The command-line parameter is a temporary fix with the parameter needed with all future shortcuts used to start JTAlert until the permanent fix is applied by creating the Registry entry.

   

de Laurie VK3AMA


locked Re: Sound files and callsign data base

WB8ASI Herb
 

Comcast/Xfinity has added new security on their routers.  You need to disable for download, then re-enable.  Here's a path to get you there.  Took me awhile to figure it out.  https://internet.xfinity.com/more/my-services/my-services-disabling  73, Herb WB8ASI

On March 6, 2020 at 1:38 PM Dave Tucker Nu4N <dwtucker19@...> wrote:

For some reason I cant dowload either of these programs. I get a response of secure connection failed.
Any help would be appreciated.
Thanks in advance. 73
--
DAVE NU4N

 


locked Sound files and callsign data base

 

For some reason I cant dowload either of these programs. I get a response of secure connection failed.
Any help would be appreciated.
Thanks in advance. 73
--
DAVE NU4N


locked Re: JTAlert 2.15.9, 2.15.10, 2.15.11 Callsign Setup Window Not Accessible on Initial Execution after Install on Win10 Laptop

HamApps Support (VK3AMA)
 

On 7/03/2020 4:58 am, HamApps Support (VK3AMA) via Groups.Io wrote:
Bill,

You have a couple of options, a command line parameter or a Registry entry.
  • Add this parameter to the command-line used to start JTAlert, /callsign=N0NYH

  • Add a Registry string (REG_SZ) under "HKEY_CURRENT_USER\Software\HamApps", with a name of "callsign" and a value of "N0NYH"

I neglected to add to the above (it has just gone 5:00am here and I'm still on my first coffee)...

The command-line parameter is a temporary fix with the parameter needed with all future shortcuts used to start JTAlert until the permanent fix is applied by creating the Registry entry.

   

de Laurie VK3AMA


locked Re: JTAlert 2.15.9, 2.15.10, 2.15.11 Callsign Setup Window Not Accessible on Initial Execution after Install on Win10 Laptop

HamApps Support (VK3AMA)
 

On 6/03/2020 11:03 pm, Bill Franzen wrote:

Good Morning. 

 

I’ve had a copy of JTAlert 2.15.9, database 2020.02.06, Sounds 2.5.1 successfully running on my Windows 10 “Shack” machine, with WSJT-X and Amateur Contact Log (ACL).

 

I am in the process of installing same stack on my laptop.  I’ve successfully installed WSJT-X, and have installed JTAlert 2.15.11.  I launch JTAlert (doesn’t matter which I start with menu bar or not), the process shows the “Reading Settings Data Standby” window.  The “Setup Callsign” window is present but not accessible either via the Windows ALT-TAB or via Task Manager’s selection on the item to move it to the foreground.  ka

I de-installed release 2.15.11, and installed 2.15.10.  Same story.  I de-installed release 2.15.10 and tried 2.15.9, same story. 

 

Then I went back to my notes and followed them exactly.  I installed JTAlert 2.15.9, then Sounds, then Database, and then launched.

 

In all cases, I can’t see the “Setup Callsign” window.  I know it’s there because I can see it from task manager (see attached png).  I just can’t get to it. 

 

I’ve done a quick search and I realize this appears to the be first time this has happened. 

 

BTW I also tried copying the HamApp AppData from the Shack machine (where things work) to the Laptop for only 2.15.9.  Still no joy.

 

I’m all out of ideas, unless there is a command line parameter invocation which accepts a call sign or there is some point of corruption in a registry entry or directory I don’t know about. 

 

At this point, I’ve de-installed JTAlert, Sounds and Database.  I have not (but will at some point) clean out the AppData HamApp directory. 

 

Any thoughts?  (I also realize this is likely a “Bill” problem; if you have any suggestions I’m happy to chase them down and report back)….

 

73

Bill

N0NYH

Bill,

You have a couple of options, a command line parameter or a Registry entry.
  • Add this parameter to the command-line used to start JTAlert, /callsign=N0NYH

  • Add a Registry string (REG_SZ) under "HKEY_CURRENT_USER\Software\HamApps", with a name of "callsign" and a value of "N0NYH"

de Laurie VK3AMA



locked Wanted VE Province Alert

WB8ASI Herb
 

Hi Laurie,   I'm using 2.15.11 Beta Build 0010.  It appears that the new VE Province Alert is not using the LOTW confirmation filter.  It is showing worked, but not yet confirmed, as no longer Wanted.  Thanks. 73, Herb WB8ASI


locked Re: Can't download JTAlert 2.15.11

Tom Gregor
 

GM de Laurie VK3AMA:

tnx for turning my attention to my AVAST installation. Yes, you were correct and I have now successfully updated to the latest version. Interestingly, I don't recall a previous issue where AVAST prevented/interfered with my ability to download a file. Live and learn...   

My thanks for all you do in providing top-notch software. Well done.

tnx es 73 de K3SSB

Tom G, Sr.


locked Re: Users with missing B4s, some questions to help isolate the cause.

Bobby Chandler
 

The B4 problem appears to have started in the 2.25.9 version. The 2.15.8 looks OK.

Bobby/N4AU


locked Re: JTAlert 2.15.9, 2.15.10, 2.15.11 Callsign Setup Window Not Accessible on Initial Execution after Install on Win10 Laptop

Michael Black
 

On Friday, March 6, 2020, 06:03:38 AM CST, Bill Franzen <wgfranzen@...> wrote:


Good Morning. 

 

I’ve had a copy of JTAlert 2.15.9, database 2020.02.06, Sounds 2.5.1 successfully running on my Windows 10 “Shack” machine, with WSJT-X and Amateur Contact Log (ACL).

 

I am in the process of installing same stack on my laptop.  I’ve successfully installed WSJT-X, and have installed JTAlert 2.15.11.  I launch JTAlert (doesn’t matter which I start with menu bar or not), the process shows the “Reading Settings Data Standby” window.  The “Setup Callsign” window is present but not accessible either via the Windows ALT-TAB or via Task Manager’s selection on the item to move it to the foreground.  ka

I de-installed release 2.15.11, and installed 2.15.10.  Same story.  I de-installed release 2.15.10 and tried 2.15.9, same story. 

 

Then I went back to my notes and followed them exactly.  I installed JTAlert 2.15.9, then Sounds, then Database, and then launched.

 

In all cases, I can’t see the “Setup Callsign” window.  I know it’s there because I can see it from task manager (see attached png).  I just can’t get to it. 

 

I’ve done a quick search and I realize this appears to the be first time this has happened. 

 

BTW I also tried copying the HamApp AppData from the Shack machine (where things work) to the Laptop for only 2.15.9.  Still no joy.

 

I’m all out of ideas, unless there is a command line parameter invocation which accepts a call sign or there is some point of corruption in a registry entry or directory I don’t know about. 

 

At this point, I’ve de-installed JTAlert, Sounds and Database.  I have not (but will at some point) clean out the AppData HamApp directory. 

 

Any thoughts?  (I also realize this is likely a “Bill” problem; if you have any suggestions I’m happy to chase them down and report back)….

 

73

Bill

N0NYH

 

 

 

 

 


locked JTAlert 2.15.9, 2.15.10, 2.15.11 Callsign Setup Window Not Accessible on Initial Execution after Install on Win10 Laptop

Bill Franzen
 

Good Morning. 

 

I’ve had a copy of JTAlert 2.15.9, database 2020.02.06, Sounds 2.5.1 successfully running on my Windows 10 “Shack” machine, with WSJT-X and Amateur Contact Log (ACL).

 

I am in the process of installing same stack on my laptop.  I’ve successfully installed WSJT-X, and have installed JTAlert 2.15.11.  I launch JTAlert (doesn’t matter which I start with menu bar or not), the process shows the “Reading Settings Data Standby” window.  The “Setup Callsign” window is present but not accessible either via the Windows ALT-TAB or via Task Manager’s selection on the item to move it to the foreground.  ka

I de-installed release 2.15.11, and installed 2.15.10.  Same story.  I de-installed release 2.15.10 and tried 2.15.9, same story. 

 

Then I went back to my notes and followed them exactly.  I installed JTAlert 2.15.9, then Sounds, then Database, and then launched.

 

In all cases, I can’t see the “Setup Callsign” window.  I know it’s there because I can see it from task manager (see attached png).  I just can’t get to it. 

 

I’ve done a quick search and I realize this appears to the be first time this has happened. 

 

BTW I also tried copying the HamApp AppData from the Shack machine (where things work) to the Laptop for only 2.15.9.  Still no joy.

 

I’m all out of ideas, unless there is a command line parameter invocation which accepts a call sign or there is some point of corruption in a registry entry or directory I don’t know about. 

 

At this point, I’ve de-installed JTAlert, Sounds and Database.  I have not (but will at some point) clean out the AppData HamApp directory. 

 

Any thoughts?  (I also realize this is likely a “Bill” problem; if you have any suggestions I’m happy to chase them down and report back)….

 

73

Bill

N0NYH

 

 

 

 

 


locked New : Sound files (2.5.3) have been updated with improved announcement sounds for non-English languages.

HamApps Support (VK3AMA)
 

The Sound files have been updated to version 2.5.3

All the non-English language files have been recreated with improved pronunciation of the alert words.
Announcements are now correct for the language. Words are spoken in the correct language rather than English words spoken with a language accent as used in 2.5.2.

For the users of US male voiced files, I was unable to get an acceptable announcement for "DX" so have used the old "DX" file from version 2.5.1.

de Laurie VK3AMA


locked Re: new callsign failure

HamApps Support (VK3AMA)
 

On 6/03/2020 6:29 pm, androman@... wrote:
Hello, I am setting up PC's for our new club vanity callsign. I installed the wsjt-x software and Jtalert.
But when I went to put in our callsign with the change callsign program it Would Not accept it.
What did I do wrong?
This happened on two different PC's.

OM,

There is no need to run the Change Callsign program when your installing JTAlert for the first time.

When you run JTAlert for the first time after a new installation, it will automatically prompt you for your Callsign.

de Laurie VK3AMA