Re: upgrade to latest Commander, now asks for permission to run (Win7)
A bit more research reveals that request by request by windows to allow the running of a program from an unknown source is partly a function of your Windows User Account Control (UAC) settings.
When the Launcher upgrades a DXLab application, it downloads a self-extracting executable, extracts the new application executable (e.g. DXView464.exe), places that new executable in the appropriate folder. Then it deletes the application's "current executable" (e.g. DXView.exe), makes a copy of the new executable (e.g. DXView464.exe), and renames that copy (in the case of DXVIew, to DXView.exe). None of this is accomplished with Administrative privileges enabled. Subsequently running the new DXView.exe does not result in Windows asking for confirmation to run a program from an unknown source.
Something you did caused Windows to alter what it considers the provenance of the file
CI-V Commander.exe
My research found no way to prevent the "run a program from an unknown source" question, other than by running with Admin privileges (don't do that!) or perhaps by reducing your UAC settings to a lower level of security.
Please do the following:
1. terminate Commander, if it's running
2. using Windows Explorer, navigate to your Commander folder
3. double-click the entry for the file
CI-V Commander1445.exe
Does Windows ask for permission to run a program from an unknown source ?
If the answer is "no", then
4. delete the file
CI-V Commander.exe
5. make a copy of the file
CI-V Commander1445.exe
6. rename the copy
CI-V Commander.exe
7. double-click the entry for the file
CI-V Commander.exe
Does Windows ask for permission to run a program from an unknown source ?
73,
Dave, AA6YQ
|
The Browser Path name is?D:\dxlab\launcher\DXLabLauncher.exe
The application Program Path is?D:\dxlab\launcher\DXLabLauncher210.exe
If I use Explorer to start Launcher using?D:\dxlab\launcher\DXLabLauncher.exe, it starts in the new version as it should. Unfortunately the Program Path is locked and I can't change the path.
Is there a way to unlock it?
|
Re: DXKeeper Display Issue
Dave, KB3MOW:
Take a look at this article I wrote several years ago:
In particular, read the very last paragraph about text may not fit into text
boxes.
The rest of the article describes how to select a monitor, should you decide
to upgrade.
I have been continuously upgrading my Monitors and Video cards, and I have
not found that any particular video card/monitor configuration to exhibit
the symptoms you describe. Providing the video card can handle the quantity
of pixels on your monitors, they should all work. Since I wrote the "old
eyes" article I have upgraded to an Acer 34" curved monitor with 3440 x 1440
pixels @ 100 Hz refresh rate. I still can drive this monitor with my old
small on-board memory video cards. But, because I ran out of proper
connections on the old cards, I upgraded to a newer video card that can
drive the 34" monitor, along with two older 23.5" monitors.
Best Regards,
Dave, w6de
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Dave Corio via groups.io Sent: 08 April, 2020 21:54 To: [email protected]Subject: Re: [DXLab] DXKeeper Display Issue Doesn't look like that's possible on this old HP. The BIOS gives the option of PCI, PCI Express, or Onboard. No combination appears to exist. This PC is almost 10 years old, so not as many bells & whistles! Going to dig a little deeper, and appreciate the input! 73 Dave - KB3MOW On 4/8/2020 4:37 PM, Dave AA6YQ wrote: + AA6YQ comments below
The video card is no longer supported and drives both monitors.
Motherboard video is disabled. I'm going to try decreasing the scaling a percentage point at a time and see if I can zero in on what (hopefully) works. Might be an easier option to just get glasses!
+ Another alternative you could try: activate the motherboard video, and use it to drive the secondary monitor.
73,
Dave, AA6YQ
|
Re: upgrade to latest Commander, now asks for permission to run (Win7)
+ AA6YQ comments below
I have had DXLabs installed for a while now (years). Been successfully clicking the "new app upgrades" banner and updating apps regularly. Never a trouble.
* Recently Defender did its thing and quarantined Commander.exe (v14.5.5),which I recovered and blocked scan of C:\DXLabs. All good on that front.
* Now when I execute commander (shortcut, from Launcher, etc) I get a request by windows to run a program from an unknown source.
* If I copy V14.4.0 to Commander.exe the trouble goes away and no questions asked.
* If I delete the upgrade versions in the Commander folder and let Laucher download the new version I still have Windows ask permission for an unknown source.
Is this a latent Windows Defender issue I have to fix?
Is V14.5.5 not signed with a source?
Something else?
+ No DXLab application has ever been "signed".
+ Every release candidate now passes a gauntlet of 60+ virus scanners via
+ before being publicly released. Each current version of each DXLab application has been checked,
+ No one has ever reported an actual infection in a DXLab application.
+ Questions about the behavior of specific antimalware applications may get answers here, but contacting the provider's technical support organization is the recommended path.
73,
Dave, AA6YQ
|
Re: DXKeeper Display Issue
Doesn't look like that's possible on this old HP. The BIOS gives the option of PCI, PCI Express, or Onboard. No combination appears to exist. This PC is almost 10 years old, so not as many bells & whistles! Going to dig a little deeper, and appreciate the input!
73
Dave - KB3MOW
toggle quoted message
Show quoted text
On 4/8/2020 4:37 PM, Dave AA6YQ wrote: + AA6YQ comments below
The video card is no longer supported and drives both monitors.
Motherboard video is disabled. I'm going to try decreasing the scaling a percentage point at a time and see if I can zero in on what
(hopefully) works. Might be an easier option to just get glasses!
+ Another alternative you could try: activate the motherboard video, and use it to drive the secondary monitor.
73,
Dave, AA6YQ
|
upgrade to latest Commander, now asks for permission to run (Win7)
Folks, Dave, I have had DXLabs installed for a while now (years). Been successfully clicking the "new app upgrades" banner and updating apps regularly. Never a trouble.
- Recently Defender did its thing and quarantined Commander.exe (v14.5.5),which I recovered and blocked scan of C:\DXLabs. All good on that front.
- Now when I execute commander (shortcut, from Launcher, etc) I get a request by windows to run a program from an unknown source.
- If I copy V14.4.0 to Commander.exe the trouble goes away and no questions asked.
- If I delete the upgrade versions in the Commander folder and let Laucher download the new version I still have Windows ask permission for an unknown source.
Is this a latent Windows Defender issue I have to fix? Is V14.5.5 not signed with a source? Something else? Thanks! -- 73 es God Bless de Ron KK1L <><
|
Re: DXKeeper Display Issue
+ AA6YQ comments below
The video card is no longer supported and drives both monitors.
Motherboard video is disabled. I'm going to try decreasing the scaling a percentage point at a time and see if I can zero in on what
(hopefully) works. Might be an easier option to just get glasses!
+ Another alternative you could try: activate the motherboard video, and use it to drive the secondary monitor.
73,
Dave, AA6YQ
|
Re: DXKeeper Display Issue
Thanks for the reply Dave!
The video card is no longer supported and drives both monitors. Motherboard video is disabled. I'm going to try decreasing the scaling a percentage point at a time and see if I can zero in on what (hopefully) works. Might be an easier option to just get glasses!
Tnx es 73
Dave - KB3MOW
toggle quoted message
Show quoted text
+ Is the secondary monitor driven by a video card, or by the motherboard? Contacting Support from the organization responsible for the video driver may yield a solution.
73,
Dave, AA6YQ
|
Re: DXKeeper Display Issue
+ AA6YQ comments below
Probably not a DXLab issue, but hoping you might have a better clue than me!
Using an AMD dual core 64 bit Win 10 Home setup with 2 monitors (24" main, 20" secondary). DXKeeper has been on the secondary monitor for several years. My eyes have gotten to the point that I was having trouble seeing either screen well. I increased the scaling of the Windows display from 100 % to 106%. I decreased the size of the font in DXKeeper, but the display now cuts off the bottom of the program, hiding the Sort, Filter name, and all the scripts. I've tried Config/Log/Log Page Display/Reset (for selected font size). I've also tried stretching the app up and out to the limits of the screen but the lower portion remains hidden. I have also closed one of the panels (Award) hoping that might work. No such luck.
I can now read the screens much better, with the exception of the bottom of DXKeeper! I suspect it's a Windows problem but maybe someone knows something I'm missing?
+ Is the secondary monitor driven by a video card, or by the motherboard? Contacting Support from the organization responsible for the video driver may yield a solution.
73,
Dave, AA6YQ
|
+ AA6YQ comments below
Thanks to all for the "virus" fix for Commander. All is well there, but I have a different issue. When Launcher opens (version 2.1.0) it indicates an upgrade to Launcher version 2.1.2 is available. That upgrade loads fine, but when I close Launcher and reopen it version 2.1.0 loads again. And the notice of an availbale upgrade shows up. I checked Defender virus history and found no reference to Launcher issues. Any ideas how to make 2.1.2 stick?
+ On the "DXLab Apps" tab of the Launcher's Configuration window, what "Program Path" is shown for the Launcher?
+ How are you starting the Launcher? What program path is specified by this mechanism?
73,
Dave, AA6YQ
|
Re: Commander and ACOM Solid State Amps
+ AA6YQ comments below
I'm curious as to why one would want do that versus using the program that comes with the Expert Amplifiers?
+ How would that program track the transceiver frequency with Commander running and connected to the transceiver's CAT port?
+ Since the SPE application is passive -- it just monitors CAT commands -- one could use a port splitter application to allow both the SPE application and the Commander to access the transceiver's CAT port. That approach requires starting and running new additional applications, compared to simply using Commander's Secondary CAT port
73,
Dave
|
Probably not a DXLab issue, but hoping you might have a better clue than me!
Using an AMD dual core 64 bit Win 10 Home setup with 2 monitors (24" main, 20" secondary). DXKeeper has been on the secondary monitor for several years. My eyes have gotten to the point that I was having trouble seeing either screen well. I increased the scaling of the Windows display from 100 % to 106%. I decreased the size of the font in DXKeeper, but the display now cuts off the bottom of the program, hiding the Sort, Filter name, and all the scripts. I've tried Config/Log/Log Page Display/Reset (for selected font size). I've also tried stretching the app up and out to the limits of the screen but the lower portion remains hidden. I have also closed one of the panels (Award) hoping that might work. No such luck.
I can now read the screens much better, with the exception of the bottom of DXKeeper! I suspect it's a Windows problem but maybe someone knows something I'm missing?
Tnx es 73
Dave - KB3MOW
|
Hi Conrad, Try this: If you are using WIN10 ? The new Launcher upgrade probably got quarantined. ? In WIN10 Search for: Search/Security at a glance in Win10 Click on Virus&Threat protection Click on Current threats/Protection history Looking at All recent items/in my case, There were Threats blocked marked Severe/click on down arrow beside each threat/at the bottom of the new window, there is a selection ( it was restore or allow) choose . In my case, I had 4 threats, all for Commander. I cleared all 4 of them. ? If you get that far, you probably need to also have the DXLab? folder set with an exception to not scan. ? Ed WA6WGS ? ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Conrad
Sent: Wednesday, April 08, 2020 8:19 AM
To: [email protected]
Subject: [DXLab] Launcher Upgrade ? Thanks to all for the "virus" fix for Commander. All is well there, but I have a different issue. When Launcher opens (version 2.1.0) it indicates an upgrade to Launcher version 2.1.2 is available. That upgrade loads fine, but when I close Launcher and reopen it version 2.1.0 loads again. And the notice of an availbale upgrade shows up. I checked Defender virus history and found no reference to Launcher issues. Any ideas how to make 2.1.2 stick?
|
Re: DXKeeper: Aux panel appears after Sync LotW QSOs operation
Log sent.
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Dave AA6YQ Sent: Tuesday, April 7, 2020 5:26 PM To: john@... Cc: [email protected]Subject: Re: [DXLab] DXKeeper: Aux panel appears after Sync LotW QSOs operation + AA6YQ comments below Thank you Dave, That's very interesting. But, 1. Right now I clicked on that QSO in my LPD, and the country code says 291; also the "rx band" field (in the Aux panel) says "6M". This QSO was logged to DXK from WSJT-X. I'm not surprised it contained incorrect info - I've run into that problem before. I don't understand why it is now correct in DXK. 2. Before the KD2KJU QSO I made other QSOs on 6M and 30M today. I uploaded these QSOs in very small batches to LotW, waiting a bit and then doing Sync LotW QSOs. Each time that I did this, the Aux panel appeared. These times were before the KD2KJU QSO existed. I checked these previous QSOs and they all appear correct regarding country code and rx band. I also clicked the Broke button, with a null result in the LPD. + The next time this behavior occurs, please place your Log file in a zip archive, attach the zip archive to an email message that describes the faulty QSO (callsign, date, time, band mode), and send the message to me via aa6yq (at) ambersoft.com + so that I can see what is going on. 73, Dave, AA6YQ
|
Thanks to all for the "virus" fix for Commander. All is well there, but I have a different issue. When Launcher opens (version 2.1.0) it indicates an upgrade to Launcher version 2.1.2 is available. That upgrade loads fine, but when I close Launcher and reopen it version 2.1.0 loads again. And the notice of an availbale upgrade shows up. I checked Defender virus history and found no reference to Launcher issues. Any ideas how to make 2.1.2 stick?
|
Re: Import Special event call log into my log
Station Call is the call used to identify the station on the air (N0S)
Operator Call is the call sign of the person operating the station (N0FY)
Owner Call is the call sign of the owner of the station (N0FY)
In LotW, the signing certificate should be a certificate for the Station Call (N0S), with location information (grid square, state, county) appropriate to the location of the station used.
73,
Rich VE3KI
toggle quoted message
Show quoted text
On Wed, Apr 8, 2020 at 09:27 AM, Tom Brown wrote:
I did not check the replacement options.? The log imported with Station Call: N0S; Op Call: N0S and Owner Call; N0S
I didn't check substitute N0FY for missing callsigns, but I'm guessing there weren't any missing based on the sentence above.
I believe the QSOs for LoTW do say N0S.
I'm guessing I need to reimport with the replacement options: Station Call N0FY; Operator Call N0S and Owner Call N0FY.
Is this how everyone sees it?
|
Re: Import Special event call log into my log
I did not check the replacement options.? The log imported with Station Call: N0S; Op Call: N0S and Owner Call; N0S
I didn't check substitute N0FY for missing callsigns, but I'm guessing there weren't any missing based on the sentence above.
I believe the QSOs for LoTW do say N0S.
I'm guessing I need to reimport with the replacement options: Station Call N0FY; Operator Call N0S and Owner Call N0FY.
Is this how everyone sees it?
|
Re: Commander and ACOM Solid State Amps
Hi
Dave
I'm
curious as to why one would want do that versus using the
program that comes with the Expert Amplifiers?
t u
73 Dwight NSS9I
On 4/7/2020 11:39 PM, Dave AA6YQ wrote:
toggle quoted message
Show quoted text
+ AA6YQ comments below
The manual for the 1200S has a table on page 22 listing Elecraft, Icom, Kenwood, and Yaesu.
Sounds like I just need to make up a custom cable for the amp's DB15 connector.
+ That's exactly what I did. Configure the Secondary CAT port to follow the Primary. I recommend using the Kenwood protocol.
+ You can use Commander's Messages window to monitor what's being sent to the Secondary CAT Port:
73,
Dave, AA6YQ
|
Re: Commander and ACOM Solid State Amps
+ AA6YQ comments below
The manual for the 1200S has a table on page 22 listing Elecraft, Icom, Kenwood, and Yaesu.
Sounds like I just need to make up a custom cable for the amp's DB15 connector.
+ That's exactly what I did. Configure the Secondary CAT port to follow the Primary. I recommend using the Kenwood protocol.
+ You can use Commander's Messages window to monitor what's being sent to the Secondary CAT Port:
<>
73,
Dave, AA6YQ
|
Re: Kenwood TS-480HX and DXLab Commander
+ AA6YQ comments below
I've spent the last hour and a half attempting to assist another ham via a Teamviewer session get Commander working the his TS-480HX. He has a RT Systems USB-63 cable and the RT Systems driver installed. (Viewing this via Windows Device Manager COM ports.)
RT USB-63:
His rig is likely set to 9600 bps (Kenwood default), but I'm working with him to confirm.
In Commander I selected KENWOOD and the port is 9600 8 N 1 with DTS and RTS are both set to On. The Port# is set to COM5. (Port appears/disappears in Device Manager Ports when he plugs/unplugs the cable and port is set to 9600/8/N/1.)
+ RTS should be set to "On", but DTR should be set to "Off".
System notes:
1) Has a K5IFNZ "Easy Digi" device attached to his laptop and this is plugged into the DIN/Data port on the TS-480.
2) He has an RTL-SDR dongle which is connected to the via an IF connection inside the TS-480.
3) Also runs HDSDR software as a panadapter. All of this appears to be working OK. HOWEVER, this software was NOT running when we tried to connect to Commander, but all of the cables for Easy Digi and IF cable are still plugged into the rig.
4) Also using a non-powered USB 4-port hub. Ports connected to the USB-63, IF wire, and Easy Digi.
We did attempt to connect the TS-480 using the USB-63 plugged directly into the laptop (no USB hub). We did power down the rig and rebooted the computer, etc.
+ I would start the debugging with in this "directly connected" configuration. Step 1 is to make sure the Commander and the radio are set to the same baud rate, word length of 8, 1 stop bit. With the port's RTS set to "on", Commander should track the transceiver's frequency and mode, and be able to set the transceiver's frequency and mode.
73,
Dave, AA6YQ
|
Dave Corio
KK1L Ron