Date   

Re: Commander to SatPC32 integration - will not connect

Dave Fugleberg
 

Thanks guys.
Some additional info.
My shack PC has local accounts only - one administrator account, and one regular user. I normally use that PC as the regular user.

I also have a laptop. On this laptop, I have only a single Microsoft account, which is an administrator. I just installed SatPC32 on that laptop. I used the right-click context menu on installer, and chose Run as Administrator, because the instructions say to do so even if you are an administrator.

After the installer completed, I ran the application normally (double click the shortcut on the desktop), and it started fine.

So, it seems to be related to the way my shack PC is set up.  Maybe it's time to give in and switch to Microsoft accounts on the shack PC.
73 de W0ZF


On Fri, Jul 30, 2021 at 9:04 PM Joe Subich, W4TV <lists@...> wrote:

 > Data files are in
 > C:Users/KI4US/AppData/Rosming/SatPC32

If the data files are in C:\User\<user_name>/AppData/Roaming
you are fine.  The program files can be in C:\Programs without
any issue (that is Microsoft's recommended configuration)
even as a "normal" user.

It sounds like Dave has another problem and should probably
seek support from the Developer of SatPC32.

73,

    ... Joe, W4TV


On 2021-07-30 9:20 PM, Bill Pence wrote:
> Satpc32.exe is in
> C:Program Files (x86)/SatPC32
>
> Data files are in
> C:Users/KI4US/AppData/Rosming/SatPC32
>
>
> As I recall, I made no changes in the install away from defaults...
>
>
> I know I am an admin on the pc but I think all my apps are in normal user
> mode...
>
> On Fri, Jul 30, 2021, 9:11 PM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> I do not run satpc32 in elevated admin mode...
>> Unsure why your system requires it.
>>
>> + In what folder do you have SatPC32 installed, Bill?
>>
>>      73,
>>
>>            Dave, AA6YQ
>>








Re: Commander to SatPC32 integration - will not connect

Joe Subich, W4TV
 

Data files are in
C:Users/KI4US/AppData/Rosming/SatPC32
If the data files are in C:\User\<user_name>/AppData/Roaming
you are fine. The program files can be in C:\Programs without
any issue (that is Microsoft's recommended configuration)
even as a "normal" user.

It sounds like Dave has another problem and should probably
seek support from the Developer of SatPC32.

73,

... Joe, W4TV


On 2021-07-30 9:20 PM, Bill Pence wrote:
Satpc32.exe is in
C:Program Files (x86)/SatPC32
Data files are in
C:Users/KI4US/AppData/Rosming/SatPC32
As I recall, I made no changes in the install away from defaults...
I know I am an admin on the pc but I think all my apps are in normal user
mode...
On Fri, Jul 30, 2021, 9:11 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I do not run satpc32 in elevated admin mode...
Unsure why your system requires it.

+ In what folder do you have SatPC32 installed, Bill?

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Bill Pence
 

Well crap. I thought i still had to "run as administrator "


On Fri, Jul 30, 2021, 9:27 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Satpc32.exe is in


C:Program Files (x86)/SatPC32

+ That's a folder that Windows considers "protected".


Data files are in
C:Users/KI4US/AppData/Rosming/SatPC32


As I recall, I made no changes in the install away from defaults...

I know I am an admin on the pc but I think all my apps are in normal user mode...

+ If your Windows user has admin privileges, so do all of the apps you start.

         73,

             Dave, AA6YQ








Re: Commander to SatPC32 integration - will not connect

Dave AA6YQ
 

+ AA6YQ comments below

Satpc32.exe is in


C:Program Files (x86)/SatPC32

+ That's a folder that Windows considers "protected".


Data files are in
C:Users/KI4US/AppData/Rosming/SatPC32


As I recall, I made no changes in the install away from defaults...

I know I am an admin on the pc but I think all my apps are in normal user mode...

+ If your Windows user has admin privileges, so do all of the apps you start.

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Dave Fugleberg
 

OK, so I uninstalled SatPC32 using the standard Windows 10 'Apps and Features' panel, and reinstalled. This time, I ran the installer using 'Run as Administrator', but when prompted for a location I instructed it to install to a new folder c:\SatPC32\.  The installation completed successfully.

I tried to run it normally (NOT as Administrator), and it immediately pops an error dialog with the title Error and the text "runtime error 217 at 00673791".

I closed that dialog and ran it using the 'Run as Administrator' right click context menu, and it runs fine.

So, it still appears to want to touch some protected area of Windows, which is bad form indeed.

I wonder what's different between my Windows system and Bill's ?  
73 de W0ZF





On Fri, Jul 30, 2021 at 7:36 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
SatPC32 is installed to the default location where its installer puts it - C:\Program Files (x86)\SatPC32\
 
Joe, if I try to run the application as a regular user, it errors with "runtime error 217 at 00673791".
 
By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110

+ You have SatPC32 installed in a file system location that Windows considers "protected", which means it requires Administrator privileges to run.

+ I suggest that you uninstall it, and install it in an unprotected location, like C:\SatPC32

     73,

           Dave, AA6YQ

 


Re: Commander to SatPC32 integration - will not connect

Bill Pence
 

Satpc32.exe is in 
C:Program Files (x86)/SatPC32

Data files are in
C:Users/KI4US/AppData/Rosming/SatPC32


As I recall, I made no changes in the install away from defaults...


I know I am an admin on the pc but I think all my apps are in normal user mode...

On Fri, Jul 30, 2021, 9:11 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I do not run satpc32 in elevated admin mode...
Unsure why your system requires it.

+ In what folder do you have SatPC32 installed, Bill?

    73,

          Dave, AA6YQ








Re: Commander to SatPC32 integration - will not connect

Dave AA6YQ
 

+ AA6YQ comments below

I do not run satpc32 in elevated admin mode...
Unsure why your system requires it.

+ In what folder do you have SatPC32 installed, Bill?

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Bill Pence
 

I do not run satpc32 in elevated admin mode...
Unsure why your system requires it.


On Fri, Jul 30, 2021, 5:50 PM Dave Fugleberg <davefugleberg@...> wrote:
Thanks Bill - I did read that. However, the problem is that Commander will not even connect to SatPC32, which must happen before SatPC32 tries to convey any data to Commander.  Just to be sure, I tried connecting while a sat was overhead and actively being tracked, but it made no difference.
I suspect the real problem is related to what Dave mentioned about administrator privilege. None of the DxLab programs require admin privs to run, and none are configured to do so.  SatPC32, on the other hand, will not even complete its installation unless you use the 'run as administrator' function on the installer. Once you do, you are forced to run the application as administrator every time you start it.  

Dave, this integration obviously works for someone...do those users routinely run DxLab as administrator? or is there some other trick involved?

On Fri, Jul 30, 2021 at 2:50 PM Bill Pence <pence.bill@...> wrote:
Could this be the issue?
Did you make this change from the dxlab setup info?

Continuous Tracking

By default, SatPC32 only conveys information to Commander when the selected satellite is above the horizon. You can change this to "always conveys information to Commander":

  1. In the ? menu, place your mouse over the Auxilliary Files entry; in the menu that appears to the right, select DivOptions.SQF

  2. The file DivOptions.SQF should appear in your default text file editor. Change the second line of this file from - (2) to + (2)

  3. Save the change you made to DivOptions.SQF


On Fri, Jul 30, 2021, 11:04 AM Dave Fugleberg <davefugleberg@...> wrote:
I'm trying to configure the integration shown in https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking to convey satellite information from SatPC32 to Commander and on to DxKeeper. I'm using SatPC32 v 12.9 and a IC-9700 with latest firmware.

Here's what works so far:
1) Commander configured for multi-radio - Radio 1 is my HF rig (K3), Radio 2 is direct control for the 9700, and radio 3 is SatPC32. All three are Enabled. the port for Radio 3 is set to - (the dash after port 64 in the pulldown).
2) Commander can control Radio 1 or Radio 2 when selected from Commander. CAT control behaves as expected for either radio.
3) With Radio 3 (SatPC32) selected in Commander, I go and start SatPC32.  SatPC32 controls the radio and works as expected.  At this point, the box in the upper right corner of Commander says Disconnected and Satellite name and mode are blank, as expected.

