Date   

Re: Windows 10 Automatic Update Created Issue with Serial Ports

fjk5146
 

Dave (w6de)

Thanks for the information on disabling automatic driver updates.  It is good to know that the V1909 update also caused problems on more than just my system.  I have another computer that I use to monitor and record several security cameras using BlueIris software.  The Windows 10 update deleted my current BlueIris configuration file.  When BlueIris restarted after the Windows 10 update, it fell back to an older version of the configuration file.  I spent several hours trying to figure out why several of my cameras were no longer accessible!  I ended up rebuilding the configuration.  I also saved several backup copies of the corrected configuration to locations Windows cannot access!

I had read somewhere that when this update was first pushed out last year, that some systems were  experiencing data loss.  I think they stopped rolling out the update to correct the problem.  When it showed up on my system earlier this month I didn't anticipate any problems.  I guess I was wrong! 

I've now spent a lot of time documenting the hardware information of each of the serial ports should this happen again.

Thanks again to all that provided helpful information.

--
Fred, KC9QQ


Re: "Leading! " Filter

Scott Stembaugh
 

Pete,

Any QSOs you deleted from DXKeeper you will need to manually delete from ClubLog.

73,
--scott N9LJX


On Thu, Mar 26, 2020 at 1:36 PM ve3ki <ve3iay@...> wrote:
Pete,

You don't want to prefix otherwise good log entries with !. A ! before the call sign indicates that the QSO in question is not valid for awards.

The Upload to Club Log button under the Check Progress tab automatically selects QSOs that have either never been uploaded or that have been modified since they were last uploaded. You don't need to select them manually.

73,
Rich VE3KI


On Thu, Mar 26, 2020 at 01:06 PM, Pete Smith wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: K3 and Commander

Dave AA6YQ
 

+ AA6YQ comments below

How can I get the Commander module to not check off the Interrogation square? For some reason my K3 will not work after a while with the Interrogation checked off. I have to do a reset and it will work but soon stop. My KX3 will work all the time with the box checked off. Same parameters.

+ Does "checked off" mean

1. the Interrogation box is checked

or

2. the Interrogation box is unchecked

?

73,

Dave, AA6YQ


Re: issue with MANUAL lotw upload

Dave AA6YQ
 

+ AA6YQ comments below

when LOTW was down I stopped automatically uploading , after each qso.
Club log kept working along fine.


I was able to set up the "auto loading" to LOTW after they got it fixed. I must have forgot something ,as I can no longer right click on a log entry and get the option to manually up load to lotw.

"Upload to lotw" is greyed out, while download from lotw is present/

Looks like I forgot to completely restore LOTW capabilities ??? Which box/s did I miss ????

+ On the Main window's QSL tab, are there one or more entries in the QSL Queue? If so, either finish the QSLing operation you have underway, or click the Clear button.

73,

Dave, AA6YQ


Re: Recurring issue: awards recompute slows down to a crawl

Dave AA6YQ
 

+ AA6YQ comments below

My DXKeeper awards recompute function used to be "instantaneous", but now it is very slow. Here is one data point: QSO ends 13:37:00; recompute finishes 13:40:00. While the recompute is going on, the log is inaccessible. I had this problem before and it seemed to have self-rectified after installing the latest version of all software, but now the problem is back. All the software is up to date and Windows 10 has the latest updates installed.

I don't know if this problem is related to the fact that my JTAlert automatic logging to DXKeeper stopped working after I upgraded to Windows 10 a month or so ago?

I suspect though, that Windows 10 is the culprit here, but I would not know where to start to fix these problems?

+ As a first diagnostic step, reboot Windows into "safe mode with networking", start DXKeeper, and take an action that initiates recomputation; any change in the time required?

73,

Dave, AA6YQ


K3 and Commander

NK6A <nk6a@...>
 

How can I get the Commander module to not check off the Interrogation square?  For some reason my K3 will not work after a while with the Interrogation checked off.  I have to do a reset and it will work but soon stop. My KX3 will work all the time with the box checked off.  Same parameters.

Thanks,
Don


issue with MANUAL lotw upload

bill steffey NY9H
 

when LOTW was down  I stopped automatically uploading , after each qso. Club log kept working along fine.


I was able to set up the "auto loading" to LOTW after they got it fixed.  I must have forgot something ,as I can no longer right click on a log entry and get the option to manually up load to lotw.

"Upload to lotw" is greyed out, while download from lotw is present/

Looks like I forgot to completely restore LOTW capabilities ??? Which box/s  did I miss ????


stay well all


Re: "Leading! " Filter

ve3ki
 

Pete,

You don't want to prefix otherwise good log entries with !. A ! before the call sign indicates that the QSO in question is not valid for awards.

The Upload to Club Log button under the Check Progress tab automatically selects QSOs that have either never been uploaded or that have been modified since they were last uploaded. You don't need to select them manually.

73,
Rich VE3KI


