¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date
What is this
I just got an alert and commander is now longer working is windows confused or do I have a problem?
By Mike Kasrich · #192685 ·
Re: Commander -- Here we go again!!!
Click on Windows security, Virus and threat protection, manage settings, add or remove exclusions, then add an exclusion, folder, then select dxlab. Save settings and your troubles with false
By Jeff Griffin · #192684 ·
Re: Commander -- Here we go again!!!
+ AA6YQ comments below I just tried to upgrade Commander to the latest version and it's telling me it can't because the Commander.exe does not exist. This is after I followed the directions suggested
By Dave AA6YQ · #192683 ·
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
+ AA6YQ comments below Thank you Dave, That's very interesting. But, 1. Right now I clicked on that QSO in my LPD, and the country code says 291; also the "rx band" field (in the Aux panel) says
By Dave AA6YQ · #192682 ·
DXKeeper Question
Is there a setting in DXKeeper that it grabs name from PathFinder when I log a QSO? -- Herb Garcia, KM6JBI www.HPGPhotography.com
By Herb Garcia <hpgarcia70@...> · #192681 ·
Re: UDP Network Service
In commander, in netserv.
By NS9I · #192680 ·
Re: Commander -- Here we go again!!!
I use McAfee All is well Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 Sent: Tuesday, April 7, 2020 3:53 PM To: [email protected]<mailto:[email protected]> Subject:
By John Battin <jbattin@...> · #192679 ·
Re: Commander -- Here we go again!!!
I discovdered that Commander.exe had been renamed commander1.exe. Don Inbody Buda, TX wrote:
By Inbody, Don · #192678 ·
Re: Commander -- Here we go again!!!
Rich, You have to go into your Anti-Virus program and find the Quarantine section, Quarantine History and then see the missing file listed, then: RESTORE the file. 73, N0AN (this is for Windows
By Hasan Schiers N0AN · #192677 ·
Re: Commander -- Here we go again!!!
I finally got it going again, but Defender made it extremely difficult because its Security Center would not open after repeated tries so I could not access the Quarantined files to free them. I DID
By KY7M Lee · #192676 ·
Re: Commander -- Here we go again!!!
I just tried to upgrade Commander to the latest version and it's telling me it can't because the Commander.exe does not exist. This is after I followed the directions suggested to exclude it from
By Richard Lawn · #192675 ·
Re: Commander -- Here we go again!!!
Dave, thanks for your reply but I owe an apology to you and the group. I meant my email as a reply to a specific user, not the list. I was not prepared to jump into the fray. I¡¯m sorry.
By Fred - NA2U <cwman@...> · #192674 ·
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
Thank you Dave, That's very interesting. But, 1. Right now I clicked on that QSO in my LPD, and the country code says 291; also the "rx band" field (in the Aux panel) says "6M". This QSO was logged
By John W1JA · #192673 ·
Re: QSL labels bottom line font settings greyed out
I've sent you a new version of DXKeeper that never disables the "Bottom Line Font" panel on the "QSL Configuration" window's "QSL Labels" tab. Please let me know how it goes. 73,
By Dave AA6YQ · #192672 ·
Re: Commander -- Here we go again!!!
+ AA6YQ comments below Apparently there is a problem with Microsoft Defender. + That's correct. It's overall approach to detecting malware is
By Dave AA6YQ · #192671 ·
Re: Commander -- Here we go again!!!
For Windows Defender two things are needed and it will work fine (until it doesn't), then you have to follow the instructions below. My copy of Defender has behaved itself by and large, but I did have
By Hasan Schiers N0AN · #192670 ·
Re: Commander -- Here we go again!!!
+ AA6YQ comments below I haven¡¯t user Commander locally since I started remoting. PLUS, I now have it on my ¡°new¡± computer. Installed the update this morning and it doesn¡¯t work. Windows
By Dave AA6YQ · #192669 ·
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
Thanks for the errorlog.txt file, John. Here's the relevant fragment: 2020-04-07 16:58:11.524 > DXLogMain.ValidFields: KD2KJU 2020-04-07 16:58:11.525 > DXLogMain.ValidField: theDXCCID = 248,
By Dave AA6YQ · #192668 ·
Re: Commander -- Here we go again!!!
Apparently there is a problem with Microsoft Defender. Has the problem been reported to Microsoft? I tried to do so. Did anyone else? 73 de Knut LA9RY Den 07.04.2020 20.14, skrev Dave AA6YQ:
By Knut Meland · #192667 ·
Re: Commander -- Here we go again!!!
I haven¡¯t user Commander locally since I started remoting. PLUS, I now have it on my ¡°new¡± computer. Installed the update this morning and it doesn¡¯t work. Windows Defender asked for
By Fred - NA2U <cwman@...> · #192666 ·