However - 
When I click Connect, nothing happens. Commander still says Disconnected.

Is there something in the configuration of SatPC32 I may have missed ?

Thanks es 73 de W0ZF


Re: Commander to SatPC32 integration - will not connect

Dave AA6YQ
 

+ AA6YQ comments below
SatPC32 is installed to the default location where its installer puts it - C:\Program Files (x86)\SatPC32\
 
Joe, if I try to run the application as a regular user, it errors with "runtime error 217 at 00673791".
 
By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110

+ You have SatPC32 installed in a file system location that Windows considers "protected", which means it requires Administrator privileges to run.

+ I suggest that you uninstall it, and install it in an unprotected location, like C:\SatPC32

     73,

           Dave, AA6YQ

 


Re: Commander to SatPC32 integration - will not connect

Joe Subich, W4TV
 

Joe, if I try to run the application as a regular user, it errors with
"runtime error 217 at 00673791".
Looks to meas if SatPC32 is putting its config files in the program
directory and you have installed it in a protected location. Simply
put, it is bad programming to make the default installation location
C:\Program Files or C:\Program Files (x86) if you write configuration
files to the program directory (or a sub directory of the program
directory).

73,

... Joe, W4TV


On 2021-07-30 7:37 PM, Dave Fugleberg wrote:
Dave,
SatPC32 is installed to the default location where its installer puts it -
C:\Program Files (x86)\SatPC32\
Joe, if I try to run the application as a regular user, it errors with
"runtime error 217 at 00673791".
By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110
73 de W0ZF
On Fri, Jul 30, 2021 at 5:40 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Once you do, you are forced to run the application as administrator
every time you start it.
Not the case unless you have installed an application that writes user
files to its own directories in a "protected" directory. I know of many
applications that recommend running the installer
(only) as administrator to assure the proper keys are written to the
Registry.