On Thu, Mar 26, 2020 at 01:06 PM, Pete Smith wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: "Leading! " Filter

W9MR Mike
 

You shouldn't need to do anything special to upload the corrected entries.

From the Check Progress tab click the upload button in the Club Log panel. This will upload any newly added or changed entries since your last Club Log upload.

If you want to filter your log display to only show those that would be upload you can filter your log using SQL.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

The Y indicates that DXKeeper knows this has been uploaded to Club Log, and the record hasn't changed since you uploaded it.
The N indicates that DX Keeper has been told to not upload this record to ClubLog, you likely don't have any of these.

Any that you have no uploaded yet should be blank, and any that you've edited since uploading should be set to M. All of these would get uploaded to Club Log if you press the upload button as described above.

Note: The above assumes that you'e configured DX Keeper with your Club Log user credentials in the QSL Config window.

73,
Mike ND9G


On Thu, Mar 26, 2020 at 12:06 PM Pete Smith <n4zr@...> wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: "Leading! " Filter

iain macdonnell - N6ML
 

On Thu, Mar 26, 2020 at 10:06 AM Pete Smith <n4zr@...> wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog. They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.
If you've configured DXKeeper for upload to Club Log [1], you'd just
need to make sure that "Club" is set to 'M' (in the Auxiliary panel)
for those QSOs, then click on "Upload" in the Club Log panel on the
Check Progress tab. Alternatively, you could right-click on each QSO
individually and select "Upload to Club Log".

73.

~iain / N6ML

[1] http://www.dxlabsuite.com/dxlabwiki/ClubLogUpload


"Leading! " Filter

Pete Smith
 

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Recurring issue: awards recompute slows down to a crawl

Jan AE7U
 

Hi Everyone:

My DXKeeper awards recompute function used to be "instantaneous", but now it is very slow.  Here is one data point: QSO ends 13:37:00; recompute finishes 13:40:00.  While the recompute is going on, the log is inaccessible.  I had this problem before and it seemed to have self-rectified after installing the latest version of all software, but now the problem is back.  All the software is up to date and Windows 10 has the latest updates installed.  

I don't know if this problem is related to the fact that my JTAlert automatic logging to DXKeeper stopped working after I upgraded to Windows 10 a month or so ago?  

I suspect though, that Windows 10 is the culprit here, but I would not know where to start to fix these problems?


Re: LoTW Callsign Certificate

neil_zampella
 

I believe the only place it needs to be updated in is TQSL.

Neil, KN3ILZ

On 3/25/2020 5:46 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I have a new updated callsign certificate but I don't see where to update it in DXLAB. Also, they offered the alternative to have
no password and I chose that option.

+ Unless you changed the callsign you're using over the air, no update in DXLab is required.

73,

Dave, AA6YQ



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


Re: Windows 10 Automatic Update Created Issue with Serial Ports

neil_zampella
 

FWIW ... also check the privacy settings for your Microphone, as it appears that M$ is trying to 'help' you by turning off stuff you turned on.   Check to make sure that WSJT-X still has access to the mic.

Neil, KN3ILZ

On 3/25/2020 2:58 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

On Wed, Mar 25, 2020 at X1:41 AM, Peter Laws wrote:

On Wed, Mar 25, 2020 at 1:38 PM Peter Laws via Groups.Io
<plaws0@...> wrote:


Dave has (somewhere) instructions on disabling automagic updates.
I'll dig for those and see if I can beat AA6YQ to it. :-) It is a
little dependent on which level of W10 you have, IIRC.
https://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown

Other stuff at https://www.dxlabsuite.com/dxlabwiki/WindowsTricks
including how to better control updates.

+ At this point, the best a Windows 10 user can do is

1. document your serial port assignments

2. configure Windows 10 to only apply updates when you direct it to do so

3. after Windows 10 completes an update, immediately check the serial port assignments, and correct any that have changed.

+ Perhaps someone with Windows device driver programming experience will create a tool that can take a named snapshot of serial port assignments, and restore serial port assignments to those specified in a named snapshot. 

          73,

                Dave, AA6YQ

 

 


Virus-free. www.avg.com


Re: Windows 10 Automatic Update Created Issue with Serial Ports

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Mar 25, 2020 at 04:38 PM, w6de wrote:

Have Windows-10 stop updating device drivers automatically.

https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10

Choose the “How to stop updates for drivers with Windows Update using Group Policy” this is a little saver than editing the registry.

Follow the directions given.

I know this works for Windows-10-Pro.  If Windows-10 for Home won’t allow you to perform this group policy change, you’ll have to use the Registry Edit procedure.

 

Make sure your USB to serial adapter is a FTDI chip based adapter.  Also down load the FTDI driver.  And, perform the Group Policy change to keep automatic updates from overloading your FTDI driver with the Microsoft generic USB driver.

 

Even if you aren’t using the USB to Serial adapters, stop the automatic driver updates

+ Thanks, Dave! That article is now accessible via


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

       73,

               Dave, AA6YQ


