http://bugs.winehq.org/show_bug.cgi?id=26792
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |focht@gmx.net Summary|Sentinel Protection: Fails |Sentinel Protection |to install |Driver/Service installer | |fails (needs | |"HKLM\SYSTEM\CurrentContr | |olSet\Control\VirtualDevi | |ceDrivers" registry key | |present) Ever Confirmed|0 |1
--- Comment #6 from Anastasius Focht focht@gmx.net 2012-02-08 15:46:45 CST --- Hello,
confirming.
--- snip --- ... 0034:trace:msi:ACTION_CustomAction Handling custom action L"MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9" (1 L"New_Binary.B391C188_6953_11D4_82CB_00D0B72E1DB9" L"MakeVDDRegEntry") 0034:trace:msi:HANDLE_CustomType1 Calling function L"MakeVDDRegEntry" from L"C:\users\focht\Temp\msief35.tmp" ... 0056:Call KERNEL32.LoadLibraryW(00c674d4 L"C:\users\focht\Temp\msief35.tmp") ret=7ecd3792 0056:Ret KERNEL32.LoadLibraryW() retval=008b0000 ret=7ecd3792 ... 0056:trace:msi:ACTION_CallDllFunction calling L"MakeVDDRegEntry" ... 0056:Call advapi32.RegOpenKeyExA(80000002,008c9578 "SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers",00000000,000f003f,0124e580) ret=008b2be1 0056:Ret advapi32.RegOpenKeyExA() retval=00000002 ret=008b2be1 0056:Call user32.MessageBeep(00000000) ret=008b2bed 0056:Ret user32.MessageBeep() retval=00000001 ret=008b2bed ... 0056:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"1: PDINSTALL 2: MakeVDDRegEntry 3: Failed to add entry! " ... 0034:err:msi:ITERATE_Actions Execution halted, action L"MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9" returned 1603 --- snip ---
Adding the following registry key prior running installer makes the services installer succeed.
--- snip --- $ wine reg add "HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers" --- snip ---
The installer adds "rnbovdd.dll" to "VDD" value (REG_MULTI_SZ) probably for supporting 16 bit legacy apps.
VDDs are outdated technology from NTVDM era and won't work anyway.
--- quote --- Windows NT Virtual MS-DOS Machines
In Windows NT, each MS-DOS-based application and 16-bit Windows-based applications run in a Windows NT virtual MS-DOS machine (NTVDM), a single-threaded process that supports 16-bit applications in a 32-bit environment. Windows NT includes the necessary virtual device drivers (VDDs) for the mouse, keyboard, printer, COM ports, and network support. The VDDs are loaded into every VDM based on values stored in the Registry. Information about VDDs is found in the following Registry path:
HKEY_LOCAL_MACHINE \System \CurrentControlSet \Control \VirtualDeviceDrivers
The system manages any changes to the VDD entries automatically when you add a device driver by using Windows NT Setup. --- quote ---
Also: http://support.microsoft.com/kb/254914
After installation the following services run through "autostart" service type:
--- snip --- focht 9550 1 0 22:24 ? 00:00:00 C:\Program Files\Common Files\SafeNet Sentinel\Sentinel Protection Server\WinNT\spnsrvnt.exe focht 9562 1 0 22:24 ? 00:00:00 C:\Program Files\Common Files\SafeNet Sentinel\Sentinel Keys Server\sntlkeyssrvr.exe focht 9569 1 5 22:24 ? 00:00:10 C:\Program Files\Common Files\SafeNet Sentinel\Sentinel Security Runtime\sntlsrtsrvr.exe focht 9613 1 0 22:24 ? 00:00:00 C:\windows\system32\winedevice.exe Sentinel --- snip ---
$ sha1sum SPI761W_RC2.iso fda3dd95cdd73dd24344441d7849d1ec349e0aee SPI761W_RC2.iso
$ wine --version wine-1.4-rc2-61-g93ed8a0
Regards