Date   

locked Re: Multiple operator using separate Windows user login - problems

Michael Black
 

Hi Rory,


If you're around tomorrow perhaps we can link up and take a look.

I've set up a 2nd account like that before.

What's a good time to call you and what's your #?  I'm usually available after 0800 Central time.

Mike W9MDB




On Friday, June 18, 2021, 06:39:45 PM CDT, Rory Davis, N7CR <n7cr@...> wrote:


[Edited Message Follows]

Has anyone had luck with setting up a separate Windows user account for a 2nd operator? The XYL really wants to get active on FT8 but I'm having trouble making it all work together.

Using Win4YaesuSuite, Log4OM2 with Omni-Rig, W WSJT-X and JTAlert.   

The setup still works with my Windows user account.

The first account all these apps are shut down and logged out of the account before attempting the second account.



In the second account, the sound devices do not appear in the Sound ON |  Sound Output Device > dropdown list. Nor does JTAlert appear in the Windows Volume Mixer.  Under the Manage Settings window, both the rig sound device and the speakers are available as options, so the Speakers selection is set in the Settings window. 

It appears that JTAlert is not communicating with WSJT-X either, though the settings are the same for both user accounts.

Also JTAlert and WSJT-X are not communicating with Log4OM2 but omni-rig is working OK. 

Is there another/better way to add a second operator with the above combination of software?


locked Re: JTAlert is blank #FT8

ag5pc@...
 

I changed the WSJT-X startup to include "rig-name" and everything started working. Norton is still installed and running. 


JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X - Flex60001   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe" --rig-name=Flex60001
WSJT-X   --rig-name   : Flex60001
WSJT-X Config File    : C:\Users\Al\AppData\Local\WSJT-X - Flex60001\WSJT-X - Flex60001.ini
WSJT-X Version               : 2.4.0
WSJT-X Revision              : c19d62
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                : WSJT-X - Flex60001
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : 127.0.0.1
WSJT-X UDP MCast on Loopback : True
WSJT-X UDP Max Schema        : 3
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 53280 52050
JTAlertV2.Manager.exe : 59184 59185 
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek High Definition Audio)
[2] DAX RESERVED IQ RX 1 (FlexRadio Systems DAX IQ)
[3] DAX RESERVED AUDIO RX 2 (FlexRadio Systems DAX Audio)
[4] DAX RESERVED MIC AUDIO (FlexRadio Systems DAX MIC Audio)
[5] DAX RESERVED IQ RX 4 (FlexRadio Systems DAX IQ)
[6] DAX RESERVED AUDIO RX 1 (FlexRadio Systems DAX Audio)
[7] DAX RESERVED IQ RX 2 (FlexRadio Systems DAX IQ)
[8] DAX RESERVED AUDIO RX 8 (FlexRadio Systems DAX Audio)
[9] DAX RESERVED AUDIO RX 6 (FlexRadio Systems DAX Audio)
[10] DAX RESERVED IQ RX 3 (FlexRadio Systems DAX IQ)
[11] DAX Audio TX (FlexRadio Systems DAX TX)
[12] DAX RESERVED AUDIO RX 3 (FlexRadio Systems DAX Audio)
[13] DAX RESERVED AUDIO RX 4 (FlexRadio Systems DAX Audio)
[14] DAX RESERVED AUDIO RX 7 (FlexRadio Systems DAX Audio)
[15] DAX RESERVED AUDIO RX 5 (FlexRadio Systems DAX Audio)
 
 
==================================================
JTAlertV2.Manager (2.16.17.0) status
(2021-06-19 00:47:40 utc)
--------------------------------------------------
NET Framework    : .NET Framework 4.8.4341.0
CLR Version      : 4.0.30319.42000
--------------------------------------------------
UDP Router       : Initialized * : YES (WSJT-X - Flex60001)
Audio            : Initialized * : YES (15 output devices)
BandData         : Initialized * : YES 
Text Msgs        : Initialized * : YES (started : 17)
HamSpots         : Initialized * : YES
QRZ Xml          : Initialized * : YES (AG5PC)
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 Chk      : Initialized * : YES
Maintenance      : Initialized * : YES
 


locked Re: New install

Chris Levingston
 

Hi Laurie.

I already looked for it off-screen and it does not appear in the taskbar.

The Help>About window does not work.

