Most all the stations spotted in Bandspread are spotted from foreign countries. How do I get it to show stations spotted from the USA? Tom WN0DRC

Bill, thanks for your suggestion. It looks like we got it taken care of by removing my LOTW password requirement from my TQSL Certificate as Dave, AA6YQ suggested. Otherwise, yes, I was ready to

+ AA6YQ comments below + Some questions: 1. what make and model transceiver are you using? 2. does Commander display your transceiver's frequency and mode when you make changes via the

Thank you Iain! Clearly I should have RTFM :( I guess something changed at that cluster node, maybe switched to DXSpider, I don't recall which flavour of DX Cluster node it was

I need some help... I have tried uninstalling Commander and reinstalling it. I have cleared the registry and tried again, but my DX Keeper does not fill in the frequency field automatically when

For SpotCollector to consider a DX Cluster source valid, the prompt that it returns must contain your username (as configured in the Spot Source). See

It started working again about an hour after I posted this. -- 73, Matt, N0EYE

I have just disabled all other sources and can confirm spots are not being taken from this source, here's a session print: This is the GB7MBC DXCluster system using DXSpider softwareIf you

I'll take that back, looking back at SpotCollector history I don't see any entries with that source as the "Network". -- 73 Bill G4WJS.

Hi Dave and all, my main spot source window, a DXSpider telnet cluster node (gb7mbc.spoo.org:8000), refuses to stay hidden. If I close the window and check the "Hide" option in Config it hides, but

If this only occurs for ft8 qso, then JT alerts is likely directing dxkeeper to upload each qso to lotw... This is a dxkeeper setting in jtalerts settings .. In jtalerts, Open settings -> logging

+ AA6YQ comments below I'm Larry, K0IS, from LeClaire, IA. First licensed as WN0ODK, became WA0ODK, and in 1978 passed my extra and became K0IS. Operate mostly CW, recently applied for my 5BDXCC

I’m Larry, K0IS, from LeClaire, IA. First licensed as WN0ODK, became WA0ODK, and in 1978 passed my extra and became K0IS. Operate mostly CW, recently applied for my 5BDXCC all CW and have six

FWIW .. you can do the same with JT-Alert ... just use an ADIF file. Neil, KN3ILZ This email has been checked for viruses by AVG antivirus software. www.avg.com

+ AA6YQ comments below Thanks for this suggestion. Although the "fails to launch" behavior still occurred in safe mode, the additional debug it inspired led me to the root cause: Notepad++ had taken

Hi Dave, Thanks for this suggestion. Although the "fails to launch" behavior still occurred in safe mode, the additional debug it inspired led me to the root cause: Notepad++ had taken the file

i have just uploaded to LoTW, all is OK, and i had to get a new Tqsl key last week after getting new computer on windows 10. It is working ok with me, if this info helps you to look for some other

+ AA6YQ comments below Is anyone else having issues with Keeper not being able to connect to LoTW this morning? I'm getting this message: "Attempt to connect to LoTW failed: ResponseInfo = Gopher -

+ AA6YQ comments below On my new Win10 PC with fresh installations of DXLabs and Trusted QSL, I have run into a problem where DXKeeper simply does not launch tqsl.exe for any LoTW operation.

+ AA6YQ comments below If you use GridTracker, it will log to Dxkeeper without needing to use anything else. It can also upload to many online services such as lots and hrdlog. + DXKeeper's LoTW