+ AA6YQ comments below

I thought I understood Workspaces and over the years believed I created several successfully.

+ Norm, I suggest that you first refresh your understanding by reviewing

https://www.dxlabsuite.com/Launcher/Help/RegistrySettings.htm

+ If you still have questions after doing so, I'll be happy to answer them.

73,

Dave, AA6YQ

I thought I understood Workspaces and over the years believed I created several successfully.  However none of my 'creations' were significantly different and I am not sure if there was any detectable operational difference.  I am about ready to move my Ham operations to an new computer and therefore Workspaces have more importance. 

It has been several years since I last created a Workspace, and frankly have forgotten what to expect going through the process.  I am sure it is likely a 'Cockpit' problem, and hopefully someone will see my error in my description of the steps I took and have listed below.  

-Launcher open and other modules closed
-Open Launcher Config., select WORKSPACES, - and this presented the first issue -  
         The left side of the Workspaces window has a window titled: Workspaces (in Current Workspace Folder) - My window is blank!
-The routing window below says C:\DXLab\Launcher\Workspaces\w4qn_2017  also to the right there is an Highlighted button labeled 'Select Folder'
-Pressing that opens another window showing the Workspaces directory and three Workspace folders that have been created (including the 2017 ver.)
-Selecting a folder and pressing OK just changes the URL target folder,  But the larger window is still blank?

I am stalled at this point as I do not know what should have happened- that didn't.   I expected that the selected folder would have appeared in the large empty window and then either Load Settings, or Save Settings would be operational.

The above is my first problem-

Next is regard the Right side of the panel  and that sub window is Titled (blue font) Selected DXLab Application  
The nature of the drop down windows listing individual applications suggests that the 'configurations' of those individuals apps can be saved or loaded.

Not making any progress on those either -

So what am I missing or what procedural steps need to be corrected?

My Objective is to create a New 2022 folder.

--
Norm_W4QN

+ AA6YQ comments below

The error message is : the QSO cannot be saved because the item(s) flashing in red font are either invalid or missing, either correct this item or delete the QSO...
I enter 2400 (without decimal separator) or 10000 this is the same error message

+ Ok. So that I can see what's going on, please do the following:

1. start DXKeeper

2. on the Configuration window's General tab, check the "Log debugging info" box

3. log a test QSO with a frequency of 2400 Mhz

4. on the Configuration window's General tab, uncheck the "Log debugging info" box

5. 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

The error message is : the QSO cannot be saved because the item(s) flashing in red font are either invalid or missing, either correct this item or delete the QSO...
I enter 2400 (without decimal separator) or 10000 this is the same error message.

73 - Damien F5RRS

+ AA6YQ comments bewlow

I use a fresh DXLabsuite installation of a fresh new computer (Win11 French-Swiss).
I have an error message that happens when I enter a transmission or reception frequency beyond 1000 MHz in DXKeeper.
It recognizes the band well (for example 13cm) but does not want to tolerate a frequency despite it being located in the range of the "DefaultBands.txt" file. I don't have a "bands.txt" file.
The problem is that I can't log a QSO without deleting the "tx Freq" and "rx Freq" fields each time.
This same operation works perfectly on another installation (Win10 French).

+ What is the exact text of the error message?

+ In DXKeeper, frequencies are specified in megahertz. Are you using the correct decimal separator character for your Windows locale?

      73,

               Dave, AA6YQ

 

Hello,
I use a fresh DXLabsuite installation of a fresh new computer (Win11 French-Swiss).
I have an error message that happens when I enter a transmission or reception frequency beyond 1000 MHz in DXKeeper.
It recognizes the band well (for example 13cm) but does not want to tolerate a frequency despite it being located in the range of the "DefaultBands.txt" file. I don't have a "bands.txt" file.
The problem is that I can't log a QSO without deleting the "tx Freq" and "rx Freq" fields each time.
This same operation works perfectly on another installation (Win10 French).
Ideas?

73 - Damien F5RRS

+ AA6YQ comments 

Update:  Did the install again but this time when it asked if I wanted to install in "DXLabLauncher" (which is strange in itself) I changed it to "DXLab" and checked "yes" when asked if I wanted that folder created.  Lo and behold all of the installions were installed!  However, Commander, Spotcollector, etc. are NOT in the "C:\\DXLab" directory.  They were all instead installed in the "C:\\" in spite of my instructions.   The only thing in the "C:\\DXLab" is Launcher and some other stuff like Launch Agent.  I just check Launcher and there were some upgrades which installed with no problems.

Anyway, I'm taking a break but will see if things actually work later.  I still have not idea why all of this is happening.  It's really weird!

+ Each DXLab application must be installed in its own folder; they will not work when installed in the same folder as another DXLab application.

+ When you direct the Launcher to install a DXLab application, it displays the default installation folder, and provides you with the opportunity to specify a different folder. This is shown in the third screen shot in

https://www.dxlabsuite.com/dxlabwiki/InstallApplication

+ To correct your installation,

1. Direct Windows to uninstall all of your DXLab applications.

2. Install the Launcher in C:\DXLab\Launcher

3. Direct the Launcher to Install Commander in C:\DXLab\Commander

4. Direct the Launcher to Install DXKeeper in C:\DXLab\DXKeeper