HOWEVER, I wondered whether the previous version of JTAlert was causing problems, so installed HRD, WSJT-X and the latest build of JTAlert on my laptop (which has never had any of them installed, and is only used for Zoom club meetings and to give me a big display on my Nano VNA) and it all works fine there.

I guess that I now need to completely uninstall the old JTAlert installation while keeping the log and settings, so open to any advice.

As always, your help is greatly appreciated - Chris


locked Multiple operator using separate Windows user login - problems

Rory Davis, N7CR
 
Edited

Has anyone had luck with setting up a separate Windows user account for a 2nd operator? The XYL really wants to get active on FT8 but I'm having trouble making it all work together.

Using Win4YaesuSuite, Log4OM2 with Omni-Rig, W WSJT-X and JTAlert.   

The setup still works with my Windows user account.

The first account all these apps are shut down and logged out of the account before attempting the second account.

In the second account, the sound devices do not appear in the Sound ON |  Sound Output Device > dropdown list. Nor does JTAlert appear in the Windows Volume Mixer.  Under the Manage Settings window, both the rig sound device and the speakers are available as options, so the Speakers selection is set in the Settings window. 

It appears that JTAlert is not communicating with WSJT-X either, though the settings are the same for both user accounts.

Also JTAlert and WSJT-X are not communicating with Log4OM2 but omni-rig is working OK. 

Is there another/better way to add a second operator with the above combination of software?


locked Re: WSJT-X Communication Problem

Wes Atchison
 

Laurie,

 

That was the problem JTA, N1MM and WSJT-X seem to be playing well together.

 

THANK YOU for your assistance.

 

73,

 

Wes

WA5TKU

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, June 17, 2021 23:32
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X Communication Problem

 

On 18/06/2021 10:33 am, Wes Atchison via groups.io wrote:

N1MM logger was the only other program I started


That will most likely be the problem. Do you have N1MM set to listen to WSJT-X? If so it would be blocking JTAlert by taking exclusive ownership of the UDP port.

N1MM does not support multicast UDP, only unicast, so it cannot operate concurrently with other apps like JTAlert that are trying to communicate with WSJT-X.

If you want both JTAlert and N1MM running concurrently, you need to enable the "Resend WSJT-X UDP packets..." setting in JTAlert, under the "Applications -> WSJT-X/JTDX" section of the Settings window and then set N1MM to listen to that port. DO NOT set that port to match WSJT-X it needs to be different.

   

de Laurie VK3AMA


Virus-free. www.avg.com


locked Re: Possible work-around for NAudio's lack of .Net 5 audio port selection

HamApps Support (VK3AMA)
 

On 18/06/2021 6:29 pm, TomK wrote:

As always, thanks for your time, Laurie. 

Even so, the Windows Advanced Audio Remapping remains a key player in my Digital Zen workflow.

It should work with any paths that go to Windows default - be they  NAudio, LaurieMagic, or lesser players 😊

I use it now to redirect most of my Digital Zen audio paths – WSJT, Motu-Mics, general web audio, etc.

I’ll happily await your next magical iteration.

TomK 73    


While Windows may offer a solution via Advanced Audio Remapping, which I have failed to find any mention of in my searches, if it requires an end user to make configuration changes to their system, that alone is enough to make it a non-starter IMO. If I can't get users to read simple release notes, getting them to make complicated (I am guessing here) configuration changes to their system would be a support nightmare.

All is not lost, earlier today a updated version of NAudio was released. That version doesn't suffer from the NET 5.0.7 induced sound playback failures. I reversed all the sound playback changes in the soon to be released JTAlert 2.50.2, bringing NAudio back into the code. A new build has been sent to the Test team. My own tests and the initial reports from the Test team all confirm that audio playback is now working correctly on systems running the latest NET 5.0.7 Desktop Runtime.

I had planned to ship JTAlert 2.50.2 on 21-June, but due to todays recoding/testing activity, I have pushed that out an extra day to 22-June.

de Laurie VK3AMA




locked Re: Possible work-around for NAudio's lack of .Net 5 audio port selection

TomK
 

As always, thanks for your time, Laurie. 

Even so, the Windows Advanced Audio Remapping remains a key player in my Digital Zen workflow.

It should work with any paths that go to Windows default - be they  NAudio, LaurieMagic, or lesser players 😊

