From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Thursday, 05 December 2019 12:11
To: Support <Support@hamapps.groups.io>
Subject: Re: [HamApps] Sound Not Working in 2.15.4

On December 4, 2019 at 5:08 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 5/12/2019 4:01 am, Robert T wrote:

I am using JTAlert to log my QSO's to DXLabs DXKeeper.  This functions fine.

I also have JTAlert logging all Q's to my QRZ callbook and Clublog, and HRDlog automatically.  This function used to work.  Each time I entered a qso it would update my online logs.  Today I made about 20 FT-8 contacts and none have shown up in QRZ, Clublog or HRDLog.

Anyone have a clue as to what may have happened?

JTAlert version is 2.15.3

Callsign database ver. 2019.12.02

Sound files ver. 2.5.1

Online Logbooks:

QRZ.com is checked and API Key is correct

ClubLog is checked, and Call and password are correct

HRDLog is checked, Call and password are correct.

Now what?

TU,

Bob, K2RET

Bob,

All online log uploads are handled by the JTAlertV2.Manager process, while DXK logging is handled directly from the main JTAlert process.

Do other JTAlertV2.Manager handled functions work, like Audio, Text messages and Band Activity display, or are they similarly proken?

The last time the online log uploads worked was it with JTAlert 2.15.3 or an earlier version? If it was an earlier version what version, was it prior to 2.15.1?

Please let me know the answers to the above questions.

If the uploads worked previously with 2.15.3, then I suggest as a first diagnostic step perform a PC reboot. If that doesn't correct the behavior, wait a few hours for the next JTAlert release (2.15.4).

de Laurie VK3AMA

Thanks very much Laurie.  I will definitely look into this tomorrow morning.

73…  Paul (VE3PS)

When WSJT-X is running, I then attempt to launch JT-Alert.  A small window pops up [Reading Settings Data/Standby] and after perhaps 40 seconds a second small window pops up with an error message [Missing or Invalid Callsign/Program will now exit].  The only option is to click OK, and the program does indeed close.

Any assistance would be greatly appreciated.

Thanks/73...  Paul (VE3PS)

Paul,

JTAlert will abort trying to start if it is unable to determine your Callsign as that controls which config file to load.
Either the necessary Registry entry is missing or your PC protection software is actively blocking JTAlert from reading the Registry key (which JTAlert creates and owns).

You can check the Registry by using Regedit and navigating to the "HKEY_CURRENT_USER\Software\HamApps" key and looking for the "callsign" entry.
eg.
  

If the callsign entry is present then you need to look to your PC Protection software as it is likely the culprit with some overzealous settings. Any File/Folder exceptions you have added will not prevent Registry read blocking, that will be (usually) hidden deep within the Protection software settings.

If the callsign registry entry is missing, you can add it (new string value).

Alternatively you can create a new JTAlert shortcut specifying the callsign. This is the method I use to test multiple different callsigns.
Simply copy the JTAlert shortcut you normally use, right-click that new shortcut, select "Properties" and edit the "Target" field of the "Shortcut" tab adding the following /callsign=VE3PS after the /wsjtx or /jtdx parameter.
eg.
   

de Laurie VK3AMA

For the next release, would it be possible to change the default time out for the TXT MSG window from whatever it currently is (wayyy too short) to the setting of "Stay on screen until closed"   which I think is an unticked "Auto Close" box......

I suggest this because there are lots and lots of users that I send messages to that actually have no idea that the message box even exists and they just don't get enough time to read what pops up before it vanishes.    I frequently get emails saying "how the hell did you do that"  meaning the message I sent.

Thanks for considering.
Cheers
David
VK7YUM

The default timeout is 20 seconds. I wouldn't characterize that as too short.

While I can alter the default setting to "No Auto Close" that will only affect new users with newly created config files. The default value only gets assigned when reading the setting during startup and the settings is not found (as with a new empty config file). The default is only applied once which creates the missing setting and will never be performed automatically again.

Changing any existing setting for current users is not something I do unless it is an unavoidable change due to code/functionality changes (ie is deemed mandatory).

Altering the auto-close property of the text message window for all exiting users is not an option IMO. I will however set the "No Auto Close" as the new default starting with the next JTAlert release.

de Laurie VK3AMA

When WSJT-X is running, I then attempt to launch JT-Alert.  A small window pops up [Reading Settings Data/Standby] and after perhaps 40 seconds a second small window pops up with an error message [Missing or Invalid Callsign/Program will now exit].  The only option is to click OK, and the program does indeed close.

Any assistance would be greatly appreciated.

Thanks/73...  Paul (VE3PS)

Paul,

JTAlert will abort trying to start if it is unable to determine your Callsign as that controls which config file to load.
Either the necessary Registry entry is missing or your PC protection software is actively blocking JTAlert from reading the Registry key (which JTAlert creates and owns).

You can check the Registry by using Regedit and navigating to the "HKEY_CURRENT_USER\Software\HamApps" key and looking for the "callsign" entry.
eg.
  

If the callsign entry is present then you need to look to your PC Protection software as it is likely the culprit with some overzealous settings. Any File/Folder exceptions you have added will not prevent Registry read blocking, that will be (usually) hidden deep within the Protection software settings.

If the callsign registry entry is missing, you can add it (new string value).

Alternatively you can create a new JTAlert shortcut specifying the callsign. This is the method I use to test multiple different callsigns.
Simply copy the JTAlert shortcut you normally use, right-click that new shortcut, select "Properties" and edit the "Target" field of the "Shortcut" tab adding the following /callsign=VE3PS after the /wsjtx or /jtdx parameter.
eg.
   

de Laurie VK3AMA