+ AA6YQ comments below + Overviews and step-by-step instructions for both forms of DXLab-WSJTX inter-operation are accessible here: https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes +

Setting up SpotCollector to work with WSJTX is no different from JTAlert, both require a single item to be checked. Under SpotCollector it is a checkbox, under JTAlert it is a menu

+ AA6YQ comments below + Yes, are quite a few WAS endorsements still "on the list". However, there's been little interest expressed here, so their priority has remain low. 73,

Not "Quixote Quest" but FT8 DXCC on each HF band (80-10M). One could call that a "mini-Quixote Quest" <G>. Yes, if your JTAlert "goals" are limited to mixed mode, any band, that is the case.

@ more AA6YQ comments below + As you have things configured, the Launcher is competing with all of the other Windows startup tasks and applications for CPU and memory resources. How long does it take

About a second or less. Pete Chamalian, W1RM W1RM@...

Trying to figure how to initiate three programs at once is a tall order. Set up Commander and WSJTX and then choose a logging approach. --Configuring SpotCollector directly interfacing to WSJTX, is

+ AA6YQ comments below + Setting the "User-specified digital mode family" to FT8 will highlight any active station in an entity not yet worked/confirmed via FT8 on any band. If you're pursuing the

That's *not* the way it operates for me. SpotCollector operates like it does with any other band/mode ... If I wave confirmed an entity on *any* band in FT8 *and* have confirmed that entity on *any

+ AA6YQ comments below I prefer the WSJTX -> JTAlert -> DXKeeper approach as JTAlert provides an entirely separate filter/alerting layer. With SpotCollector one gets generic "Digital" alerts for

+ AA6YQ comments below When I log a contact from winWarbler, in psk31 mode, DXKeeper does not upload to LOTW or eQSL, even though they are checked on the WinWarbler window, and in the config for

On my new PC I have launcher set to start by putting a shortcut in the windows startup folder. When the PC boots, launcher is running in the background as I can see the process in Task Manager.

I've been using DXLab Commander with WSJT-X and GridTracker. It has worked well for me.

Depends on what else Windows is doing at the time. Look at "Startup" in Task Manager and check to see what "Services" Windows is starting (automatically) on start-up. Adobe, Google, "Anti-Malware"

Interesting ... I would have expected tQSL/DXKeeper to have complained about an invalid certificate in that case. 73, ... Joe, W4TV

I could not agree more. With Dave. Another super feature of DXLabs. Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb

How are you logging? Are you clicking the "Log" button in the QSO Info panel or are you using a script command in one of your macros? Are you using the same method for RTTY and PSK31/64/126? Are

I prefer the WSJTX -> JTAlert -> DXKeeper approach as JTAlert provides an entirely separate filter/alerting layer. With SpotCollector one gets generic "Digital" alerts for each band (if enabled) and

When I log a contact from winWarbler, in psk31 mode, DXKeeper does not upload to LOTW or eQSL, even though they are checked on the WinWarbler window, and in the config for WinWarbler. If I log a RTTY

While JT Alert works for interfacing WSJTX to DXLab; DXLab already has a direct interface to WSJTX. http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect The DXLab WIKI also has an