Date   

Re: Transfer a Workspace ...

Dave AA6YQ
 

* AA6YQ comments below

The whole point of moving the workspace from my PC to the new trustee's PC is so he can maintain the log for the club station. Do I not need to bother with the workspace part at all and just Dropbox him the database?

* The database will enable access to the log, but all of DXKeeper's other settings would have to be manually configured.


I had never looked at the files in the workspace folders before, what
with fear of black magic and all, and now I see that they are
basically just the Registry entries in plain text. Including LOTW and
TQSL credentials in plain text. :/

+ They are files with a .reg suffix. Be careful: double-clicking one of them in Windows Explorer, and its contents will be loaded into the Windows Registry.
c:/apps/DXLab/Launcher/Workspaces contains a number of directories, one for each workspace as I guess you'd expect. In each of these directories are files with the name of the various DXL modules. None of them have .reg extensions (yes, I have "hide extensions" turned off because that's weird and I'm looking at them in PowerShell in any case). All appear to *be* Registry entries, e.g.,

REGEDIT4

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper]

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper\ADIF]

et cetera so we're talking about the same items regardless of how they may be named.

* My mistake; they contain registry entries, but do not have a .reg file extension.



Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before the transfer happens?

+ I don't understand the first question. In general, to update a
+ Workspace's contents,
In the DXKeeper file (no .reg) within the Workspace directory corresponding to the club's callsign, I find my own callsign in addition to the club call.

"MarathonInformation-0"="N5UWY"
"LotWUser"="n5uwy"
"n5uwy"="[REDACTED]"

I would like to clean that up in a programmatic way since my inclination is to go to Windows Subsystem for Linux, and edit the suckers out of there with vi ... but that's probably not the best way.

* I strongly advise against directly editing the registry files. Instead,

1. Terminate all DXLab applications except the Launcher

2. Direct the Launcher to load the Workspace

3. Start DXKeeper

4. Use DXKeeper to correct the incorrect settings

5. Terminate DXKeeper

6. Direct the Launcher to save Settings to the Workspace

* Now the Workspace has been updated with your corrected settings

73,

Dave, AA6YQ


Re: PropView: No predicted Sunspot Numbers

Dave AA6YQ
 

+ AA6YQ comments below

Over the last few days, when the DXLab suite starts up, I get an error message for PropView. The error is:

No 'Predicted Sunspot Numbers' URL specified in the Configuration windows 'Prediction URLs' panel.

If I go into the configuration panel within PropView, the Prediction URL's are blank.

What are the suggested URL's to insert in the empty fields?

+ Predicted Sunspot Numbers: https://services.swpc.noaa.gov/json/solar-cycle/predicted-solar-cycle.json

+ Current solar and geomagnetic conditions: https://services.swpc.noaa.gov/text/wwv.txt

+ Predicted SFI and A-index: https://services.swpc.noaa.gov/text/45-day-ap-forecast.txt

73,

Dave, AA6YQ


Re: Broken Link-"Display callsign progress on Lookup"

Dave AA6YQ
 

+ AA6YQ comments below
Those links still don't work for me. Will a newer version of DXKeeper with new Help files/documents need to being installed before the broken links work?

+ I corrected this web page:

https://www.dxlabsuite.com/dxkeeper/Help/ViewEditLog.htm

+ To update your local copy, you can download it into DXKeeper's Help folder, replacing the existing ViewEditLog.htm file. Your local copy will be automatically updated by the next version of DXKeeper.

       73,

             Dave, AA6YQ


 


Re: Broken Link-"Display callsign progress on Lookup"

Jim McPhee
 

Hi Dave,

Those links still don't work for me. Will a newer version of DXKeeper with new Help files/documents need to being installed before the broken links work?
--
Jim McPhee
Placitas, NM
W5ABA


Re: Transfer a Workspace ...

Peter Laws / N5UWY
 

