Date   
Re: DXKeeper Window

Dave AA6YQ
 

The article referred to below is here:

<https://www.dxlabsuite.com/dxlabwiki/MonitorsForOldEyes>

       73,

              Dave, AA6YQ

On Fri, May 29, 2020 at 07:02 PM, Dave AA6YQ wrote:

+ Check out this article by Dave W6DE, as it does a nice job of explaining the relationship between resolution and physical size.

Re: DXKeeper Window

Dave AA6YQ
 

+ AA6YQ comments below

Well under the General Tab >>> Main "Log QSOs" options >>>

I unticked "Display panels in two columns"

I guess that will have to suffice until I get a larger Monitor???

+ You need a monitor with sufficient horizontal resolution to display the Main window's "Log QSOs" tab with the "Display panels in two columns" option enabled: at least 1024 pixels.

+ To make displayed text and images easier to read, Windows can be configured to use a lower resolution than what the monitor can display, so check the Resolution settings in the Display section of the Windows Control Panel.

+ Check out this article by Dave W6DE, as it does a nice job of explaining the relationship between resolution and physical size.

73,

Dave, AA^YQ

Re: DXKeeper Window

Rick Arzadon - N8XI
 

Well under the General Tab >>> Main "Log QSOs" options >>> 

I unticked "Display panels in two columns"

I guess that will have to suffice until I get a larger Monitor???

73, Rick - N8XI

DXKeeper Window

Rick Arzadon - N8XI
 

Because of RFI problems I removed a 19 inch LED monitor and replaced it with a 17 inch LCD monitor. 
 
In DXKeeper if I choose any of the 8 boxes to the right of the Log QSO's area (Auxilary thru User-defined)
The boxes are still visible but the Auxilary thru User-defined text can no longer be seen.
 
I can't seem to expand the right side of the window.
In fact I just tried and I cant expand nor contract  the window horizontally when one of the boxes are selected.
Vertically, no problem. 

Thanks
73, Rick - N8XI

If you are pursuing IOTA awards...

Dave AA6YQ
 

...then after upgrading to DXKeeper 15.6.0 (described below), click the Recompute button at the bottom of the Main window's "Check
Progress" tab to incorporate your LoTW confirmations into your Realtime Award Tracking for IOTA.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, May 28, 2020 10:09 PM
To: DXLab@groups.io
Subject: [DXLab] DXKeeper 15.6.0 is available

This release

- doesn't disable the "Bottom Line Font" panel on the "QSL Configuration" window's "QSL Labels" tab (tnx to Pete OH2EUU)

- prevents erroneous detection of invalid QSO items by the "Sync LoTW QSOs" function (tnx to John W1JA)

- will upload a QSO to LoTW whose RX frequency is not specified (tnx to Tony KG4TAH)

- updates the displayed TQSL version number when selecting a newly installed version of TQSL whose pathname has not changed (tnx to
Phil GU0SUP)

- if a callbook lookup for a station whose callsign ends in /am or /mm specifies a DXCC entity, leaves the QSOS's DXCC code set to 0
(tnx to Rich K1HTV)

- normalizes the tab order on the Advanced Sorts, Filters, and Modifiers window (tnx to Steve K8JQ)

- prevents an errorlog.txt file entry from being generated by DXLogModule.GetSpotDetails (tnx to Ed K2TE)

- when clearing the QSL Queue with "QSL Via" set to LoTW, doesn't change a queued QSO's LoTW_QSL_RCVD item from 'R' to blank if it's
LoTW_QSL_Sent item is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- when clearing the QSL Queue with "QSL Via" set to eQSL, doesn't change a queued QSO's eQSL_QSL_RCVD item from 'R' to blank if it's
eQSL_QSL_Sent item is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- with realtime VUCC award checking enabled, when the "Sync LoTW QSLs" or "Update from LoTW" function reports an LoTW confirmation
that does not specify a grid square on a band on which VUCC is sought, reports the logged QSO's grid square and confirmation status
(tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Overwrite Log Data with LotW data", the after action report shows each
updated item's new value, and its previously logged value (tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Display a dialog box and let operator choose", the after action report
shows each updated item's new value, and its previously logged value, as well as items whose values have been retained (tnx to Iain
N6ML)