I use it now to redirect most of my Digital Zen audio paths – WSJT, Motu-Mics, general web audio, etc.

I’ll happily await your next magical iteration.

TomK 73                

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, June 17, 2021 3:41 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Possible work-around for NAudio's lack of .Net 5 audio port selection

 

On 17/06/2021 3:33 pm, TomK wrote:

Thanks for the fast work, Laurie, with the audio workaround - not to mention all else you do!
 
Too bad NAudio doesn’t support specific device selection. Especially with multiple apps fighting over device ports.
Using only “default audio port” can be confusing as to which apps are using a specific output audio port.
 
However, it may be possible to use Windows Advanced Audio settings panel to remap to a specific port - unbeknownst to the app's own port request. 
To wit: Even if NAudio limits audio port to "Default", the Windows Advanced Audio panel can possibly remap to a specific port with its remapping feature.
I’d be happy to test the Beta in that scenario. 😊
 
Just another thought!
TomK / KT1TK / 73


Tom,

Sorry you have it wrong. NAudio does allow for playback device selection, that is one of the reasons I was using it. But it is broken with NET 5.0.7. The code introduced in 5.0.7 that triggers the NAudio issues has been reversed by the .NET devs, but it may be months before it makes it into a new NET release. As a result I have had to temporarily abandon using NAudio and rely instead on the inbuilt sound functions of WPF, which is the new code used to create JTAlert 2.50.x. It is those inbuilt sound routines that lack any ability to select an output device, all playback goes to the Windows default device.

de Laurie VK3AMA


locked Re: JTAlert is blank #FT8

HamApps Support (VK3AMA)
 

On 18/06/2021 1:49 pm, ag5pc@... wrote:
The host name is "Bugs".  

_._,_._,_



Something is not right. There is little to no network activity from JTAlert and JTAlertV2.Manager.exe in the above screen capture. Looks like they are being blocked.

On my shack PC which has no radio connected at the moment, so no incoming decodes feed, JTAlert is sitting there idle just updating the Activity window, I see greater network activity than what you show for you PC.

de Laurie VK3AMA


locked Re: JTAlert is blank #FT8

HamApps Support (VK3AMA)
 

On 18/06/2021 1:37 pm, ag5pc@... wrote:
I had suspected that Norton might be blocking something. I turned off the firewall, restarted WSJT-X and JTAlert to no avail

Pardon the pun, but Norton is notorious for being a bad PC citizen, it does not, in my experience, disable all its "Protection" functions when instructed, it is still active to some extent.

While you may have turned off the Norton firewall, that does not mean that any rules it has applied to the
Windows firewall have been turned off. They would still be active.

I know people don't like to hear it, especially when they have invested money in a product, but in my experience and many who have posted to this and other groups, Norton software is a POS!

de Laurie VK3AMA


locked Re: WSJT-X Communication Problem

HamApps Support (VK3AMA)
 

On 18/06/2021 10:33 am, Wes Atchison via groups.io wrote:
N1MM logger was the only other program I started

That will most likely be the problem. Do you have N1MM set to listen to WSJT-X? If so it would be blocking JTAlert by taking exclusive ownership of the UDP port.

N1MM does not support multicast UDP, only unicast, so it cannot operate concurrently with other apps like JTAlert that are trying to communicate with WSJT-X.

If you want both JTAlert and N1MM running concurrently, you need to enable the "Resend WSJT-X UDP packets..." setting in JTAlert, under the "Applications -> WSJT-X/JTDX" section of the Settings window and then set N1MM to listen to that port. DO NOT set that port to match WSJT-X it needs to be different.

   

de Laurie VK3AMA


locked Re: JTAlert is blank #FT8