On Mon, Jul 19, 2021 at 5:10 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ The Launcher's Workspaces window displays the Workspaces present in the current Workspaces folder (which defaults to the Launcher's Workspaces folder). If you move a new folder into the current Workspaces folder while the Launcher is running, terminate and restart the Launcher; the new folder should now be present on the Launcher's Workspaces window.

Cool!


2) Move the DXKeeper MDB with the club log before or after the workspace shenanigans?

+ I don't understand the question. Please elaborate.
The whole point of moving the workspace from my PC to the new
trustee's PC is so he can maintain the log for the club station. Do I
not need to bother with the workspace part at all and just Dropbox him
the database? 'Cause that makes the rest of this moot. :-)




I had never looked at the files in the workspace folders before, what with fear of black magic and all, and now I see that they are basically just the Registry entries in plain text. Including LOTW and TQSL credentials in plain text. :/

+ They are files with a .reg suffix. Be careful: double-clicking one of them in Windows Explorer, and its contents will be loaded into the Windows Registry.
c:/apps/DXLab/Launcher/Workspaces contains a number of directories,
one for each workspace as I guess you'd expect. In each of these
directories are files with the name of the various DXL modules. None
of them have .reg extensions (yes, I have "hide extensions" turned off
because that's weird and I'm looking at them in PowerShell in any
case). All appear to *be* Registry entries, e.g.,

REGEDIT4

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper]

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper\ADIF]

et cetera so we're talking about the same items regardless of how they
may be named.



Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before the transfer happens?

+ I don't understand the first question. In general, to update a Workspace's contents,
In the DXKeeper file (no .reg) within the Workspace directory
corresponding to the club's callsign, I find my own callsign in
addition to the club call.

"MarathonInformation-0"="N5UWY"
"LotWUser"="n5uwy"
"n5uwy"="[REDACTED]"

I would like to clean that up in a programmatic way since my
inclination is to go to Windows Subsystem for Linux, and edit the
suckers out of there with vi ... but that's probably not the best way.

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


PropView: No predicted Sunspot Numbers

RIchard Thorne
 

Over the last few days, when the DXLab suite starts up, I get an error message for PropView. The error is:

No 'Predicted Sunspot Numbers' URL specified in the Configuration windows 'Prediction URLs' panel.

If I go into the configuration panel within PropView, the Prediction URL's are blank.

What are the suggested URL's to insert in the empty fields?

Rich - N5ZC


Re: Transfer a Workspace ...

Dave AA6YQ
 

+ AA6YQ comments below

I meant zip, of course. So 1) will Launcher just see the new directory and "do the right thing", or will he need to set up the workspace before we put the directory there?

+ The Launcher's Workspaces window displays the Workspaces present in the current Workspaces folder (which defaults to the Launcher's Workspaces folder). If you move a new folder into the current Workspaces folder while the Launcher is running, terminate and restart the Launcher; the new folder should now be present on the Launcher's Workspaces window.

2) Move the DXKeeper MDB with the club log before or after the workspace shenanigans?

+ I don't understand the question. Please elaborate.


I had never looked at the files in the workspace folders before, what with fear of black magic and all, and now I see that they are basically just the Registry entries in plain text. Including LOTW and TQSL credentials in plain text. :/

+ They are files with a .reg suffix. Be careful: double-clicking one of them in Windows Explorer, and its contents will be loaded into the Windows Registry.


Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before the transfer happens?

+ I don't understand the first question. In general, to update a Workspace's contents,

1. terminate all DXLab applications except the Launcher

2. make a backup copy of the Workspace folder whose settings you wish to update

3. on the Launcher's Workspaces Window,

3a. select the Workspace whose settings you wish to update

3b. direct the Launcher to load settings from the selected Workspace

3c. start the DXLab applications)whose setting you wish update, use those applications to update the settings as desired, and then terminate those DXLab applications

3d. direct the Launcher to save settings to the selected Workspace

73,