- when reporting the results of a "Sync eQSL QSLs" or "Sync LoTW QSLs" or "Update from LoTW" function for a QSO whose QSO mode is
represented by an ADIF mode and ADIF submode, reports the QSO mode

- considers QSOs confirmed via LoTW as confirmed for IOTA (tnx to Peter N5UWY)

- adds RS-44, HO-107, and Taurus to the DefaultSatellites.txt file (tnx to Paul N8HM)

- augments the SecondarySubdivisionDatabase with new Districts defined in http://rdaward.org/press16_eng.txt (tnx to Jerry SM6BZV)

- if "Sync LoTW QSOs" or "Sync LoTW QSLs" are invoked with the Log Page Display filtered, offers a "cancel" option (tnx to Steve
K8JQ)

- includes an EntityCount.txt script (tnx to Rich K1HTV)

- updates the Configuration.htm, ConfigurationLogPageDisplay.htm, Items.htm, and Progress.htm documentation files


Notes:

1. The RDA press release in http://rdaward.org/press16_eng.txt specifies the deletion of 52 Districts, each re-assigned to another
district. The deleted Districts have not been removed from the SecondarySubdivisionDatabase, as logged QSOs likely still refer to
them. If updating those logged QSOs to reference current Districts is the appropriate course of action, a script could be developed
to accomplish that.


2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


DXKeeper 15.6.0 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ






--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: Sort log by SOTA summit ref#

Kent N6WT
 

Dave

Thanks

73
Kent
N6WT


On Fri, May 29, 2020 at 4:05 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below


On Fri, May 29, 2020 at 03:20 PM, Kent Olsen wrote:

I tried SOTA_REF='W5N*' and it did not work. I can do SOTA_REF='W5N/SM-019' and it will give me a list of the 2 qso's I have with that summit, but I want all qso's in the W5N association. What is the syntax??

+ When you want to filter the Log Page Display using a wildcard character like *, you must use the LIKE operator instead of the = operator. In this case

SOTA_REF LIKE 'W5N*'

+ No apologies necessary, Kent; we're all learning here...

         73,

                Dave, AA6YQ

Re: A Commander Slider Question ...

Dave AA6YQ
 

+ AA6YQ comments below

On Fri, May 29, 2020 at 03:07 PM, Mike Flowers wrote:

Continuing, I wondered if I could implement a slider to control the Span of the P3’s display.   This slider would have to implement the 'MN255;#SPN<D3>; command where D3 would be incremented from a low range of 000020 to an upper range of 002000 in increments of 100.  

 

The P3 Programmers Guide gives the #SPN command as:

#SPN (Span; GET/SET)

SET/RSP format: #SPNxxxxxx; where xxxxxx is 000020-002000, the span in 100-Hz units. Example:

#SPN000500; sets the span to 50 kHz.

 

Apparently, the slider function truncates leading zeros and limits the value of <D3> to three digits.

+ Correct. If I understand correctly, you should instead use <D6>

'MN255;#SPN<D6>;

      73,

             Dave, AA6YQ

Re: Sort log by SOTA summit ref#

Dave AA6YQ
 

+ AA6YQ comments below


On Fri, May 29, 2020 at 03:20 PM, Kent Olsen wrote:

I tried SOTA_REF='W5N*' and it did not work. I can do SOTA_REF='W5N/SM-019' and it will give me a list of the 2 qso's I have with that summit, but I want all qso's in the W5N association. What is the syntax??

+ When you want to filter the Log Page Display using a wildcard character like *, you must use the LIKE operator instead of the = operator. In this case

SOTA_REF LIKE 'W5N*'

+ No apologies necessary, Kent; we're all learning here...

         73,

                Dave, AA6YQ

Re: Sort log by SOTA summit ref#

Kent N6WT
 

Dave

