[Bug 45510] Sentinel HASP Runtime v6.6-7.8 driver installer reports Windows error 1053 when starting the 32-bit hardlock kernel driver service (custom imports resolver fails to locate some ntoskrnl exports)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=45510

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Sentinel HASP Runtime       |Sentinel HASP Runtime
                   |(driver) 6.6-7.8 installer  |v6.6-7.8 driver installer
                   |fails, reports 'Error when  |reports Windows error 1053
                   |starting the hardlock       |when starting the 32-bit
                   |service' (custom imports    |hardlock kernel driver
                   |resolver fails to locate    |service (custom imports
                   |some ntoskrnl exports)      |resolver fails to locate
                   |                            |some ntoskrnl exports)
             Status|NEW                         |RESOLVED
      Fixed by SHA1|                            |a1cdcc5290618c00d73e7a71aaa
                   |                            |38897ec501138
                URL|https://supportportal.gemal |https://web.archive.org/web
                   |to.com/csm/?id=kb_article&s |/20201128131118/http://www.
                   |ys_id=a459d328dba207c8fe0af |cadshop.ru/drivers/HASPDINS
                   |f3dbf9619ce                 |T_7.32.exe
         Resolution|---                         |FIXED

--- Comment #13 from Anastasius Focht  ---
Hello folks,

@ comment #10

--- quote ---
Present at version 3.17
--- quote ---

Although it doesn't matter that much I found the exact Sentinel HASP runtime
version you've used here:

www.cadshop.ru/drivers/HASPDINST_7.32.exe

Snapshot:

https://web.archive.org/web/20201128131118/http://www.cadshop.ru/drivers/HAS...

The 32-bit Hardlock driver exhibits a different set of problems versus the
64-bit driver (default WoW64 prefix) which loads even with older Wine 3.x
releases (no error from entry point / driver init).

--- snip ---
[28/11/2020-15:40:39]check action type
 ../hhlinst.c,2070,
[28/11/2020-15:40:39] hardlock.sys VER 0 ../instdrv.c,1956,
[28/11/2020-15:40:39]InstallService Hardlock. ../instdrv.c,629,
[28/11/2020-15:40:39]service Hardlock newer 0 serviceexist 0. ../instdrv.c,668,
[28/11/2020-15:40:39]start service Hardlock. ../instdrv.c,742,
[28/11/2020-15:40:39]UnInstallService hardlock. ../instdrv.c,825,
[28/11/2020-15:40:39]UnInstallService hardlock end status 0. ../instdrv.c,938,
[28/11/2020-15:40:45]Error when starting the  hardlock service with parameters
1168 1053 1. ../instdrv.c,774,
[28/11/2020-15:40:45]Windows error 1053
--- snip ---

That particular error 1053 was fixed by
https://source.winehq.org/git/wine.git/commitdiff/a1cdcc5290618c00d73e7a71aa...
("ntoskrnl: Build with msvcrt."), part of Wine 4.11 release.

Thanks Alexandre.

The driver still fails after that commit but with a different error class
(ZwLoadDriver -> c000009a). Let's not recycle bugs.

--- snip ---
...
[28/11/2020-15:39:37]check action type
 ../hhlinst.c,2070,
[28/11/2020-15:39:37] hardlock.sys VER 0 ../instdrv.c,1956,
[28/11/2020-15:39:37]InstallService Hardlock. ../instdrv.c,629,
[28/11/2020-15:39:37]service Hardlock newer 0 serviceexist 0. ../instdrv.c,668,
[28/11/2020-15:39:37]start service Hardlock. ../instdrv.c,742,
[28/11/2020-15:39:37]UnInstallService hardlock. ../instdrv.c,825,
[28/11/2020-15:39:37]UnInstallService hardlock end status 0. ../instdrv.c,938,
[28/11/2020-15:39:43]Error when starting the  hardlock service with parameters
1168 1450 1. ../instdrv.c,774,
[28/11/2020-15:39:43]Windows error 1450
--- snip ---

I will create additional bugs as needed or reference on existing ones.

$ sha1sum HASPDINST_7.32.exe 
96520c7e2bdc40a232daca01d6edbd7aa3f162ba  HASPDINST_7.32.exe

$ du -sh HASPDINST_7.32.exe 
16M    HASPDINST_7.32.exe

$ wine --version
wine-4.10-171-ga1cdcc52906

$ wine --version
wine-5.22-196-g2001705a3f0

Regards