ag5pc@...
 

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\Al\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               : 
WSJT-X Revision              : 
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                : 
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : 239.255.0.1
WSJT-X UDP MCast on Loopback : True
WSJT-X UDP Max Schema        : 
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 52625 61106
JTAlertV2.Manager.exe : 55063 55064 
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek High Definition Audio)
[2] DAX RESERVED IQ RX 1 (FlexRadio Systems DAX IQ)
[3] DAX RESERVED AUDIO RX 2 (FlexRadio Systems DAX Audio)
[4] DAX RESERVED MIC AUDIO (FlexRadio Systems DAX MIC Audio)
[5] DAX RESERVED IQ RX 4 (FlexRadio Systems DAX IQ)
[6] DAX RESERVED AUDIO RX 1 (FlexRadio Systems DAX Audio)
[7] DAX RESERVED IQ RX 2 (FlexRadio Systems DAX IQ)
[8] DAX RESERVED AUDIO RX 8 (FlexRadio Systems DAX Audio)
[9] DAX RESERVED AUDIO RX 6 (FlexRadio Systems DAX Audio)
[10] DAX RESERVED IQ RX 3 (FlexRadio Systems DAX IQ)
[11] DAX Audio TX (FlexRadio Systems DAX TX)
[12] DAX RESERVED AUDIO RX 3 (FlexRadio Systems DAX Audio)
[13] DAX RESERVED AUDIO RX 4 (FlexRadio Systems DAX Audio)
[14] DAX RESERVED AUDIO RX 7 (FlexRadio Systems DAX Audio)
[15] DAX RESERVED AUDIO RX 5 (FlexRadio Systems DAX Audio)
 
 
==================================================
JTAlertV2.Manager (2.16.17.0) status
(2021-06-18 03:50:22 utc)
--------------------------------------------------
NET Framework    : .NET Framework 4.8.4341.0
CLR Version      : 4.0.30319.42000
--------------------------------------------------
UDP Router       : Initialized * : YES (WSJT-X)
Audio            : Initialized * : YES (15 output devices)
BandData         : Initialized * : YES 
Text Msgs        : Initialized * : YES (started : 17)
HamSpots         : Initialized * : YES
QRZ Xml          : Initialized * : YES (AG5PC)
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 Chk      : Initialized * : YES
Maintenance      : Initialized * : YES


locked Re: JTAlert is blank #FT8

ag5pc@...
 

The host name is "Bugs".  


locked JTAlert is blank #FT8

ag5pc@...
 

I have WSJT-X and JTAlert configured as described in the JTAlert UDP troubleshooting page and nothing shows up in JTAlert. When I bring up the network resource monitor, JTAlert.exe and JTAlertV2.Manager are using the host name and WSJT-X is using the multicast address. I had suspected that Norton might be blocking something. I turned off the firewall, restarted WSJT-X and JTAlert to no avail. None of the applications are running with elevated privileges. 
WSJT-X 2.4.0
JTAlert 2.16.17

Interestingly enough, it worked for a while last night. Then I made the mistake of shutting down for the evening. Tonight, no JTAlert. Everything else works. You can see screenshots of my configuration in my previous post. I really like JTAlert but this is really frustrating.


locked Re: WSJT-X Communication Problem

Wes Atchison
 

Laurie,

 

Thanks for the response.

 

This is a first time install.

 

I have checked and the short cut calling WSJT-X is not run as administrator.  Did find WSJT-X had administrator turned on so I turned off.

 

The only other ap working with WSJT-X is N1MM Logger.

 

I am not using a 3rd pat yap to call WSJT-x.

 

After turning off I rebooted the PC and started WSJT and JTA but get the same error message.  N1MM logger was the only other program I started.

 

I do not know how to check if there is another program using UDP.

 

Normally I run PSK Reporter which I think uses UDP but with the last reboot it is not running,

 

What else can I check?

 

Wes

WA5TKU

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, June 17, 2021 18:48
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X Communication Problem

 

On 18/06/2021 7:35 am, Wes Atchison via groups.io wrote:

Below is my current JT Alert setup.  Getting error message saying JTA can not connect to WSJT-X.

Wes
WA


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\wa5tk\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version         : 

WSJT-X Revision        : 

WSJT-X Spec Op Mode    : None

WSJT-X UDP ID          : 

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  : 


Is this a recent problem, has JTAlert correctly previously?

That info dump tells me that JTAlert identified a running WSJT-X instance but never received any UDP traffic from it.
Some possibilities...

  1. Another application is working with WSJT-X and it is set to use unicast, not multicast UDP and has taken exclusive control of port 2237 preventing JTAlert from receiving UDP messages. Do you have any other apps working with WSJT-X? If so what are they?
  2. WSJT-X is being run with elevated privileges, set to run as administrator. The is never any normal need to do this. Check both the wsjtx.exe application file and the shortcut used to start WSJT-X to see if "Run as administrator" is checked. If that setting is set, turn it off, DON'T try and solve the problem by running JTAlert elevated.
  3. WSJT-X is being started by a third application and that application is set to "Run as administrator".