Dave, AA6YQ


Re: Transfer a Workspace ...

Peter Laws / N5UWY
 

On Mon, Jul 19, 2021 at 4:20 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

Is there a how-to for moving a workspace from one system to another?

+ A Workspace is simply a folder containing one file for each DXLab application. It can be copied from one Windows system to another like any other folder.

I'm going to assume it's something along the lines of "switch to that ws, save all the settings, switch out, then tar up the directory in c:/apps/DXLab/Launcher/Workspace" ... Untarring it on his system is great but how do we get Launcher to see it?

+ On the destination system, put the Workspace (folder) in the Launcher's Workspaces folder. The Launcher can reference a Workspace located anywhere on a computer's file system, but it's best to maintain them in one place: the Launcher's Workspaces folder.
I meant zip, of course. So 1) will Launcher just see the new
directory and "do the right thing", or will he need to set up the
workspace before we put the directory there? 2) Move the DXKeeper MDB
with the club log before or after the workspace shenanigans?

I had never looked at the files in the workspace folders before, what
with fear of black magic and all, and now I see that they are
basically just the Registry entries in plain text. Including LOTW and
TQSL credentials in plain text. :/

Looking at the club DXKeeper stuff in the club workspace, I see my own
LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before
the transfer happens?


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Transfer a Workspace ...

Dave AA6YQ
 

+ AA6YQ comments below

I have a workspace (and log and TQSL certs) for a club's call. As soon as I get the paperwork done, I will no longer legally be trustee for the call or hold the repeater coordinations - yay me!

I need to move the log to the new trustee's system. We expect to do this by Zoom and Dropbox because it's 2021 and there is no need to be within 2 m of other humans (we're both vaxxed, but still - Oklahoma's 7-day rolling average was down to about 100 new cases/day around Memorial Day ... now at 500/day ... and climbing).

The new trustee uses DXLab -- I helped him with his own TQSL setup within it -- but I'm not sure he has any workspaces configured. Does a new install set one up or is the default to not set one up?

+ You must create and populate the Workspace, as described in the article you cite below.

It's been so long since I first installed the Suite, I don't remember! If
he doesn't have a workspace, I plan to send him to https://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace and https://www.dxlabsuite.com/Launcher/Help/RegistrySettings.htm so he has one for his own call.

Is there a how-to for moving a workspace from one system to another?

+ A Workspace is simply a folder containing one file for each DXLab application. It can be copied from one Windows system to another like any other folder.

I'm going to assume it's something along the lines of "switch to that ws, save all the settings, switch out, then tar up the directory in c:/apps/DXLab/Launcher/Workspace" ... Untarring it on his system is great but how do we get Launcher to see it?

+ On the destination system, put the Workspace (folder) in the Launcher's Workspaces folder. The Launcher can reference a Workspace located anywhere on a computer's file system, but it's best to maintain them in one place: the Launcher's Workspaces folder.

73,

Dave, AA6YQ


Re: VUCC report query

Dave AA6YQ
 

+ AA6YQ comments below

Simply because my compromise antenna seems to be doing better than expected, mainly because of the improving conditions on 6m, I am starting to chase DXCC, and also keeping an eye on my VUCC total on LoTW.

Currently, LoTW shows that I have 200 grids confirmed on 6m.
However, when I check the VUCC report in DXKeeper, it says 214 worked and 186 confirmed.

Looking at the report, there are quite a few that show MISSING under the LoTW Confirm heading, but are confirmed on LoTW and show up in my VUCC total.

Is it because they were RTTY, rather than FT8, where the grid is usually logged, whist in RTTY, it usually isn't?

+ A QSO can be confirmed via LoTW for DXCC, but if your QSO partner didn't include a grid square in the "Station Location" he or she employed to submit your QSO to LoTW, then the grid square won't be confirmed. If after submitting a QSO with a "Station Location" that doesn't specify a grid square, one of your QSO partners adds the grid square to the "Station Location" and resubmits that QSO, DXKeeper's "Sync LoTW QSLs" function will not update your QSO to reflect the grid square confirmation because LoTW doesn't consider the update a "new confirmation" -- a defect in LOTW, in my opinion.

