Topics

Install Problem (Constant Restore)

Carl Jón Denbow
 

I’m having problems installing on one Win10-64 machine.  DX Launcher installs, but then shows “Restore” next to its line.  And so with any other program, like DX Commander, that I install via Launcher.  If click on restore, it will go through the motions of reinstalling, but in the end it still says “Restore.” Something is obviously corrupt.  I’ve tried to uninstall and reinstall, but nothing changes.  Any suggestions are welcomed! — 73 de Carl N8VZ


================================
Carl Jón Denbow, Ph.D. 
Director of Communication Emeritus 
Ohio University 
Heritage College of Osteopathic Medicine 
Athens, Ohio 

================================

Dave AA6YQ
 

+ AA6YQ comments below

I’m having problems installing on one Win10-64 machine. DX Launcher installs, but then shows “Restore” next to its line. And so with any other program, like DX Commander, that I install via Launcher. If click on restore, it will go through the motions of reinstalling, but in the end it still says “Restore.” Something is obviously corrupt.

+ That's not correct.

+ If a DXLab application has not yet been installed, then the Launcher will display an Install button in that application's Action column (Configuration window, "DXLab Apps" tab)

+ If a DXLab application has been installed, but a more recent version is available, then the Launcher will display an Upgrade button in that application's Action column.

+ If a DXLab application has been installed and you are running the currently available version (or a more advanced version), then the Launcher will display an Restore button in that application's Action column.

+ Thus the presence of a Restore button in an application's Action column is not an indication of trouble:

<https://www.dxlabsuite.com/Launcher/Help/InstallUpgrade.htm>


I’ve tried to uninstall and reinstall, but nothing changes.

+ Unless there's an error message informing you that a library or component cannot be found, uninstalling and then reinstalling a DXLab application will not correct the problem at hand, but may confuse Windows into creating an even worse problem.

73,

Dave, AA6YQ

Carl Jón Denbow
 

OK, I was wrong about the significance of the Restore label.  I was having some problems with the program hanging (now solved), and I was not analyzing the situation correctly. Now, though, I have one remaining problem, when I click on Net Serv button in Commander, it simple changes focus to the main Commander screen.  I thought it was supposed  to pop up a dialogue box where you could enter a server address to match the one in another app, in this case WSJT-X.  When I run WSJT-X it says that it cannot communicate with DX Commander.  Any further help would be appreciated. -- 73 de Carl N8VZ

Carl Jón Denbow
 

Maybe this error log would help diagnose the problem:

2020-07-12 17:45:38.453 > Common.Terminate: CI-V Commander shutdown
 
2020-07-12 17:45:52     > CI-V Commander version 14.6.2
2020-07-12 17:45:52     > App.Path          : C:\DXLab\Commander
2020-07-12 17:45:52     > App.exe           : CI-V Commander
2020-07-12 17:45:52     > Module            : C:\DXLab\Commander\CI-V Commander.exe
2020-07-12 17:45:52     > Operating System  : Windows 10 Home (64-bit) build 18362
2020-07-12 17:45:52     > Locale ID         : 1033 (0x409)
2020-07-12 17:45:52     > ANSI CodePage     : 1252
2020-07-12 17:45:52     > OEM CodePage      : 437
2020-07-12 17:45:52     > Country           : United States
2020-07-12 17:45:52     > Language          : English
2020-07-12 17:45:52     > DecimalSeparator  : .
2020-07-12 17:45:52     > ThousandSeparator : ,
2020-07-12 17:45:52     > DXLab Apps        : 
2020-07-12 17:45:55     > Monitors          : 1
2020-07-12 17:45:55     > Monitor 1
2020-07-12 17:45:55     >    width          : 1600
2020-07-12 17:45:55     >    height         : 900
2020-07-12 17:45:55     >    dimensions     : (0, 0)-(1600, 900)
2020-07-12 17:45:55.869 > program error 339 in module TCPServerModule.Initialize: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
2020-07-12 17:45:55.885 > program error 339 in module CIVMain.Form_Load, State = 13: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
2020-07-12 17:46:05.654 > program error 339 in module CIVConfig.NetServCmd_Click: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

Dave AA6YQ
 

Is the file MSWINSCK.OCX present in your Commander folder?

If so, then please do the following:

1. if Commander is running, terminate it

2. using Windows Explorer, right-click the entry for

C:\DXLab\Commander\CI-V Commander.exe