5. Direct the Launcher to Install DXView in C:DXLab\DXView

6. Direct the Launcher to Install Pathfinder in C:\DXLab\Pathfinder

7. Direct the Launcher to Install PropView in C:\DXLab\PropView

8. Direct the Launcher to Install SpotCollector in C:\DXLab\SpotCollector

9. Direct the Launcher to Install WinWarbler in C:\DXLab\WinWarbler

    73,

          Dave, AA6YQ

 

 

Update:  Did the install again but this time when it asked if I wanted to install in "DXLabLauncher" (which is strange in itself) I changed it to "DXLab" and checked "yes" when asked if I wanted that folder created.  Lo and behold all of the installions were installed!  However, Commander, Spotcollector, etc. are NOT in the "C:\\DXLab" directory.  They were all instead installed in the "C:\\" in spite of my instructions.   The only thing in the "C:\\DXLab" is Launcher and some other stuff like Launch Agent.  I just check Launcher and there were some upgrades which installed with no problems.

Anyway, I'm taking a break but will see if things actually work later.  I still have not idea why all of this is happening.  It's really weird!

Aubrey, W7OLY

 

I am using Parallels 18 and Windows 11. I have installed DXLabs on a MacBook with the Intel chip and Windows 10 and previous versions of Parallels with out issue.

Tom
KQ5S

+ AA6YQ comments below

Yes, that would work,  but it seems to me that if the ADIF record coming from somewhere else doesn't have a contest ID and contest mode is selected in DxKeeper and a contest ID is specified it would be simple enough to substitute the DxKeeper info into the log.

+ The fact that something would be easy or difficult to implement is irrelevant.

+ To avoid confusion and conflicts, the source of the QSO must specify the Contest ID, tx exchange, and rx exchange. 

        73,

              Dave, AA6YQ

Yes, that would work,  but it seems to me that if the ADIF record coming from somewhere else doesn't have a contest ID and contest mode is selected in DxKeeper and a contest ID is specified it would be simple enough to substitute the DxKeeper info into the log.
--
John P.
WA2FZW

+ AA6YQ comments below

Neither WSJT-X not JTAlert have a provision for specifying a contest ID so they're incapable of telling DxKeeper what contest to log. If I tell DxKeeper to log the contest ID, seems as though it should do what I told it to do!

+ As I've stated, DXKeeper expects that an ADIF record it receives from another application to specify the Contest_ID and all other contest details.

+ You can quickly add the Contest ID to a set of already-logged QSOs by filtering the Log Page Display to include only those QSOs and then employing the "Modify QSOs" panel; see

https://www.dxlabsuite.com/dxlabwiki/QSOModifying

73,

Dave, AA6YQ

Neither WSJT-X not JTAlert have a provision for specifying a contest ID so they're incapable of telling DxKeeper what contest to log. If I tell DxKeeper to log the contest ID, seems as though it should do what I told it to do!
--
John P.
WA2FZW

+ AA6YQ comments below

Here's a screen shot of the results I get.

+ Screen shots are not conveyed here. Please attach your screen shot to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

+ AA6YQ comments below

Manual says:

"With Contest mode <https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Contest-mode> enabled and a Contest ID <https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Contest%20name> specified, the Contest ID <https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Contest%20name> is logged in each QSO."

+ That's correct when a QSO is logged via DXKeeper's Capture window or via its Main window's "Log QSOs" tab.

That's what I have set. Logging via WSJT-X and JTAlert.

+ When DXKeeper is directed by another application to log a QSO, the DXKeeper logs the Contest ID specified by the other application.

73,

Dave, AA6YQ

Thanks Tom.  I did and do all the things you described. Which version of Parallels and Windows?

I'm actually trying to install on a Mac Mini with an Intel chip and Monterey 12.5.1 using Parallels Desktop 18 for Mac and Windows 11 but I'm getting really frustrated.  Don't know if it's me or the hardware/software. 

The only Windows PC I have is the one I use for radios, logging, etc. and I'm getting to the point where I'm starting to think I'm just going to have to live with it and Win 7 Pro in the shack.

Aubrey, W7OLY

I just tried installing the suite on my M1 Mac.  Everything went as planned.   I downloaded Launcher and installed it. I then clicked on the config button in Launcher and installed the other apps.  Make sure there are no pop up windows hidden behind other windows.  I noticed this a couple of times.  I am using Parallels.

Tom
KQ5S

Here's a screen shot of the results I get.

Aubrey, W7OLY
Well, maybe not.  Appears that I can't send a jpg.

Dave,

Thanks for the reply.

The the installation software in the download package I got from the DXLab web site is defaulting to a folder called "DXLab Suite Installer" which I know isn't normal.  I tried it that way and got the symptoms I described.  I then changed the folder to "DXLab" and tried again with the same result.  Even tried "DXLab Suite". Again, no joy.

It's very strange!

Aubrey, W7OLY

On Sun, Sep 11, 2022 at 03:07 AM, Dave AA6YQ wrote:

On the Configuration window's Contest tab, to what did you set the "Contest ID" selector (just above the Cabrillo panel)?

It's set to "ARRL-VHF-SEP".
 
--
John P.
WA2FZW