+ To update those QSOs,

1. filter the Log Page Display with

(Band = '6m') and (Len(gridsquare)>0 ) and (APP_DXKEEPER_LOTW_QSL_RCVD in ('Y','S','V')) and not (APP_DXKEEPER_LOTWCONFIRMATION like '*G*')

and note the number of QSOs in the Log Page Display

2. On the Main window's QSL tab,

2a. set the "QSL Via" panel to LoTW

2b. click the "Update from LoTW" button

3. rerun the SQL expression from step 1 to see how many 6M QSOs with unconfirmed gridsquares remain in your log


+ If you have made 6M QSOs with stations operating on grid square boundaries, then you should repeat the above process for gridsquares 2, 3, and 4. Grid 2, for example, would employ this SQL expression in step 1:

(Band = '6m') and (Len(APP_DXKEEPER_GRID2)>0 ) and (APP_DXKEEPER_LOTW_QSL_RCVD in ('Y','S','V')) and not (APP_DXKEEPER_LOTWCONFIRMATION like '*2*')


I also notice that the VUCC report brings up contacts where there is no card, and no LoTW confirmation, so I would really like to get a VUCC report for just those grids confirmed on LoTW. is that possible?

+ Yes; filter the Log Page Display with the expression

(APP_DXKEEPER_LOTWCONFIRMATION like '*G*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*2*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*3*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*4*')

+ before running the VUCC progress report

73,

Dave, AA6YQ


Transfer a Workspace ...

Peter Laws / N5UWY
 

Transfer a what now?

I have a workspace (and log and TQSL certs) for a club's call. As
soon as I get the paperwork done, I will no longer legally be trustee
for the call or hold the repeater coordinations - yay me!

I need to move the log to the new trustee's system. We expect to do
this by Zoom and Dropbox because it's 2021 and there is no need to be
within 2 m of other humans (we're both vaxxed, but still - Oklahoma's
7-day rolling average was down to about 100 new cases/day around
Memorial Day ... now at 500/day ... and climbing).

The new trustee uses DXLab -- I helped him with his own TQSL setup
within it -- but I'm not sure he has any workspaces configured. Does
a new install set one up or is the default to not set one up? It's
been so long since I first installed the Suite, I don't remember! If
he doesn't have a workspace, I plan to send him to
https://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace and
https://www.dxlabsuite.com/Launcher/Help/RegistrySettings.htm so he
has one for his own call.

Is there a how-to for moving a workspace from one system to another?
I'm going to assume it's something along the lines of "switch to that
ws, save all the settings, switch out, then tar up the directory in
c:/apps/DXLab/Launcher/Workspace" ... Untarring it on his system is
great but how do we get Launcher to see it?

Peter

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


VUCC report query

Phil Cooper
 

Hi Dave and the group,

Simply because my compromise antenna seems to be doing better than expected, mainly because of the improving conditions on 6m, I am starting to chase DXCC, and also keeping an eye on my VUCC total on LoTW.

Currently, LoTW shows that I have 200 grids confirmed on 6m.
However, when I check the VUCC report in DXKeeper, it says 214 worked and 186 confirmed.

Looking at the report, there are quite a few that show MISSING under the LoTW Confirm heading, but are confirmed on LoTW and show up in my VUCC total.
Is it because they were RTTY, rather than FT8, where the grid is usually logged, whist in RTTY, it usually isn't?

I also notice that the VUCC report brings up contacts where there is no card, and no LoTW confirmation, so I would really like to get a VUCC report for just those grids confirmed on LoTW. is that possible?

