locked Single/double click within callsigns window not working


BOB K5HX
 

I have traced the inability of a single click within the callsign window of JTAlert to activate WSJT-x to ZoneAlarm security software.  If I shutdown ZoneAlarm all works as expected.  However, if I temporarily suspend the firewall within ZoneAlarm,  I still get no communication between WSJT-x and JTAlert which is strange.  Also,  I attempted to configure the firewall to allow inbound and outbound UDP traffic on port 2237 but wasn't sure if that was correct.  In any event it didn't solve the problem.

My JT-Alert info is as follows:

JTAlert Instance       : #1

JTAlert Start Params   : /wsjtx

WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

WSJT-X   --rig-name    : 

WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version         : 2.4.0

WSJT-X Revision        : c19d62

WSJT-X Spec Op Mode    : None

WSJT-X UDP ID          : WSJT-X

WSJT-X UDP Port        : 2237

WSJT-X UDP Server      : 239.255.0.1

WSJT-X UDP MCast on LB : True

WSJT-X UDP Max Schema  : 3

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 62399 60379

JTAlertV2.Manager.exe : 61968 61969 61970

JTAlertV2.Decodes.exe : 

 

 

==================================================

Audio output devices

--------------------------------------------------

[1] Speakers (Dell AC511 USB SoundBar)

[2] DELL U2414H (Intel(R) Display Audio)

[3] Navigator Transmit (2- USB Audio CODEC )

[4] DELL U2417H-4 (NVIDIA High Definition Audio)

 

 

==================================================

JTAlertV2.Manager (2.50.2.0) status

(2021-07-07 23:49:30 utc)

--------------------------------------------------

CLR Version       : 5.0.6

NET Framework     : .NET 5.0.6

Architecture      : x64 64bit

--------------------------------------------------

UDP Router        : Initialized : YES (WSJT-X)

Audio             : Initialized : YES (4 output devices)

Activity Service  : Initialized : YES (started : 58)

Messaging Service : Initialized : YES (started : 17)

HamSpots Service  : Initialized : YES

QRZ Xml           : Initialized : YES (K5HX)

HamQth Xml        : Initialized : YES 

QRZ Log           : Initialized : YES 

HamQth Log        : Initialized : YES 

ClubLog Log       : Initialized : YES 

Eqsl Log          : Initialized : YES 

HrdLog Log        : Initialized : YES 

DXLab DDE         : Initialized : YES

User Alert        : Initialized : YES

Updates Check     : Initialized : YES (started : 3600)

Environment Check : Initialized : YES (started : 3600)

Maintenance       : Initialized : YES (started : 3600)

--------------------------------------------------

Any suggestions are appreciated.

Bob   K5HX
 

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