de Laurie VK3AMA


Virus-free. www.avg.com


locked Re: How to Silence Audible voiced Alert of the Called Station?

HamApps Support (VK3AMA)
 

On 18/06/2021 10:12 am, Glen Jenkins WB4KTF wrote:
How do I silence the Audible ALERT of the Station that Someone is Calling or Communicating with?
Example, in this " RA2WW WB4XXX EM10".  Say I cannot hear/or work the RA2WW station, JTAlert will Announce "DX" even though I cannot see or hear that station, so I get flooded with Audible Alerts of 'DX', 'New Continent', 'New State', etc.  I do want to get an audible alert of the calling station if it were as"  "WB4XXX RA2WW  -15" as I could possibly work the RA2WW in this instance.
Glen, WB4KTF, Austin, TX

JTAlert will only ever play audio alerts for stations that are decoded, NOT of stations being called. Only heard stations are alerted. In your example, JTAlert would never alert on RA2WW.
This is how JTAlert has always behaved.

If your getting a DX alert on a "RA2WW WB4XXX EM10" decode, it will be due to WB4XXX triggering the alert, NEVER on
RA2WW.

Putting it another way, JTAlert never Alerts on called stations only on calling stations that have been decoded.

de Laurie VK3AMA


locked How to Silence Audible voiced Alert of the Called Station?

Glen Jenkins WB4KTF
 

How do I silence the Audible ALERT of the Station that Someone is Calling or Communicating with?
Example, in this " RA2WW WB4XXX EM10".  Say I cannot hear/or work the RA2WW station, JTAlert will Announce "DX" even though I cannot see or hear that station, so I get flooded with Audible Alerts of 'DX', 'New Continent', 'New State', etc.  I do want to get an audible alert of the calling station if it were as"  "WB4XXX RA2WW  -15" as I could possibly work the RA2WW in this instance.
Glen, WB4KTF, Austin, TX


locked Re: New install

HamApps Support (VK3AMA)
 

On 18/06/2021 9:05 am, KS0JD-Jeff-913-558-0388 wrote:
I went one version back and everything seems to work now.
Thanks
Jeff

What version did you roll back to?

You never did answer the question I asked here,
Are you able to open the Help -> About window? That result would provide me with some insight as to what was happening. But that is irrelevant now as you have changed version.

de Laurie VK3AMA




locked Re: WSJT-X Communication Problem

HamApps Support (VK3AMA)
 

On 18/06/2021 7:35 am, Wes Atchison via groups.io wrote:
Below is my current JT Alert setup.  Getting error message saying JTA can not connect to WSJT-X.

Wes
WA


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\wa5tk\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 
WSJT-X Revision        : 
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : 
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  : 

Is this a recent problem, has JTAlert correctly previously?

That info dump tells me that JTAlert identified a running WSJT-X instance but never received any UDP traffic from it.
Some possibilities...
  1. Another application is working with WSJT-X and it is set to use unicast, not multicast UDP and has taken exclusive control of port 2237 preventing JTAlert from receiving UDP messages. Do you have any other apps working with WSJT-X? If so what are they?

  2. WSJT-X is being run with elevated privileges, set to run as administrator. The is never any normal need to do this. Check both the wsjtx.exe application file and the shortcut used to start WSJT-X to see if "Run as administrator" is checked. If that setting is set, turn it off, DON'T try and solve the problem by running JTAlert elevated.

  3. WSJT-X is being started by a third application and that application is set to "Run as administrator".

de Laurie VK3AMA


locked Re: New install

KS0JD-Jeff-913-558-0388
 

I went one version back and everything seems to work now.
Thanks
Jeff


locked WSJT-X Communication Problem

Wes Atchison
 

Below is my current JT Alert setup.  Getting error message saying JTA can not connect to WSJT-X.

Wes
WA


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\wa5tk\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 
WSJT-X Revision        : 
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : 
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  : 
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 63763 60838
JTAlertV2.Manager.exe : 64243 64244 64245
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (C-Media PCI Audio Device)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-06-17 21:32:04 utc)
--------------------------------------------------
CLR Version      : 5.0.7
NET Framework    : .NET 5.0.7
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (1 output devices)
BandData         : Initialized : YES (started : 58)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (WA5TKU)
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      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------
 

2241 - 2260 of 37662