I guess I am missing how to sort the SOTA_REF to just "W5N"? 

I tried SOTA_REF='W5N*' and it did not work. I can do SOTA_REF='W5N/SM-019' and it will give me a list of the 2 qso's I have with that summit, but I want all qso's in the W5N association. What is the syntax??

Sorry, I am not a good programmer.

Thanks
73
Kent
N6WT


On Fri, May 29, 2020 at 1:50 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I just made my 200th contact with someone on a New Mexico summit and would like to apply for the Double NM Century Award.

I would like to sort my log by SOTA summit reference #, only showing contacts starting with ref # "W5N", then sort by date. Then I would like to print a report showing these contacts. How would be the best way to do this??

+ Filter the Log Page Display to show the desired subset of QSOs. Use the Sort panel on the "Advanced Sorts, Filters, and Modifiers" window to sort by reference number and then by date. Then click the Report button above the Log Page Display on the main window's "Log QSOs" tab.

     73,

                Dave, AA6YQ




A Commander Slider Question ...

Mike Flowers
 

Hi Folks,

 

More out of curiosity than actual need, I wondered if I could use Commander sliders to send commands to the P3 Panadapter attached to my K3.

 

Sure enough, I was able to adjust the Reference Level of the P3’s display using a slider with the command:  'MN255;#REF-<D3>;

 

Continuing, I wondered if I could implement a slider to control the Span of the P3’s display.   This slider would have to implement the 'MN255;#SPN<D3>; command where D3 would be incremented from a low range of 000020 to an upper range of 002000 in increments of 100.  

 

The P3 Programmers Guide gives the #SPN command as:

#SPN (Span; GET/SET)

SET/RSP format: #SPNxxxxxx; where xxxxxx is 000020-002000, the span in 100-Hz units. Example:

#SPN000500; sets the span to 50 kHz.

 

Apparently, the slider function truncates leading zeros and limits the value of <D3> to three digits.

 

Is this a span (bridge) too far for a slider to control?

 

All suggestions – including ‘give it up’ – gratefully accepted.

 

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

 

Re: Sort log by SOTA summit ref#

Dave AA6YQ
 

+ AA6YQ comments below

I just made my 200th contact with someone on a New Mexico summit and would like to apply for the Double NM Century Award.

I would like to sort my log by SOTA summit reference #, only showing contacts starting with ref # "W5N", then sort by date. Then I would like to print a report showing these contacts. How would be the best way to do this??

+ Filter the Log Page Display to show the desired subset of QSOs. Use the Sort panel on the "Advanced Sorts, Filters, and Modifiers" window to sort by reference number and then by date. Then click the Report button above the Log Page Display on the main window's "Log QSOs" tab.

73,

Dave, AA6YQ

Re: SP Heading logged from WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

Just worked and logged a couple of Qs with WSJT-X feeding DXK. The heading logged for both Qs was for an XE2 that I had previously called a couple of days ago. (not worked anything in between). DXK ver is 15.6.0 and SC ver 8.5.5.

Is this correct behavior or do I need to correct a setting?

+ By default, DXKeeper logs the last antenna azimuth and path sent to your rotator, as reported by DXView.

+ There's a "Report computed short path heading when disabled or on an unsupported band" option on the "Rotator Control" tab of DXView's Configuration window.

73,

Dave, AA6YQ

Sort log by SOTA summit ref#

Kent N6WT
 

I just made my 200th contact with someone on a New Mexico summit and would like to apply for the Double NM Century Award. 

I would like to sort my log by SOTA summit reference #, only showing contacts starting with ref # "W5N", then sort by date. Then I would like to print a report showing these contacts. How would be the best way to do this??

I have tried a SOTA CSV Progress Report and sorted it in Excel. But I can't sort it by date that way. 

Thanks
73
Kent
N6WT

SP Heading logged from WSJT-X

Rod Greene
 

Just worked and logged a couple of Qs with WSJT-X feeding DXK. The heading logged for both Qs  was for an XE2 that I had previously called a couple of days ago. (not worked anything in between). DXK ver is 15.6.0 and SC ver 8.5.5.