+ That's my next question, Dave: in what folder is SatPC32 installed?

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Dave Fugleberg
 

Dave,
SatPC32 is installed to the default location where its installer puts it - C:\Program Files (x86)\SatPC32\

Joe, if I try to run the application as a regular user, it errors with "runtime error 217 at 00673791".

By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110

73 de W0ZF


On Fri, Jul 30, 2021 at 5:40 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

> Once you do, you are forced to run the application as administrator
> every time you start it.

Not the case unless you have installed an application that writes user files to its own directories in a "protected" directory.  I know of many applications that recommend running the installer
(only) as administrator to assure the proper keys are written to the Registry.

+ That's my next question, Dave: in what folder is SatPC32 installed?

       73,

             Dave, AA6YQ








Re: Commander to SatPC32 integration - will not connect

Dave AA6YQ
 

+ AA6YQ comments below

Once you do, you are forced to run the application as administrator
every time you start it.
Not the case unless you have installed an application that writes user files to its own directories in a "protected" directory. I know of many applications that recommend running the installer
(only) as administrator to assure the proper keys are written to the Registry.

+ That's my next question, Dave: in what folder is SatPC32 installed?

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Joe Subich, W4TV
 

Once you do, you are forced to run the application as administrator
every time you start it.
Not the case unless you have installed an application that writes
user files to its own directories in a "protected" directory. I
know of many applications that recommend running the installer
(only) as administrator to assure the proper keys are written
to the Registry.

73,

... Joe, W4TV


