Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
Re: UDP Network Service
toggle quoted message
Show quoted text
+ AA6YQ comments below How can I save the settings tp appear from session to session? + About which DXLab application are you inquiring? 73, Dave, AA6YQ |
Re: Commander -- Here we go again!!!
John Battin
开云体育I use McAfee???? ?All is well ? Sent from for Windows 10 ? From: Inbody, Don
Sent: Tuesday, April 7, 2020 3:53 PM To: [email protected] Subject: Re: [DXLab] Commander -- Here we go again!!! ? I discovdered that Commander.exe had been renamed commander1.exe. ? Don Inbody Buda, TX ? ? On Tue, Apr 7, 2020 at 3:49 PM Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
? |
Re: Commander -- Here we go again!!!
I discovdered that Commander.exe had been renamed commander1.exe. Don Inbody Buda, TX On Tue, Apr 7, 2020 at 3:49 PM Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
|
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 Defender) Hasan On Tue, Apr 7, 2020 at 3:42 PM Richard Lawn <rjlawn@...> wrote: 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 being quarantined by Windows Defender. Now what do I do? |
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 add specific exclusions to Defender last week for all of DXLabs and for DXLabs\Commander.? It did not help today. ? Lee, KY7M ? |
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 being quarantined by Windows Defender. Now what do I do?
-- Rick, W2JAZ |
Re: Commander -- Here we go again!!!
Fred - NA2U
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.
toggle quoted message
Show quoted text
73, Fred/NA2U On Apr 7, 2020, at 12:42 PM, Dave AA6YQ <aa6yq@...> wrote: |
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
Thank you Dave,
toggle quoted message
Show quoted text
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 to DXK from WSJT-X. I'm not surprised it contained incorrect info - I've run into that problem before. I don't understand why it is now correct in DXK. 2. Before the KD2KJU QSO I made other QSOs on 6M and 30M today. I uploaded these QSOs in very small batches to LotW, waiting a bit and then doing Sync LotW QSOs. Each time that I did this, the Aux panel appeared. These times were before the KD2KJU QSO existed. I checked these previous QSOs and they all appear correct regarding country code and rx band. I also clicked the Broke button, with a null result in the LPD. 73, John W1JA -----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave AA6YQ Sent: Tuesday, April 7, 2020 3:40 PM To: john@... Cc: [email protected] Subject: Re: [DXLab] 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, CorrectDXCCPrefix = I, DXLogMain.Fieldbox(DXCCPrefixField) = K 2020-04-07 16:58:11.525 > DXLogMain.ValidFields: not valid: DXCCID = 248 2020-04-07 16:58:11.526 > DXLogMain.ValidField: FreqRX = 50.314111, BandRX unspecified 2020-04-07 16:58:11.527 > DXLogMain.LogFrameSelect_Click, Index = 0 2020-04-07 16:58:11.527 > DXLogSetup.LogFrameVisible_Click, Index = 0, MakeVisible = True, LogFrameVisibleShift = 0 2020-04-07 16:58:11.528 > Main window height = 9525 2020-04-07 16:58:11.528 > Log grid height = 4158 2020-04-07 16:58:11.529 > DXLogMain.ValidField: enabling panel 0: BandRX error Your logged QSO with KD2KJU as its DXCC country code set to 248 (Italy) but its DXCC Prefix set to K. Also, its BandRX item is empty though its FreqRX specifies a 6m frequency. The combination of two different errors in the same QSO may be the reason that a label is not flashing to highlight what's wrong; I will investigate. 73, Dave, AA6YQ |
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 defective. <> Has the problem been reported to Microsoft? + Thousands of times (not all by me). + The correct approach to defending against malware is to make the operating system kernel secure, and provide each active process with a secure environment in which to execute. These techniques were well understood when I was studying operating system design back in 1971. For example: <> 73, Dave, AA6YQ |
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 to restore a file from quarantine on the 23rd of March. (SpotCollector) 1. In Defender,? make an exclusion for the entire DXLab folder...not a file, a folder. 2. Learn how to get a file out of Quarantine (restore). The steps required have been posted here many times. Once you have excluded DXLab apps from virus checking, all the apps will run fine, if, and only if, you RESTORE any that got quarantined earlier. Since I did that many months ago, it is fairly rare to have a DXLab file get quarantined after having excluded it in Defender, but it can happen. If it does, go into Defender's Quarantine (history) and RESTORE it. This is going to happen to nearly all anti-virus programs, not just Defender. HamApps' JTAlert has been having a very difficult time with the same issue. Again, create an exception or exclusion for the JTAlert directory and RESTORE any prior quarantined files and you should be good, until the next time this kind of thing shows up....and it will. The advantage being, you now know how to fix the problem. There are also two kinds of situations that may result in a quarantine: 1. From the the download itself. (no install yet) ??? Solution: Go to Defender quarantine and Restore the file. Then you can install it. 2. Files already installed have disappeared. Go to Defender quarantine and Restore them. As long as you have an exclusion enabled for the program directory, there will only be a few instances where you have to go back in and restore, but these days, it's important to know how to do it. (for whatever anti-virus program you are using) Bottom line: the anti-virus software is not getting any better in terms of false-positives. The only solution I have seen is to learn how to recognize when your A-V software has asserted itself, and how to use the anti-virus software you have to recover/restore the disappeared file. ...because until you find (and pay for) the perfect anti-virus program, you are going to see this issue crop up? again and again. 73, N0AN Hasan On Tue, Apr 7, 2020 at 2:20 PM Knut Meland <knut.meland@...> wrote: Apparently there is a problem with Microsoft Defender. Has the problem |
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 Defender asked for permission to allow its installation and I clicked “Allow”. Zippo. I’m stuck for now. Because of all the changes I made I’m not quite sure where to start. Fortunately, I don’t really use it. + Your actions have not reversed the damage caused by your anti-malware application. See <> 73, Dave, AA6YQ |
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, CorrectDXCCPrefix = I, DXLogMain.Fieldbox(DXCCPrefixField) = K 2020-04-07 16:58:11.525 > DXLogMain.ValidFields: not valid: DXCCID = 248 2020-04-07 16:58:11.526 > DXLogMain.ValidField: FreqRX = 50.314111, BandRX unspecified 2020-04-07 16:58:11.527 > DXLogMain.LogFrameSelect_Click, Index = 0 2020-04-07 16:58:11.527 > DXLogSetup.LogFrameVisible_Click, Index = 0, MakeVisible = True, LogFrameVisibleShift = 0 2020-04-07 16:58:11.528 > Main window height = 9525 2020-04-07 16:58:11.528 > Log grid height = 4158 2020-04-07 16:58:11.529 > DXLogMain.ValidField: enabling panel 0: BandRX error Your logged QSO with KD2KJU as its DXCC country code set to 248 (Italy) but its DXCC Prefix set to K. Also, its BandRX item is empty though its FreqRX specifies a 6m frequency. The combination of two different errors in the same QSO may be the reason that a label is not flashing to highlight what's wrong; I will investigate. 73, Dave, AA6YQ |
Re: Commander -- Here we go again!!!
Apparently there is a problem with Microsoft Defender. Has the problem been reported to Microsoft?
toggle quoted message
Show quoted text
I tried to do so. Did anyone else? 73 de Knut LA9RY Den 07.04.2020 20.14, skrev Dave AA6YQ: + AA6YQ comments below |
Re: Commander -- Here we go again!!!
Fred - NA2U
开云体育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 permission to allow its installation and I clicked “Allow”. ?Zippo. ?I’m stuck for now. ?Because of all the changes I made I’m not quite sure where to start. ?Fortunately, I don’t really use it. ?Will keep you posted.? 73, Fred/NA2U On Apr 7, 2020, at 8:54 AM, KY7M Lee <ars.ky7m@...> wrote:
|
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
Message sent!
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave AA6YQ Sent: Tuesday, April 7, 2020 2:31 PM To: [email protected] Subject: Re: [DXLab] DXKeeper: Aux panel appears after Sync LotW QSOs operation + AA6YQ comments below -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Pelham Sent: Tuesday, April 07, 2020 2:19 PM To: [email protected] Subject: [DXLab] DXKeeper: Aux panel appears after Sync LotW QSOs operation DXK 15.4.8. When I do a Sync LotW QSOs operation, and return to the Log QSOs tab, the Auxiliary panel appears. Nothing in the panel is red, or blue, or flashing. When I close the Aux panel, the DXK main window does not return to its previous size, and I must resize it manually. The issue used to occur very occasionally, maybe once in 100 operations, from the time a few years ago when I started with DXKeeper, until a few months ago when it disappeared. Starting today, I have done 5 Sync LotW QSOs operations, and it has happened every time. Since it happens every time, I captured a debug log during the 4th operation; I can send it if it would be helpful. + Please attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ |
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
+ AA6YQ comments below
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of John Pelham Sent: Tuesday, April 07, 2020 2:19 PM To: [email protected] Subject: [DXLab] DXKeeper: Aux panel appears after Sync LotW QSOs operation DXK 15.4.8. When I do a Sync LotW QSOs operation, and return to the Log QSOs tab, the Auxiliary panel appears. Nothing in the panel is red, or blue, or flashing. When I close the Aux panel, the DXK main window does not return to its previous size, and I must resize it manually. The issue used to occur very occasionally, maybe once in 100 operations, from the time a few years ago when I started with DXKeeper, until a few months ago when it disappeared. Starting today, I have done 5 Sync LotW QSOs operations, and it has happened every time. Since it happens every time, I captured a debug log during the 4th operation; I can send it if it would be helpful. + Please attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ |
Re: DXKeeper 15.4.9 is available
+ AA6YQ comments below
"- enables the "Sync LoTW QSOs", "Sync LoTW QSLs" functions to work correctly when the CTRL key is depressed after the breaking changes made by the ARRL to LoTW's lotwreport programmatic interface (tnx to Vince VA3VF)" Can you explain this a little more? Mine seems to be working fine with v15.4.8 after I did a manual date change for "Sync LoTW QSOs" and "Sync LoTW QSLs" after ARRL broke it and then later fixed it. Should you only do this if it's not working? I don't want to re-download all 307k QSO records and 176.5k QSLs if I don't have to! HI + In an effort to prevent abuse by users who continuously download all of their QSOs from LoTW, the ARRL made changes to the API that DXKeeper uses to obtain information about submitted QSOs from LoTW. In the course of making those changes, they introduced two regressions, both of which were and reported by DXLab users and corrected by LoTW Staff within 48 hours. + They also made an unannounced permanent change to the API that broke the ability of DXKeeper's "Sync LoTW QSOs" and "Sync LoTW QSLs" functions to request all accepted QSOs or all confirmed QSOs respectively by depressing the CTRL key while invoking the operation. These "request all" functions should only be used when switching to DXKeeper from another logging application that does not include LoTW status information in the ADIF file it exported. + DXKeeper 15.4.9 restores the ability to "request all" by depressing the CTRL key while invoking "Sync LoTW QSOs" or "Sync LoTW QSLs". There is no need for any current DXLab user to do this. 73, Dave, AA6YQ |
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
John -? I installed DXK 15.4.9 shortly after it became available. I am not seeing the behavior you are describing, but I don't recall seeing it in 15.4.8 either. I know that may not help you, except perhaps to remind you that 15.4.9 is available.? GL de Dave - K9FN On Tue, Apr 7, 2020 at 2:18 PM John Pelham <john@...> wrote: DXK 15.4.8. When I do a Sync LotW QSOs operation, and return to the Log QSOs tab, the Auxiliary panel appears. Nothing in the panel is red, or blue, or flashing. When I close the Aux panel, the DXK main window does not return to its previous size, and I must resize it manually. |