Is this correct behavior or do I need to correct a setting?

Thanks and 73, Rod/w7zrc

Re: DXKeeper 15.6.0 is available

Gilbert Baron W0MN
 

Wow, almost like a whole new program here. How do you find the time. More
than 10 LOC I bet. :-}

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Thursday, May 28, 2020 21:09
To: DXLab@groups.io
Subject: [DXLab] DXKeeper 15.6.0 is available

This release

- doesn't disable the "Bottom Line Font" panel on the "QSL Configuration"
window's "QSL Labels" tab (tnx to Pete OH2EUU)

- prevents erroneous detection of invalid QSO items by the "Sync LoTW QSOs"
function (tnx to John W1JA)

- will upload a QSO to LoTW whose RX frequency is not specified (tnx to Tony
KG4TAH)

- updates the displayed TQSL version number when selecting a newly installed
version of TQSL whose pathname has not changed (tnx to Phil GU0SUP)

- if a callbook lookup for a station whose callsign ends in /am or /mm
specifies a DXCC entity, leaves the QSOS's DXCC code set to 0 (tnx to Rich
K1HTV)

- normalizes the tab order on the Advanced Sorts, Filters, and Modifiers
window (tnx to Steve K8JQ)

- prevents an errorlog.txt file entry from being generated by
DXLogModule.GetSpotDetails (tnx to Ed K2TE)

