Hi Laurie, thank's you for all. Its working as usual. 73 DX.

#DXLAB

Thanks, Laurie. I was off the air for so long there were no useful backups (only one and it was from today!). I started over and it looks to be working now. 73 de K2DT

#DXLAB

Well George, to answer your question. When I got my ticket in 1956, I just plain didn't know abt. GMT. And I don't believe DST was operative in Iowa at the time. In any event, I will follow whatever I

#DXLAB

+ AA6YQ comments below You need to run a JTAlert Scan Log & Rebuild with the Wanted DXCC scan QSL confirmation type(s) set per your requirements for considering a DXCC as no longer needed. Performance

#DXLAB

Thanks for the info to all who posted. Laurie, OK on how the name & QTH is pulled, definitely helps my troubleshooting! Dave, I'll follow the transfer instructions. (Probably going to uninstall everyt

#DXLAB

Jerry, Short Answer... Enable one of the JTAlert XML services. Settings window, "Web Services -> Online XML Callbooks" section. Long Answer... When the DX Call in WSJT-X changes, JTAlert will initiall

#DXLAB

Jim, Currently all decodes are sent to SpotCollector regardless of any filters set within JTAlert. Think of it as a raw data feed. Already on the todo list is to restrict the SpotCollector spots to de

#DXLAB

Walt, Don't worry. It has always been my policy that when new features are added they are optional such that they don't change existing behaviour. de Laurie VK3AMA

#DXLAB

+++ more AA6YQ comments below

#DXLAB

OM, JTAlert Settings, Miscellaneous -> Performance section and increase the QSO check time. Likely DXKeeper is being delayed in writing the QSO to its log file due to uploading the QSO to one or more

#DXLAB

There is *never* any reason to display the WSJT-X/JTAlertX data in DXKeeper's Capture window as that window is not used for logging with JT-Alert. At best Capture provides only a sub-set of the data a

#DXLAB

Neil, That last support email I got from you and your previous post to this group of an image of your Settings shows that you only had the DXKeeper lookup enabled. Your observation confirms that, as t

#DXLAB