I'm also very surprised at the number of stations using 6m that use LoTW, but do not have a grid set in whatever it is they use to upload to LoTW! Sadly, most are Italian stations, but there are others too.

73 de Phil GU0SUP


Re: Windows 11

Gilbert Baron W0MN
 

Two things. First I got 2 copies of this post but one had no text. They came at the same time. Very strange.
As for W11, my worry is not the possibility of trouble with W11 and the coding tools used buy Dave. So far it seems there is o problem.

My worry is that when W10 support ends I will be out of luck since I cannot switch to W11 under the 3rd gen processor in this machine. Everything I have is running well and do not wat to be forced to buy a new machine. If the current information that you will need an 8th gen processor to run W11 is true it is a worry. On the other hand I would not be surprised if things force me to buy new machines. At least it is 4 years away you say.

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 Al Groff via groups.io
Sent: Monday, July 19, 2021 13:08
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 11

FWIW..
DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary! And Windows 11 could still change before release.

AL, K0VM


On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.










--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DXK DXCC Submission Question

Dave AA6YQ
 

+ AA6YQ comments below

I have generated a DXCC submission in DXK, based on QSL cards received, that resulted in 139 QSO's being selected for submission. I only want to include 100 of those QSO's. If I go into my log and change the QSL received status for the 39 QSO's that I don't want to submit from "S" back to "Y" and I then generate the ADIF file for online submission will the ADIF file only include the 100 QSO's I want to submit? Assuming my DXCC application QSO's are later all verified by DXCC, if I select "Verify Submission" will DXK only change the QSL received status to "V" for the 100 QSO's I submitted?

+ Yes.

I know the answer may seem obvious but I want to check with the experts before I mess things up if I'm wrong. I already messed up my log by changing QSO's in the QSL Queue a while back and I don't want a repeat.

+ To alleviate your anxiety, I strongly suggest that you make a backup copy of your log before starting the above process. Then you'll be able to "undo" if things don't go as expected.

73,

Dave, AA6YQ


Re: Windows 11

Ed W2LCQ
 

Great focus Dave. Thanks for those replies.

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA

On Jul 19, 2021, at 2:08 PM, Al Groff via groups.io <al.k0vm=yahoo.com@groups.io> wrote:

FWIW..
DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary! And Windows 11 could still change before release.

AL, K0VM


On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.







Re: Windows 11

Al Groff
 

FWIW..
  DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary!  And Windows 11 could still change before release.

AL, K0VM

On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.



Re: Windows 11

Peter Laws / N5UWY
 

The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Windows 11

Dave AA6YQ
 

+ AA6YQ comments below

I see this morning that W11 will not install on any processor that is not at least an 8th generation I assume that means W10 will stay with us

+ That's Microsoft's call.

and that DXLab will live on with my 3rd generation processor, right?

+ The last time I checked, DXLab applications could still run on Windows 98.

73,

Dave, AA6YQ


DXK DXCC Submission Question

Dale Drake
 

I have generated a DXCC submission in DXK, based on QSL cards received, that resulted in 139 QSO's being selected for submission.  I only want to include 100 of those QSO's.  If I go into my log and change the QSL received status for the 39 QSO's that I don't want to submit from "S" back to "Y" and I then generate the ADIF file for online submission will the ADIF file only include the 100 QSO's I want to submit?  Assuming my DXCC application QSO's are later all verified by DXCC, if I select "Verify Submission" will DXK only change the QSL received status to "V" for the 100 QSO's I submitted?

I know the answer may seem obvious but I want to check with the experts before I mess things up if I'm wrong.  I already messed up my log by changing QSO's in the QSL Queue a while back and I don't want a repeat.

Thanks,

Dale AA1QD


Windows 11

Gilbert Baron W0MN
 

I see this morning that W11 will not install on any processor that is not at least an 8th generation I assume that means W10 will stay with us and that DXLab will live on with my 3rd generation processor, right? 😊

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

5581 - 5600 of 208073