On 2021-07-30 5:50 PM, Dave Fugleberg wrote:
Thanks Bill - I did read that. However, the problem is that Commander will
not even connect to SatPC32, which must happen before SatPC32 tries to
convey any data to Commander. Just to be sure, I tried connecting while a
sat was overhead and actively being tracked, but it made no difference.
.
I suspect the real problem is related to what Dave mentioned about
administrator privilege. None of the DxLab programs require admin privs to
run, and none are configured to do so. SatPC32, on the other hand, will
not even complete its installation unless you use the 'run as
administrator' function on the installer. Once you do, you are forced to
run the application as administrator every time you start it.
Dave, this integration obviously works for someone...do those users
routinely run DxLab as administrator? or is there some other trick involved?
On Fri, Jul 30, 2021 at 2:50 PM Bill Pence <pence.bill@...> wrote:

Could this be the issue?
Did you make this change from the dxlab setup info?
https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking
Continuous Tracking

By default, SatPC32 only conveys information to Commander when the
selected satellite is above the horizon. You can change this to "always
conveys information to Commander":

1.

In the *?* menu, place your mouse over the *Auxilliary Files* entry;
in the menu that appears to the right, select *DivOptions.SQF*
2.

The file *DivOptions.SQF* should appear in your default text file
editor. Change the second line of this file from - (2) to + (2)
3.

Save the change you made to *DivOptions.SQF*


On Fri, Jul 30, 2021, 11:04 AM Dave Fugleberg <davefugleberg@...>
wrote:

I'm trying to configure the integration shown in
https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking to convey
satellite information from SatPC32 to Commander and on to DxKeeper. I'm
using SatPC32 v 12.9 and a IC-9700 with latest firmware.

Here's what works so far:
1) Commander configured for multi-radio - Radio 1 is my HF rig (K3),
Radio 2 is direct control for the 9700, and radio 3 is SatPC32. All three
are Enabled. the port for Radio 3 is set to - (the dash after port 64 in
the pulldown).
2) Commander can control Radio 1 or Radio 2 when selected from Commander.
CAT control behaves as expected for either radio.
3) With Radio 3 (SatPC32) selected in Commander, I go and start SatPC32.
SatPC32 controls the radio and works as expected. At this point, the box
in the upper right corner of Commander says Disconnected and Satellite name
and mode are blank, as expected.

However -
When I click Connect, nothing happens. Commander still says Disconnected.

Is there something in the configuration of SatPC32 I may have missed ?

Thanks es 73 de W0ZF


Re: Commander to SatPC32 integration - will not connect

Dave Fugleberg
 

Thanks Bill - I did read that. However, the problem is that Commander will not even connect to SatPC32, which must happen before SatPC32 tries to convey any data to Commander.  Just to be sure, I tried connecting while a sat was overhead and actively being tracked, but it made no difference.
I suspect the real problem is related to what Dave mentioned about administrator privilege. None of the DxLab programs require admin privs to run, and none are configured to do so.  SatPC32, on the other hand, will not even complete its installation unless you use the 'run as administrator' function on the installer. Once you do, you are forced to run the application as administrator every time you start it.  

Dave, this integration obviously works for someone...do those users routinely run DxLab as administrator? or is there some other trick involved?

On Fri, Jul 30, 2021 at 2:50 PM Bill Pence <pence.bill@...> wrote:
Could this be the issue?
Did you make this change from the dxlab setup info?

Continuous Tracking

By default, SatPC32 only conveys information to Commander when the selected satellite is above the horizon. You can change this to "always conveys information to Commander":

  1. In the ? menu, place your mouse over the Auxilliary Files entry; in the menu that appears to the right, select DivOptions.SQF

  2. The file DivOptions.SQF should appear in your default text file editor. Change the second line of this file from - (2) to + (2)

  3. Save the change you made to DivOptions.SQF


On Fri, Jul 30, 2021, 11:04 AM Dave Fugleberg <davefugleberg@...> wrote:
I'm trying to configure the integration shown in https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking to convey satellite information from SatPC32 to Commander and on to DxKeeper. I'm using SatPC32 v 12.9 and a IC-9700 with latest firmware.

