TC USB cable server process does not terminate

[Hacker]

Hi,
TC 9.22a x64 on Windows 7 x64 and Windows 10 x64.

Run

Code: Select all

%COMMANDER_EXE% /S=P:USB

Click OK (if you don't have an Easy Transfer USB cable) or Abort (if you do).
The USB Server window disappears but the process stays running in the task manager.
Repeat to your liking.

Roman

[petermad]

I can confirm this but only with 64bit TC 9.22a not with the 32 bit version (only tested under Win 7 so far).

I see the bug the first time in TC 9.20 beta 5

[ghisler(Author)]

I will check it, thanks.

[petermad]

2ghisler(Author)
I just tried loading the parallel port driver using:

Code: Select all

%COMMANDER_EXE% /S=P:LPT1

The samme occurs here, the process does not terminate - and again it is the 64bit TC that is affected.

----------------------

BTW - if I (under Win 7) try to install the parallel port driver with either:

Code: Select all

cm_NTinstallDriver

or

Code: Select all

TOTALCMD64.EXE /INSTALLDRIVER

I get the message:
---------------------------
C:\totalcmd\cglpt64.sys
---------------------------
Could not start driver!
---------------------------
OK
---------------------------

And thereafter I get this message (the first time I try) http://madsenworld.dk/tcmd/lptdriver.png - saying that the driver cgltp64.sys is not signed. If I check the cgltp64.sys its certificate is valid from 25th of may 2016 to 25th of may 2017.

I might add that the PC that I am testing on does not have an LPT1 port.

[Dalai]

If I check the cgltp64.sys its certificate is valid from 25th of may 2016 to 25th of may 2017.

That doesn't matter. Certificates have a certain validity time span. After that they can still be considered valid if the system can verify the certificate chain, i.e. if the CAs that signed the specific certificate are still valid.

Example: CGLPT64.sys of TC 8.52a is signed with a certificate that was valid from 2010-05-11 to 2011-05-12, but my system still considers it valid because the signing CAs (VeriSign Class 3 Code Signing 2009-2 CA and VeriSign Class 3 Public Primary CA) are still valid. If the Root CA becomes invalid, the file's signature will become invalid, too.

The one important thing is that certificate signatures often can only be verified with an active internet connection. So if your system doesn't have internet access it will try to verify the certificates with the Root CAs installed on the system, but these might be old and expired.

PS: The whole signature stuff is not easy to understand, especially for normal users.

Regards
Dalai

[petermad]

So if your system doesn't have internet access

But my system is always online - so that cannot be the case.

[Dalai]

2petermad
Well, does your system see the file's certificate as valid (despite the validity time span)? If so, there's nothing to worry about.

Regards
Dalai

[petermad]

2petermad
Well, does your system see the file's certificate as valid (despite the validity time span)? .

The the context menu says: "This digital signature is OK" (translated) ( http://madsenworld.dk/tcmd/lptsignatur.png )

So why do I get this: http://madsenworld.dk/tcmd/lptdriver.png when I try to use the driver?

Translation of screenshot:

A digitally signed driver for Windows is required

A recently installed program tried to install a driver which is not signed. This version of Windows requires that all drivers has a valid digital signature.
The driver is not available and the program that uses the driver might not work correctly

Remove the program or the unit that uses the driver and go to the suppliers support website to get a digitally signed driver.

Driver: Ghisler Parallel Driver
Service: cglpt64
Supplier: Ghisler Software GmbH
Location: C:\Windows\System32...\cglpt64.sys

[Dalai]

2petermad
OK, so the file's signature is valid (I assume both of them, sha1 and sha256). Unfortunately I'm not sure as to why the system complains about a missing signature. Perhaps an additional .cat file is required? That's what hardware drivers are usually shipped with (.inf, .sys and .cat).

Regards
Dalai

[umbra]

If I remember correctly, drivers must be signed also by Microsoft or one of its partners with a special certificate. There are even multiple boot options for this reason in Windows - one will allow loading drivers with any valid certificate while the other allows even unsigned drivers.

[petermad]

I tried the LPT Port driver under other OS's:
On another Windows 7 PC I get the same message: http://madsenworld.dk/tcmd/lptdriver.png
On my Windows 8.1 PC I get a similar message: http://madsenworld.dk/tcmd/lptdriverw81.png
On my Windows 10 and my Windows XP PC's - I don't get the message.

[ghisler(Author)]

Only certain drivers need to be countersigned by Microsoft, like display drivers (WHQL).

Maybe your system is configured to only accept SHA256-signed drivers? I have signed the driver with my current certificates (SHA1 and SHA256).
Can you try it please?
https://www.totalcommander.ch/win/cglptnt.zip

[petermad]

Can you try it please?
https://www.totalcommander.ch/win/cglptnt.zip

Tried this - but I still get the same message: http://madsenworld.dk/tcmd/lptdriver.png

What I do (all with TC 9.22a x64 in elevated mode):
1. First I use the cm_NTinstallDriver command to install the driver - after a while I get this message:

---------------------------
C:\totalcmd\cglpt64.sys
---------------------------
Could not start driver!
---------------------------
OK
---------------------------

2. Then i run the command: %COMMANDER_EXE% /S=P:LPT1
And I get this message:

---------------------------
cglpt64
---------------------------
Could not load port driver!
---------------------------
OK
---------------------------

And then this message:

---------------------------
Total Commander
---------------------------
Connect failed!
---------------------------
OK
---------------------------

3. Then I run the command: cm_NTremoveDriver
and get this message:

---------------------------
Total Commander
---------------------------
Driver removed OK!
---------------------------
OK
---------------------------

4. Then I do step 1 again - and after a while I get the http://madsenworld.dk/tcmd/lptdriver.png message.

It is only when I have run the cm_NTremoveDriver command and then run the cm_NTinstallDriver that I get the bessage.

[ghisler(Author)]

I'm also getting an error now that the service cannot be started. Unfortunately it looks like Microsoft has tightened security, so my driver can no longer be loaded. Driver certification can cost thousands of dollars with no guarantee that it will be approved, so I will have to remove this function. Most PCs no longer have a parallel port anyway, so the USB port connection is a good alternative.

[petermad]

2ghisler(Author)

so I will have to remove this function

Will it not work under older OS's (Windows 95, 98, NT)? - if that is the case, I think you should keep the function, but make it give a message if it is not supported by the Users OS.