Re: Windows 10 Automatic Update Created Issue with Serial Ports

w6de
 

Have Windows-10 stop updating device drivers automatically.

https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10

Choose the “How to stop updates for drivers with Windows Update using Group Policy” this is a little saver than editing the registry.

Follow the directions given.

I know this works for Windows-10-Pro.  If Windows-10 for Home won’t allow you to perform this group policy change, you’ll have to use the Registry Edit procedure.

 

Make sure your USB to serial adapter is a FTDI chip based adapter.  Also down load the FTDI driver.  And, perform the Group Policy change to keep automatic updates from overloading your FTDI driver with the Microsoft generic USB driver.

 

Even if you aren’t using the USB to Serial adapters, stop the automatic driver updates.

 

Now, having said that, with my Windows-10 update to version 1909, the V-1909 update among other things un-did that Policy Change, threw away my FTDI driver, changed all the port assignments AND screwed up my default sound card assignments.

 

73,

Dave, w6de

 

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of fjk5146
Sent: 25 March, 2020 21:32
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 10 Automatic Update Created Issue with Serial Ports

 

Thanks to everyone for the helpful information.  I will see if I can do a better job of documenting the serial port information.  I may try to if I can get details at the hardware level that I can use to identify what hardware addresses are connected to each COMM port before and after an update.  Maybe that can be used to ease the remapping.


Also, thanks for the confidence in USB to RS232  adapters.  The device I had the problem with was the USB port on the Green Heron RT11 Rotor controller.  I even installed large chunks of ferrite on the cable without success. I may try using an actual USB to RS232 adapter on the Green Heron serial port to see if that works OK within some RF.  

Thanks again for all the good advice,
--
Fred, KC9QQ


Re: LoTW Callsign Certificate

Dave AA6YQ
 

+ AA6YQ comments below

I have a new updated callsign certificate but I don't see where to update it in DXLAB. Also, they offered the alternative to have
no password and I chose that option.

+ Unless you changed the callsign you're using over the air, no update in DXLab is required.

73,

Dave, AA6YQ


Re: LoTW Callsign Certificate

Bill Pence
 

Pretty certain this gets updated in the eqsl app....


On Wed, Mar 25, 2020, 5:40 PM Michael Daly <n5sj@...> wrote:

Dave,

I have a new updated callsign certificate but I don’t see where to update it in DXLAB.  Also, they offered the alternative to have no password and I chose that option.

 

Cordially,

Mike

 

Michael Daly, N5SJ

1408 Linda Drive

Gallup, NM 87301-5616

DM55pm

505 870 3430

N5sj@...

 


Re: Reduced QSL picture quality

Dave AA6YQ
 

+ AA6YQ comments below

After successfully printing almost a thousand QSLs using the DXKeeper's 'Print QSL cards' feature I'm now running into a problem of quality and its not a printer issue. When I view the background image BMP file with a photo viewing app, both large and small font text and the small logo lettering looks fine. But when I click on the "Print QSL Cards" button with the "Print preview (QSL cards)" box checked, the quality of the preview is much poorer and matches the poorer printed QSL card. I tried an older version of DXK and get the same results, poor quality preview and prints that match what the preview shows. At the top right of the preview the background image dimensions (pixels) reads 538 X 357, if that might be a clue to the poor quality preview. The background image BMP file is the same one that I've been using for over a year.

I love the idea of printing my own cards with QSO data as part of each personalized QSL, but the resolution of the smaller print and small logos on the cards printed by DXK is so poor that I can't use them.

Is there a parameter in the setup that I may be overlooking that may have been changed to cause this problem?

+ If you're saying that the quality of images printed on DXKeeper-generated QSL cards has degraded from what it was in the past, there has been no change to that functionality in DXKeeper for many years. If you specify a date on which you last generated images of acceptable quality, I can send you the then-public version of DXKeeper to test; that will reveal whether the degradation is a result of a subsequent change to DXKeeper or a change in your system.

+ Here's a QSL card that I generated from DXKeeper back in August 2011:

<http://www.dxlabsuite.com/dxkeeper/BackgroundQSL.jpg>

+ It's resolution is 504 x 313 - around 100 pixels per inch. If this is not sufficient for your purposes, your options are to

1. configure DXKeeper to generate an ADIF file from the QSL Queue, and use that to drive a more flexible QSL-generating application:

<https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20ADIF>

2. Purchase pre-printed QSL cards bearing your images, and have DXKeeper generate QSL labels that you can affix to them:

<https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20with%20Paper.

73,

Dave, AA6yQ


LoTW Callsign Certificate

Mike Daly
 

Dave,

I have a new updated callsign certificate but I don’t see where to update it in DXLAB.  Also, they offered the alternative to have no password and I chose that option.

 

Cordially,

Mike

 

Michael Daly, N5SJ

1408 Linda Drive

Gallup, NM 87301-5616

DM55pm

505 870 3430

N5sj@...

 

17401 - 17420 of 209546