- when clearing the QSL Queue with "QSL Via" set to LoTW, doesn't change a
queued QSO's LoTW_QSL_RCVD item from 'R' to blank if it's LoTW_QSL_Sent item
is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- when clearing the QSL Queue with "QSL Via" set to eQSL, doesn't change a
queued QSO's eQSL_QSL_RCVD item from 'R' to blank if it's eQSL_QSL_Sent item
is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- with realtime VUCC award checking enabled, when the "Sync LoTW QSLs" or
"Update from LoTW" function reports an LoTW confirmation that does not
specify a grid square on a band on which VUCC is sought, reports the logged
QSO's grid square and confirmation status (tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Overwrite Log
Data with LotW data", the after action report shows each updated item's new
value, and its previously logged value (tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Display a dialog
box and let operator choose", the after action report shows each updated
item's new value, and its previously logged value, as well as items whose
values have been retained (tnx to Iain
N6ML)

- when reporting the results of a "Sync eQSL QSLs" or "Sync LoTW QSLs" or
"Update from LoTW" function for a QSO whose QSO mode is represented by an
ADIF mode and ADIF submode, reports the QSO mode

- considers QSOs confirmed via LoTW as confirmed for IOTA (tnx to Peter
N5UWY)

- adds RS-44, HO-107, and Taurus to the DefaultSatellites.txt file (tnx to
Paul N8HM)

- augments the SecondarySubdivisionDatabase with new Districts defined in
http://rdaward.org/press16_eng.txt (tnx to Jerry SM6BZV)

- if "Sync LoTW QSOs" or "Sync LoTW QSLs" are invoked with the Log Page
Display filtered, offers a "cancel" option (tnx to Steve
K8JQ)

- includes an EntityCount.txt script (tnx to Rich K1HTV)

- updates the Configuration.htm, ConfigurationLogPageDisplay.htm, Items.htm,
and Progress.htm documentation files


Notes:

1. The RDA press release in http://rdaward.org/press16_eng.txt specifies the
deletion of 52 Districts, each re-assigned to another district. The deleted
Districts have not been removed from the SecondarySubdivisionDatabase, as
logged QSOs likely still refer to them. If updating those logged QSOs to
reference current Districts is the appropriate course of action, a script
could be developed to accomplish that.


2. Update your firewall and anti-malware applications to consider this new
version of DXKeeper to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade"
section of <http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


DXKeeper 15.6.0 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ







--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

Re: Failure to Upload Qs to LOTW

Dave AA6YQ
 

+ AA6YQ comments below

I am, once again, running Update from LotW. At the current rate it is going to take way over a week to complete. Inconsistencies
not previously revealed are being found. My fault for not having performed this operation before. The problem I am facing is that
the update stops each time a inconsistency is found and and the update won't continue until I accept the LotW value. I doubt it but
is there any way to speed up this operation? Thanks.

+ You have control over the handling of inconsistencies. See the "Handling of LotW QSL Detail Inconsistencies" section of

<https://www.dxlabsuite.com/dxlabwiki/DownloadLotW>


Another major problem is that I have about 29 years-worth of Qs under my old call sign, WA0QOA. I see that then I corrected the
NA2U/7 calls it took them out of my NA2U log which was all-onclusive.

+ All of your QSOs made from the same DXCC entity should be present in the same log file. Thus when you say

"I see that then I corrected the NA2U/7 calls it took them out of my NA2U log which was all-onclusive"

+ I assume that you are referring to your ARRL DXCC Record. Your LoTW accounts for NA2U, NA2U/7, and WA0QOA should all be linked to
a single DXCC record. See the Merging and Linking sections of

<https://lotw.arrl.org/lotw-help/dxcc-setup>

73,

Dave, AA6YQ

Re: Failure to Upload Qs to LOTW

Fred - NA2U
 

I am, once again, running Update from LotW. At the current rate it is going to take way over a week to complete. Inconsistencies not previously revealed are being found. My fault for not having performed this operation before. The problem I am facing is that the update stops each time a inconsistency is found and and the update won't continue until I accept the LotW value. I doubt it but is there any way to speed up this operation? Thanks.

Another major problem is that I have about 29 years-worth of Qs under my old call sign, WA0QOA. I see that then I corrected the NA2U/7 calls it took them out of my NA2U log which was all-onclusive. Changing the Station Callsign for the WA0QOA callsign will take all of those out and my awards numbers will be all whacked. I won't be correcting those.

73 from the desert,

Fred/NA2U

---------- Original Message ----------
From: "Dave AA6YQ" <@AA6YQ>
To: <DXLab@groups.io>
Subject: Re: [DXLab] Failure to Upload Qs to LOTW
Date: Mon, 25 May 2020 17:37:58 -0400

+ AA6YQ comments below

All 43 NA2U/7 QSOs have now been accepted.

+ Those 43 QSOs were already accepted by LoTW. Your logged QSOs not marked as accepted because of the discrepancy between the
information you uploaded to LoTW and the information present in your logged QSOs. Now that you've updated our logged QSOs to specify
the correct Station Callsign, DXKeeper's automation was able to update them to reflect their acceptance.

+ I suspect that the remainder of your logged QSOs marked as "not accepted by LoTW" suffer from similar inaccuracies. You now
understand how to correct them and then update them.

73,

Dave, AA6YQ




____________________________________________________________
Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_taglines_more

George Floyd's Family Urges Calm in Minneapolis
http://thirdpartyoffers.juno.com/TGL3141/5ed07a29627297a293385st02vuc1
Boston Gives Up on This Year's Marathon
http://thirdpartyoffers.juno.com/TGL3141/5ed07a297d69d7a293385st02vuc2
Chinese Spokesman Now Has a Label on His Tweets
http://thirdpartyoffers.juno.com/TGL3141/5ed07a2997f417a293385st02vuc3

Pathfinder SM search update

Dave AA6YQ
 

The next time you start Pathfinder, you will be notified that an updated search for the Swedish online callbook is available, tnx to
Björn SM7IUN. To obtain this updated search, click the Update button that appears in the upper-left corner of Pathfinder's Main
window.

Thanks, Björn!

73,

Dave, AA6YQ

DXKeeper 15.6.0 is available

Dave AA6YQ
 

This release

- doesn't disable the "Bottom Line Font" panel on the "QSL Configuration" window's "QSL Labels" tab (tnx to Pete OH2EUU)

- prevents erroneous detection of invalid QSO items by the "Sync LoTW QSOs" function (tnx to John W1JA)

- will upload a QSO to LoTW whose RX frequency is not specified (tnx to Tony KG4TAH)

- updates the displayed TQSL version number when selecting a newly installed version of TQSL whose pathname has not changed (tnx to
Phil GU0SUP)

- if a callbook lookup for a station whose callsign ends in /am or /mm specifies a DXCC entity, leaves the QSOS's DXCC code set to 0
(tnx to Rich K1HTV)

- normalizes the tab order on the Advanced Sorts, Filters, and Modifiers window (tnx to Steve K8JQ)

- prevents an errorlog.txt file entry from being generated by DXLogModule.GetSpotDetails (tnx to Ed K2TE)

- when clearing the QSL Queue with "QSL Via" set to LoTW, doesn't change a queued QSO's LoTW_QSL_RCVD item from 'R' to blank if it's
LoTW_QSL_Sent item is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- when clearing the QSL Queue with "QSL Via" set to eQSL, doesn't change a queued QSO's eQSL_QSL_RCVD item from 'R' to blank if it's
eQSL_QSL_Sent item is set to 'U' or 'Y' (tnx to Björn SM7IUN)

- with realtime VUCC award checking enabled, when the "Sync LoTW QSLs" or "Update from LoTW" function reports an LoTW confirmation
that does not specify a grid square on a band on which VUCC is sought, reports the logged QSO's grid square and confirmation status
(tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Overwrite Log Data with LotW data", the after action report shows each
updated item's new value, and its previously logged value (tnx to Iain N6ML)

- with "Handling of LoTW QSL detail inconsistencies set to "Display a dialog box and let operator choose", the after action report
shows each updated item's new value, and its previously logged value, as well as items whose values have been retained (tnx to Iain
N6ML)

- when reporting the results of a "Sync eQSL QSLs" or "Sync LoTW QSLs" or "Update from LoTW" function for a QSO whose QSO mode is
represented by an ADIF mode and ADIF submode, reports the QSO mode

- considers QSOs confirmed via LoTW as confirmed for IOTA (tnx to Peter N5UWY)

- adds RS-44, HO-107, and Taurus to the DefaultSatellites.txt file (tnx to Paul N8HM)

- augments the SecondarySubdivisionDatabase with new Districts defined in http://rdaward.org/press16_eng.txt (tnx to Jerry SM6BZV)

- if "Sync LoTW QSOs" or "Sync LoTW QSLs" are invoked with the Log Page Display filtered, offers a "cancel" option (tnx to Steve
K8JQ)

- includes an EntityCount.txt script (tnx to Rich K1HTV)

- updates the Configuration.htm, ConfigurationLogPageDisplay.htm, Items.htm, and Progress.htm documentation files


Notes:

1. The RDA press release in http://rdaward.org/press16_eng.txt specifies the deletion of 52 Districts, each re-assigned to another
district. The deleted Districts have not been removed from the SecondarySubdivisionDatabase, as logged QSOs likely still refer to
them. If updating those logged QSOs to reference current Districts is the appropriate course of action, a script could be developed
to accomplish that.


2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


DXKeeper 15.6.0 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ

Re: Help Commander Disappeared **FIXED**

Michael Daly
 

Larry,

Thanks for posting.  It was Malwarebytes that caused trouble here too.

Mike, n5sj

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Larry Bryan
Sent: Friday, April 03, 2020 15:20
To: DXLab@groups.io
Subject: Re: [DXLab] Help Commander Disappeared **FIXED**

 

It was the Malwarebytes program that was trapping commander.exe. This did not show up when I checked prior. There was nothing showing as a threat or in the quarantine folder. However when I went into the Commander folder and renamed the last version and tried to upgrade to current, I got the detection notice that I expected to get and when checking the malware program, it showed the threat and commander.exe was quarantined. In checking the excluded folders, DXLabs was not in the list.

Not sure why, maybe an update but I put it back in exclusion and restarted DXSuite then upgraded Commander to the latest version and it's all back running. I've had other program files quarantined that I had to resolved, but none to my recollection where the program was running then it wasn't.

Posting resolution for others benefit

Larry
W8LIG