and select "Run as Administrator" from the popup menu

3. after Commander starts and initializes, terminate it

4. direct the Launcher to start Commander; does Commander's Main window title bar indicate that entries have been added to its errorlog.txt file?

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Carl Jón Denbow
Sent: Sunday, July 12, 2020 1:48 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Install Problem (Constant Restore)

Maybe this error log would help diagnose the problem:


2020-07-12 17:45:38.453 > Common.Terminate: CI-V Commander shutdown

2020-07-12 17:45:52 > CI-V Commander version 14.6.2
2020-07-12 17:45:52 > App.Path : C:\DXLab\Commander
2020-07-12 17:45:52 > App.exe : CI-V Commander
2020-07-12 17:45:52 > Module : C:\DXLab\Commander\CI-V Commander.exe
2020-07-12 17:45:52 > Operating System : Windows 10 Home (64-bit) build 18362
2020-07-12 17:45:52 > Locale ID : 1033 (0x409)
2020-07-12 17:45:52 > ANSI CodePage : 1252
2020-07-12 17:45:52 > OEM CodePage : 437
2020-07-12 17:45:52 > Country : United States
2020-07-12 17:45:52 > Language : English
2020-07-12 17:45:52 > DecimalSeparator : .
2020-07-12 17:45:52 > ThousandSeparator : ,
2020-07-12 17:45:52 > DXLab Apps :
2020-07-12 17:45:55 > Monitors : 1
2020-07-12 17:45:55 > Monitor 1
2020-07-12 17:45:55 > width : 1600
2020-07-12 17:45:55 > height : 900
2020-07-12 17:45:55 > dimensions : (0, 0)-(1600, 900)
2020-07-12 17:45:55.869 > program error 339 in module TCPServerModule.Initialize: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
2020-07-12 17:45:55.885 > program error 339 in module CIVMain.Form_Load, State = 13: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
2020-07-12 17:46:05.654 > program error 339 in module CIVConfig.NetServCmd_Click: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Carl Jón Denbow
 

Dave, I followed all those steps, and in answer to your question (Step #4), there was no indication in the title bar of an addition to the errorlog.txt file.  So, what is the significance of that?  Tnxs & 73 de Carl N8VZ 

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I followed all those steps, and in answer to your question (Step #4), there was no indication in the title bar of an addition to the errorlog.txt file. So, what is the significance of that?

+ It means that when you ran Commander with Administrative privileges, it was able to install the Winsck component, which it employs to communicate with other applications via TCP and UDP. Subsequently running Commander without Administrative privileges succeeded because the Winsck component had been installed by the previous action.

+ This was necessary because your Windows system is configured to prevent an application like Commander from installing a component.

+ Does Commander now work correctly when started by the Launcher?

73,

Dave, AA6YQ

Carl Jón Denbow
 

Dave: I seem to be making progress, but I'm not quite there yet.  I can now open the NetServ dialogue box.  I've entered what I think is the correct information, but WSJT-X still reports that it is not communicating with DX Commander.   In Commander I had UPD IP Address as 127.0.0.1 and Port 12060; these are the defaults.  TCP is listed as 52000 for Base Port and 52002 for listening.  In WSJT-X I have 52002 listed for Network Server.  Does all of this look correct?  Tnxs & 73 de Carl N8VZ

Dave AA6YQ
 

+ AA6YQ comments below

Dave: I seem to be making progress, but I'm not quite there yet. I can now open the NetServ dialogue box.

+ That was previously impeded by Commander being unable to access the Winsck component.


I've entered what I think is the correct information, but WSJT-X still reports that it is not communicating with DX Commander. In Commander I had UPD IP Address as 127.0.0.1 and Port 12060; these are the defaults.

+ Those settings are irrelevant, as WSJT-X does not communicate with Commander via UDP.


TCP is listed as 52000 for Base Port and 52002 for listening. In WSJT-X I have 52002 listed for Network Server.

+ In the "CAT Control" panel on the Radio tab of the WSJT-X Settings window, leave the "Network Server" box empty.

+ Complete configuration instructions are here:

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect>

73,

Dave, AA6YQ

Carl Jón Denbow
 

Thank you very much, it's working now. The key was leaving the Network Server box empty.  I thought I had read somewhere to populate it as it had.  Wrong!  I really appreciate your help.  Now, I can get my WSPR operation running again! -- 73 de Carl N8VZ