Here's what works so far:
1) Commander configured for multi-radio - Radio 1 is my HF rig (K3), Radio 2 is direct control for the 9700, and radio 3 is SatPC32. All three are Enabled. the port for Radio 3 is set to - (the dash after port 64 in the pulldown).
2) Commander can control Radio 1 or Radio 2 when selected from Commander. CAT control behaves as expected for either radio.
3) With Radio 3 (SatPC32) selected in Commander, I go and start SatPC32.  SatPC32 controls the radio and works as expected.  At this point, the box in the upper right corner of Commander says Disconnected and Satellite name and mode are blank, as expected.

However - 
When I click Connect, nothing happens. Commander still says Disconnected.

Is there something in the configuration of SatPC32 I may have missed ?

Thanks es 73 de W0ZF


Re: Change of ClubLog status

Dave AA6YQ
 

+ AA6YQ comments below

+ DXKeeper does include the CREDIT_GRANTED field when exporting an
ADIF file using the Main window's "Export QSOs" tab, but does not
include this field when uploading a QSO to ClubLog because ClubLog
doesn't currently accept it. Michael G7VJR has indicated that he will
extend ClubLog to accept CREDIT_GRANTED, at which point I will extend
DXKeeper to include it when uploading a QSO to ClubLog.

I understand that Michael will be working to extend ClubLog to accept the ADIF <CREDIT_GRANTED> tag. Will you replace the use of QSL_RCVD= 'V', 'E', 'B', & 'M' and and LotW_QSL_RCVD='V' with their equivalent DXCC representation in <CREDIT_GRANTED>?

+ No. I will leave the QSL_RCVD and LOTW_QSL_RCVD fields in place, and add CREDIT_GRANTED.

73,

Dave, AA6YQ


Re: Change of ClubLog status

Joe Subich, W4TV
 

+ DXKeeper does include the CREDIT_GRANTED field when exporting an ADIF file using the Main window's "Export QSOs" tab, but does not include this field when uploading a QSO to ClubLog because ClubLog doesn't currently accept it. Michael G7VJR has indicated that he
will extend ClubLog to accept CREDIT_GRANTED, at which point I will extend DXKeeper to include it when uploading a QSO to ClubLog.
I understand that Michael will be working to extend ClubLog to accept
the ADIF <CREDIT_GRANTED> tag. Will you replace the use of QSL_RCVD=
'V', 'E', 'B', & 'M' and and LotW_QSL_RCVD='V' with their equivalent
DXCC representation in <CREDIT_GRANTED>?

However, my first issue is not directly impacted by that as it appears
CLubLog's Grid Map is not reflecting *any* QSO confirmed (or verified
for DXCC) by card. I have further responded to Michael off-line with
several examples from my own logs where the QSO is present and marked
"confirmed" or "verified" when examined in ClubLog's Log Explorer but
is not present (or another "lower priority" QSO shown) in the ClubLog
Grid Map (Beta).


73,

... Joe, W4TV


On 2021-07-30 2:15 PM, Dave AA6YQ wrote:
+ AA6YQ comments below


As reported off-line, ClubLog's grid square map is very buggy.

1) It does not reflect grids (I've only checked on 6m) confirmed
or verified by card (QSL_RCVD= Y or V)
2) It does not show as "Verified" *any* grid that is not also
"Verified" for DXCC by LotW (App_DXKeeper_LotW_QSL_RCVD = V).

The first is completely unexpected while the second could be
foreseen since DXKeeper does not export a "Credit Granted" tag.
+ DXKeeper does include the CREDIT_GRANTED field when exporting an ADIF file using the Main window's "Export QSOs" tab, but does not include this field when uploading a QSO to ClubLog because ClubLog doesn't currently accept it. Michael G7VJR has indicated that he will extend ClubLog to accept CREDIT_GRANTED, at which point I will extend DXKeeper to include it when uploading a QSO to ClubLog.
73,
Dave, AA6YQ


