ClusterAPI.imageBuilder/packer/ova/windows/pvscsi/amd64/pvscsi.inf
Danny Bessems f2b0a5e7c7
Some checks failed
continuous-integration/drone Build is failing
Test dependencies
2023-02-22 21:24:42 +01:00

222 lines
4.1 KiB
INI

;pvscsi.inf
;This file contains the information required to load the driver for the VMware PVSCSI Controller
; Copyright (C) 2001 - 2019, VMware, Inc.
[version]
Signature="$Windows NT$"
Class=SCSIAdapter
ClassGuid={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%VMWARE%
DriverVer=08/02/2019,1.3.15.0
CatalogFile=pvscsi.cat
[ControlFlags]
ExcludeFromSelect = *
[SourceDisksNames]
1 = %DSKID1%,pvscsi.sys,,
[SourceDisksFiles]
pvscsi.sys = 1,,
[Manufacturer]
%VMWARE%=pvscsi,NTamd64.6.2
; ##################################################
; Other architectures are unsupported, as are older versions of Windows on all platforms.
[pvscsi]
[pvscsi.NTamd64.6.2]
%DEVICE%=DDInstall.x64.vista, PCI\VEN_15AD&DEV_07C0
; ##################################################
[DDInstall.x64.vista.NT]
CopyFiles=pvscsi.x64.CopyFiles
; ##################################################
[DDInstall.x64.vista.NT.HW]
AddReg=enableMSI.reg
Include=machine.inf
Needs=PciIoSpaceNotRequired
; ##################################################
[pvscsi.x64.CopyFiles]
pvscsi.sys,,,2
; ##################################################
[DDInstall.x64.NT.Services]
AddService=pvscsi,2,Service_Install.x64,EventLog_Install
[DDInstall.x64.vista.NT.Services]
AddService=pvscsi,2,Service_Install.x64,EventLog_Install
; ##################################################
[DestinationDirs]
pvscsi.x64.CopyFiles = 12
DefaultDestDir=12
; ##################################################
[Service_Install.x64]
DisplayName=%pvscsi.DiskName%
ServiceType=1 ; %SERVICE_KERNEL_DRIVER%
StartType=0 ; %SERVICE_BOOT_START%
ErrorControl=1 ; %SERVICE_ERROR_NORMAL%
ServiceBinary=%12%\pvscsi.sys
LoadOrderGroup=SCSI Miniport
; We need to force the use of \Driver\pvscsi32 as the driver object name,
; otherwise the crash dump driver loader functions cannot find the driver.
; StartName entry defined in the INF format is supposed to facilitate that,
; but at least on win2k3sp2-32 and win2k8-datacenter-32 the driver installer
; interpretes StartName as the name of the account to start the service under,
; which is an incorrect interpretation for SERVICE_KERNEL_DRIVER type. As a
; work around ObjectName registry entry is added directly using brute-force.
AddReg=busTypeSAS,pnpsafe_pci_addreg,vmware_installers_addreg
DelReg=driverObjectName.del
; ##################################################
[busTypeSAS]
HKR, "Parameters", "BusType", 0x00010001, 0x0000000A ; BusTypeSAS
[enableMSI.reg]
HKR, Interrupt Management,, %FLG_ADDREG_KEYONLY%
HKR, Interrupt Management\MessageSignaledInterruptProperties,, %FLG_ADDREG_KEYONLY%
HKR, Interrupt Management\MessageSignaledInterruptProperties, MSISupported, \
%FLG_ADDREG_TYPE_DWORD%, 1
HKR, Interrupt Management\MessageSignaledInterruptProperties, MessageNumberLimit, \
%FLG_ADDREG_TYPE_DWORD%, 1
[pnpsafe_pci_addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001
[vmware_installers_addreg]
HKR,, %pvscsi.installers.value.name%, %FLG_ADDREG_KEYONLY%, %pvscsi.installers.value.windows%
;; FLG_ADDREG_KEYONLY
HKR,, %pvscsi.installers.value.name%, 0x00010002, %pvscsi.installers.value.windows%
;; FLG_ADDREG_NOCLOBBER | FLG_ADDREG_TYPE_MULTI_SZ
[driverObjectName.del]
HKR, , "ObjectName"
[EventLog_Install]
AddReg = EventLog_AddReg
[EventLog_AddReg]
HKR,,EventMessageFile,%FLG_ADDREG_TYPE_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll"
HKR,,TypesSupported,%FLG_ADDREG_TYPE_DWORD%,7
[strings]
pvscsi.installers.value.name="vwdk.installers"
pvscsi.installers.value.windows="Windows"
pvscsi.DiskName="pvscsi Storage Controller Driver"
VMWARE="VMware, Inc."
DEVICE="VMware PVSCSI Controller"
DSKID1="VMware PVSCSI Controller Installation Disk 1"
FLG_ADDREG_KEYONLY = 0x00000010
FLG_ADDREG_TYPE_DWORD = 0x00010001
FLG_ADDREG_TYPE_EXPAND_SZ = 0x00020000
FLG_DELREG_MULTI_SZ_DELSTRING = 0x00018002