locked Re: JT-Alert Will Not Run


Paul
 

Laurie,

 

Thank you.  The callsign entry was indeed missing in the registry.  I added it per your suggestion and JT-Alert now runs.  Thanks again.  Much appreciated.

 

73…  Paul (VE3PS)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Paul
Sent: December 3, 2019 23:40
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT-Alert Will Not Run

 

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

 

73…  Paul (VE3PS)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: December 3, 2019 23:33
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT-Alert Will Not Run

 

On 4/12/2019 2:56 pm, Paul wrote:

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

Join Support@HamApps.groups.io to automatically receive all group messages.