Re: Reset filter button

Dave AA6YQ
 

+ AA6YQ comments below

On the main Log QSOs tab of DXKeeper, next to the window to enter filter parameters is the X button that resets the display of all QSO's , Ctrl Click reset the filter and set sort panel to UTC

+ The Filter panel's X button removes all filtering from the Log Page Display. CTRL-click removes all filtering and sets the sort to UTC.

.Everything works except resetting the filter box to a null set (clear it out). Very very minor, but maybe something to add to the next updates.

+ The current behavior is correct. If you want to clear the Filter panel's textbox, place the mouse cursor in that textbox, and strike CTRL-A followed by the DEL key.

73,

Dave, AA6YQ


Reset filter button

Michael E Wilson Sr <ke5wct@...>
 

On the main Log QSOs tab of DXKeeper, next to the window to enter filter parameters is the X button that resets the display of all QSO's , Ctrl Click reset the filter and set sort panel to UTC. Everything works except resetting the filter box to a null set (clear it out). Very very minor, but maybe something to add to the next updates.
I only noticed because I am writing a more non-technical narrative of how to configure things and how they work, for my young grand-children.
Thank you for a wonderful produce.
73 de KE5WCT
MikE


Re: Commander to SatPC32 integration - will not connect

Bill Pence
 

Could this be the issue?
Did you make this change from the dxlab setup info?

Continuous Tracking

By default, SatPC32 only conveys information to Commander when the selected satellite is above the horizon. You can change this to "always conveys information to Commander":

  1. In the ? menu, place your mouse over the Auxilliary Files entry; in the menu that appears to the right, select DivOptions.SQF

  2. The file DivOptions.SQF should appear in your default text file editor. Change the second line of this file from - (2) to + (2)

  3. Save the change you made to DivOptions.SQF


On Fri, Jul 30, 2021, 11:04 AM Dave Fugleberg <davefugleberg@...> wrote:
I'm trying to configure the integration shown in https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking to convey satellite information from SatPC32 to Commander and on to DxKeeper. I'm using SatPC32 v 12.9 and a IC-9700 with latest firmware.

Here's what works so far:
1) Commander configured for multi-radio - Radio 1 is my HF rig (K3), Radio 2 is direct control for the 9700, and radio 3 is SatPC32. All three are Enabled. the port for Radio 3 is set to - (the dash after port 64 in the pulldown).
2) Commander can control Radio 1 or Radio 2 when selected from Commander. CAT control behaves as expected for either radio.
3) With Radio 3 (SatPC32) selected in Commander, I go and start SatPC32.  SatPC32 controls the radio and works as expected.  At this point, the box in the upper right corner of Commander says Disconnected and Satellite name and mode are blank, as expected.

However - 
When I click Connect, nothing happens. Commander still says Disconnected.

Is there something in the configuration of SatPC32 I may have missed ?

Thanks es 73 de W0ZF


Re: Change of ClubLog status

Dave AA6YQ
 

+ AA6YQ comments below
As reported off-line, ClubLog's grid square map is very buggy.

1) It does not reflect grids (I've only checked on 6m) confirmed
or verified by card (QSL_RCVD= Y or V)
2) It does not show as "Verified" *any* grid that is not also
"Verified" for DXCC by LotW (App_DXKeeper_LotW_QSL_RCVD = V).

The first is completely unexpected while the second could be
foreseen since DXKeeper does not export a "Credit Granted" tag.

+ DXKeeper does include the CREDIT_GRANTED field when exporting an ADIF file using the Main window's "Export QSOs" tab, but does not include this field when uploading a QSO to ClubLog because ClubLog doesn't currently accept it. Michael G7VJR has indicated that he will extend ClubLog to accept CREDIT_GRANTED, at which point I will extend DXKeeper to include it when uploading a QSO to ClubLog.

     73,

            Dave, AA6YQ

6861 - 6880 of 209546