TC USB cable server process does not terminate

[Dalai]

Well, I think that if someone needs this feature he/she will be able to use an older version of TC. For me it doesn't make sense to partly support a feature. Then again, cm_EditPermissionInfo should have been either removed a long time ago or adapted to work on newer versions of Windows.

Regards
Dalai

[petermad]

2Dalai

Then again, cm_EditPermissionInfo should have been either removed a long time ago or adapted to work on newer versions of Windows.

The same for cm_EditAuditInfo and cm_EditOwnerInfo

[Usher]

Well, I have already proposed legacy free, fully Unicode Total Commander X:
https://www.ghisler.ch/board/viewtopic.php?f=6&t=52739&p=356503&hilit=fully+Unicode+Total+Commander+X#p356503

[ghisler(Author)]

Good news: I found out that the driver does work when signed with my old (SHA1 only) certificate. Since the driver wasn't changed since then, it's sfw to use it instead of the one signed with my new certificate. Apparently Microsoft allows legacy drivers which didn't get any updates. I have tested it on Windows 7 and 10.

Download here:
https://www.totalcommander.ch/win/cglptnt_old.zip

[petermad]

I can confirm thet the driver from https://www.totalcommander.ch/win/cglptnt_old.zip does not give the https://madsenworld.dk/tcmd/lptdriver.png error message (Windows 7).

I cannot say if the driver actually works, since I don't have any computers with printer ports.

[petermad]

With TC 9.5b2 i no longer get these messages: http://madsenworld.dk/tcmd/lptdriver.png and https://madsenworld.dk/tcmd/lptdriverw81.png

[ghisler(Author)]

Yes, that's because I reverted to the drivers signed with my older certificate. Windows 10 accepts these old certs, but not the newer ones: They only accept Extended Validation certificates now for driver signing, but the old certs stay valid for compatibility reasons. This isn't a problem because the drivers were unchanged, only the signature was changed.

[Hacker]

The original problem is fixed as well, thank you!

Roman