Date
1 - 8 of 8
DXLab Launcher 2.2.2 is available
Dave AA6YQ
If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in
<https://www.microsoft.com/en-us/wdsi/definitions>
before installing or upgrading to DXLab Launcher version 2.2.2.
Reminder, since it's been more than a year since the DXLab Launcher was last updated: when you direct the Launcher to update itself,
it downloads the new version, and then displays a small window informing you that it is about to terminate.
You must click the OK button in this small window to complete the update. The running version of the Launcher will terminate, and
then version 2.2.2 will automatically start
This release
- replaces the existing ability to terminate "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" with a mechanism
that no longer requires the specification of each application's "Main window caption"; the "Show Paths" and "Show Captions" buttons
on the Configuration window's "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" tabs are no longer needed, and
have been removed
- provides Terminate buttons that manually terminate Apps "Started Before DXLab Apps" and "Apps Started After DXLab Apps" and
"Terminate Forcefully" checkboxes that when checked cause these apps to be terminated forcefully
- for "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps", accepts a Command Line with optional arguments
- when the Main window's Terminate button is clicked, terminates enabled "Apps Started After DXLab Apps" first, followed by DXLab
Apps, followed by "Apps Started Before DXLab Apps"; this is a change in behavior from the previous Launcher versions, which
terminated all non-DXLab apps after terminating DXLab apps.
- updates the Configuration.htm and ControllingApplications.htm documentation files
Notes
1. Thanks to Don AD0K, Dave W6DE, Joe W4TV, Rick K8EZB, David N4IW, and Chris W2PA and for their encouragement and help with this
new version of the Launcher
2. The Launcher's improved ability to terminate non-DXLab applications is documented here:
https://www.dxlabsuite.com/Launcher/Help/ControllingApplications.htm#Order_of_Application_Start-up_and_Termination
3. If you've been specifying .bat files to start non-DXLab applications that require command line arguments and want to exploit
Launcher 2.2.2's ability to also terminate those applications, then change the "Command Lines" for those applications to specify the
required arguments; otherwise, you can continue to specify .bat files.
4. Update your firewall and anti-malware applications to consider this new version of the Launcher to be "safe"
Virus total: 68 of 69 engines detected no malware
Jotti: 14 of 14 engines detected no malware
Microsoft Security Intelligence: no malware
5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>
6. After upgrading, to revert to the previous version of the Launcher, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>
7. No other publicly-released DXLab application exploits the new RDA database; that will soon change.
DXLab Launcher 2.2.2 is available via the DXLab Launcher and via
<http://www.dxlabsuite.com/download.htm>
73,
Dave, AA6YQ
<https://www.microsoft.com/en-us/wdsi/definitions>
before installing or upgrading to DXLab Launcher version 2.2.2.
Reminder, since it's been more than a year since the DXLab Launcher was last updated: when you direct the Launcher to update itself,
it downloads the new version, and then displays a small window informing you that it is about to terminate.
You must click the OK button in this small window to complete the update. The running version of the Launcher will terminate, and
then version 2.2.2 will automatically start
This release
- replaces the existing ability to terminate "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" with a mechanism
that no longer requires the specification of each application's "Main window caption"; the "Show Paths" and "Show Captions" buttons
on the Configuration window's "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" tabs are no longer needed, and
have been removed
- provides Terminate buttons that manually terminate Apps "Started Before DXLab Apps" and "Apps Started After DXLab Apps" and
"Terminate Forcefully" checkboxes that when checked cause these apps to be terminated forcefully
- for "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps", accepts a Command Line with optional arguments
- when the Main window's Terminate button is clicked, terminates enabled "Apps Started After DXLab Apps" first, followed by DXLab
Apps, followed by "Apps Started Before DXLab Apps"; this is a change in behavior from the previous Launcher versions, which
terminated all non-DXLab apps after terminating DXLab apps.
- updates the Configuration.htm and ControllingApplications.htm documentation files
Notes
1. Thanks to Don AD0K, Dave W6DE, Joe W4TV, Rick K8EZB, David N4IW, and Chris W2PA and for their encouragement and help with this
new version of the Launcher
2. The Launcher's improved ability to terminate non-DXLab applications is documented here:
https://www.dxlabsuite.com/Launcher/Help/ControllingApplications.htm#Order_of_Application_Start-up_and_Termination
3. If you've been specifying .bat files to start non-DXLab applications that require command line arguments and want to exploit
Launcher 2.2.2's ability to also terminate those applications, then change the "Command Lines" for those applications to specify the
required arguments; otherwise, you can continue to specify .bat files.
4. Update your firewall and anti-malware applications to consider this new version of the Launcher to be "safe"
Virus total: 68 of 69 engines detected no malware
Jotti: 14 of 14 engines detected no malware
Microsoft Security Intelligence: no malware
5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>
6. After upgrading, to revert to the previous version of the Launcher, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>
7. No other publicly-released DXLab application exploits the new RDA database; that will soon change.
DXLab Launcher 2.2.2 is available via the DXLab Launcher and via
<http://www.dxlabsuite.com/download.htm>
73,
Dave, AA6YQ
Dave AA6YQ
Item #7 in the Notes section below is an inadvertent leftover from the 2.1.7 release note; please ignore it.
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
73,
Dave, AA6YQ
-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, March 25, 2023 10:04 PM
To: DXLab@groups.io
Subject: [DXLab] DXLab Launcher 2.2.2 is available
If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in
<https://www.microsoft.com/en-us/wdsi/definitions>
before installing or upgrading to DXLab Launcher version 2.2.2.
Reminder, since it's been more than a year since the DXLab Launcher was last updated: when you direct the Launcher to update itself,
it downloads the new version, and then displays a small window informing you that it is about to terminate.
You must click the OK button in this small window to complete the update. The running version of the Launcher will terminate, and
then version 2.2.2 will automatically start
This release
- replaces the existing ability to terminate "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" with a mechanism
that no longer requires the specification of each application's "Main window caption"; the "Show Paths" and "Show Captions" buttons
on the Configuration window's "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" tabs are no longer needed, and
have been removed
- provides Terminate buttons that manually terminate Apps "Started Before DXLab Apps" and "Apps Started After DXLab Apps" and
"Terminate Forcefully" checkboxes that when checked cause these apps to be terminated forcefully
- for "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps", accepts a Command Line with optional arguments
- when the Main window's Terminate button is clicked, terminates enabled "Apps Started After DXLab Apps" first, followed by DXLab
Apps, followed by "Apps Started Before DXLab Apps"; this is a change in behavior from the previous Launcher versions, which
terminated all non-DXLab apps after terminating DXLab apps.
- updates the Configuration.htm and ControllingApplications.htm documentation files
Notes
1. Thanks to Don AD0K, Dave W6DE, Joe W4TV, Rick K8EZB, David N4IW, and Chris W2PA and for their encouragement and help with this
new version of the Launcher
2. The Launcher's improved ability to terminate non-DXLab applications is documented here:
https://www.dxlabsuite.com/Launcher/Help/ControllingApplications.htm#Order_of_Application_Start-up_and_Termination
3. If you've been specifying .bat files to start non-DXLab applications that require command line arguments and want to exploit
Launcher 2.2.2's ability to also terminate those applications, then change the "Command Lines" for those applications to specify the
required arguments; otherwise, you can continue to specify .bat files.
4. Update your firewall and anti-malware applications to consider this new version of the Launcher to be "safe"
Virus total: 68 of 69 engines detected no malware
Jotti: 14 of 14 engines detected no malware
Microsoft Security Intelligence: no malware
5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>
6. After upgrading, to revert to the previous version of the Launcher, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>
7. No other publicly-released DXLab application exploits the new RDA database; that will soon change.
DXLab Launcher 2.2.2 is available via the DXLab Launcher and via
<http://www.dxlabsuite.com/download.htm>
73,
Dave, AA6YQ
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, March 25, 2023 10:04 PM
To: DXLab@groups.io
Subject: [DXLab] DXLab Launcher 2.2.2 is available
If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in
<https://www.microsoft.com/en-us/wdsi/definitions>
before installing or upgrading to DXLab Launcher version 2.2.2.
Reminder, since it's been more than a year since the DXLab Launcher was last updated: when you direct the Launcher to update itself,
it downloads the new version, and then displays a small window informing you that it is about to terminate.
You must click the OK button in this small window to complete the update. The running version of the Launcher will terminate, and
then version 2.2.2 will automatically start
This release
- replaces the existing ability to terminate "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" with a mechanism
that no longer requires the specification of each application's "Main window caption"; the "Show Paths" and "Show Captions" buttons
on the Configuration window's "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" tabs are no longer needed, and
have been removed
- provides Terminate buttons that manually terminate Apps "Started Before DXLab Apps" and "Apps Started After DXLab Apps" and
"Terminate Forcefully" checkboxes that when checked cause these apps to be terminated forcefully
- for "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps", accepts a Command Line with optional arguments
- when the Main window's Terminate button is clicked, terminates enabled "Apps Started After DXLab Apps" first, followed by DXLab
Apps, followed by "Apps Started Before DXLab Apps"; this is a change in behavior from the previous Launcher versions, which
terminated all non-DXLab apps after terminating DXLab apps.
- updates the Configuration.htm and ControllingApplications.htm documentation files
Notes
1. Thanks to Don AD0K, Dave W6DE, Joe W4TV, Rick K8EZB, David N4IW, and Chris W2PA and for their encouragement and help with this
new version of the Launcher
2. The Launcher's improved ability to terminate non-DXLab applications is documented here:
https://www.dxlabsuite.com/Launcher/Help/ControllingApplications.htm#Order_of_Application_Start-up_and_Termination
3. If you've been specifying .bat files to start non-DXLab applications that require command line arguments and want to exploit
Launcher 2.2.2's ability to also terminate those applications, then change the "Command Lines" for those applications to specify the
required arguments; otherwise, you can continue to specify .bat files.
4. Update your firewall and anti-malware applications to consider this new version of the Launcher to be "safe"
Virus total: 68 of 69 engines detected no malware
Jotti: 14 of 14 engines detected no malware
Microsoft Security Intelligence: no malware
5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>
6. After upgrading, to revert to the previous version of the Launcher, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>
7. No other publicly-released DXLab application exploits the new RDA database; that will soon change.
DXLab Launcher 2.2.2 is available via the DXLab Launcher and via
<http://www.dxlabsuite.com/download.htm>
73,
Dave, AA6YQ
dl8le
Unfortunately the new release does not allow any longer to launch a bat-file, it request an exe-file according to the error-message popping up. I realised this when I wanted to launch sparksdr2dxc as one of my programs I start via the launcher. A bat-file is necessary for defining the necessary parameters. I can still launch the program manually, but it is not as convenient as before with the previous version of DXLab Launcher.
Info: sparksdr2dxc is a very helpful tool which acts as a spot source for Spotcollector, it collects all the data I receive on my Hermes Lite II using SparkSDR, i.e. I have an overview of all stations I receive at the moment.
73
Juergen, DL8LE
Info: sparksdr2dxc is a very helpful tool which acts as a spot source for Spotcollector, it collects all the data I receive on my Hermes Lite II using SparkSDR, i.e. I have an overview of all stations I receive at the moment.
73
Juergen, DL8LE
Dave AA6YQ
+ AA6YQ comments below
Unfortunately the new release does not allow any longer to launch a bat-file, it request an exe-file according to the error-message popping up. I realised this when I wanted to launch sparksdr2dxc as one of my programs I start via the launcher. A bat-file is necessary for defining the necessary parameters. I can still launch the program manually, but it is not as convenient as before with the previous version of DXLab Launcher.
+ Can you not specify those parameters in the Launcher's Command Line?
73,
Dave, AA6YQ
Unfortunately the new release does not allow any longer to launch a bat-file, it request an exe-file according to the error-message popping up. I realised this when I wanted to launch sparksdr2dxc as one of my programs I start via the launcher. A bat-file is necessary for defining the necessary parameters. I can still launch the program manually, but it is not as convenient as before with the previous version of DXLab Launcher.
+ Can you not specify those parameters in the Launcher's Command Line?
73,
Dave, AA6YQ
Bruce - K5WBM
I also use a bat file to execute a series of commands prior to starting the DXLab applications.
I also get an error "the specified Log File pathname for DXKeeper C:\... does not exist; DXKeeper will open the log file previously opened." The correct log is being opened but getting the error message at every startup is not desired.
On Sun, Mar 26, 2023 at 4:20 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
Unfortunately the new release does not allow any longer to launch a bat-file, it request an exe-file according to the error-message popping up. I realised this when I wanted to launch sparksdr2dxc as one of my programs I start via the launcher. A bat-file is necessary for defining the necessary parameters. I can still launch the program manually, but it is not as convenient as before with the previous version of DXLab Launcher.
+ Can you not specify those parameters in the Launcher's Command Line?
73,
Dave, AA6YQ
--
Bruce
K5WBM
Paul Keating
I, too, use a simple batch file (no defining parameters or other junk involved) that DXLab Launcher 2.2.2 will not start after opening all desired DXLab applications just because it's a ".bat" file vs an ".exe" file. The batch file further allows me to select applications (by keystroke) for operating based on operating mode (i.e., WSJT-X, JS8Call, FLDigi, etc.). While I could simply point & click on the batch file's desktop icon after clearing the pop-up error window and call it a day, it sure would be nice to have the batch file opened as it had been in previous releases.
This seems to be an "otherwise, you can continue to specify .bat files" situation that fails.
73 de Paul DU2FIS / K8SQ
This seems to be an "otherwise, you can continue to specify .bat files" situation that fails.
73 de Paul DU2FIS / K8SQ
Dave AA6YQ
+ AA6YQ comments below
I, too, use a simple batch file (no defining parameters or other junk involved) that DXLab Launcher 2.2.2 will not start after opening all desired DXLab applications just because it's a ".bat" file vs an ".exe" file. The batch file further allows me to select applications (by keystroke) for operating based on operating mode (i.e., WSJT-X, JS8Call, FLDigi, etc.). While I could simply point & click on the batch file's desktop icon after clearing the pop-up error window and call it a day, it sure would be nice to have the batch file opened as it had been in previous releases.
This seems to be an "otherwise, you can continue to specify .bat files" situation that fails.
+ Please see
https://groups.io/g/DXLab/message/214193?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Clauncher%2C20%2C2%2C0%2C97858963
+ The next version of the Launcher corrects the .bat regression, and enables you to select one of three termination methods for each non-DXLab application:
1. Close - direct Windows to send a "close" message to the application; as was the case in Launcher version 2.1.7, you must specify the application's Main Window Caption
2. Kill - direct Windows to terminate the application's process using its Taskkill command
3. ForceKill - direct Windows to terminate the application's process using its Taskkill command with its "terminate forcefully" option enabled
+ Several users are now testing a release candidate.
73,
Dave, AA6YQ
I, too, use a simple batch file (no defining parameters or other junk involved) that DXLab Launcher 2.2.2 will not start after opening all desired DXLab applications just because it's a ".bat" file vs an ".exe" file. The batch file further allows me to select applications (by keystroke) for operating based on operating mode (i.e., WSJT-X, JS8Call, FLDigi, etc.). While I could simply point & click on the batch file's desktop icon after clearing the pop-up error window and call it a day, it sure would be nice to have the batch file opened as it had been in previous releases.
This seems to be an "otherwise, you can continue to specify .bat files" situation that fails.
+ Please see
https://groups.io/g/DXLab/message/214193?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Clauncher%2C20%2C2%2C0%2C97858963
+ The next version of the Launcher corrects the .bat regression, and enables you to select one of three termination methods for each non-DXLab application:
1. Close - direct Windows to send a "close" message to the application; as was the case in Launcher version 2.1.7, you must specify the application's Main Window Caption
2. Kill - direct Windows to terminate the application's process using its Taskkill command
3. ForceKill - direct Windows to terminate the application's process using its Taskkill command with its "terminate forcefully" option enabled
+ Several users are now testing a release candidate.
73,
Dave, AA6YQ