mirror of https://github.com/tongzx/nt5src
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
117 lines
3.4 KiB
117 lines
3.4 KiB
<html>
|
|
|
|
<head>
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
|
|
<meta name="ProgId" content="FrontPage.Editor.Document">
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
|
|
<title>New Page 1</title>
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<p>;<br>
|
|
; INF.TXT<br>
|
|
;<br>
|
|
; This file is part of the WMIFILT sample filter driver in the<br>
|
|
; Windows 2000 DDK. It is not a complete INF file.<br>
|
|
; It lists the sections of your INF file that you need to<br>
|
|
; change in order to have a filter driver loaded for your device.<br>
|
|
;<br>
|
|
<br>
|
|
<br>
|
|
[Manufacturer]<br>
|
|
"ThisVendor"=THIS_VENDOR<br>
|
|
<br>
|
|
[THIS_VENDOR]<br>
|
|
;<br>
|
|
; Generic HID Interface (HidUsb as service)<br>
|
|
;<br>
|
|
"My device description" = My_Install_Section, INSERT_PNP_ID_HERE<br>
|
|
<br>
|
|
<br>
|
|
<br>
|
|
[My_Install_Section.NT]<br>
|
|
;<br>
|
|
; This section name's prefix matches 'My_Install_Section' above.<br>
|
|
; The appended ".NT" indicates Windows NT -specific processing.<br>
|
|
;<br>
|
|
Copyfiles = MyCopyFiles<br>
|
|
AddReg = MyAddReg<br>
|
|
<br>
|
|
<br>
|
|
[My_Install_Section.NT.HW]<br>
|
|
;<br>
|
|
; Because of the ".HW" suffix,<br>
|
|
; the 'AddReg' entries in this section apply to the device's<br>
|
|
; hardware key (rather than the software key, as usual).<br>
|
|
;<br>
|
|
AddReg = My_HW_AddReg<br>
|
|
<br>
|
|
<br>
|
|
[MyCopyFiles]<br>
|
|
; mydriver.sys<br>
|
|
wmifilt.sys<br>
|
|
<br>
|
|
<br>
|
|
[MyAddReg]<br>
|
|
;<br>
|
|
; Insert regular (software-branch) registry entries here<br>
|
|
;<br>
|
|
<br>
|
|
;<br>
|
|
; Include the list of classes that you wish to show up as property <br>
|
|
; pages within the device manager. The list should be a comma separated<br>
|
|
; list of WMI class names that are specifed in the MOF for the driver<br>
|
|
;<br>
|
|
HKR,,"WmiConfigClasses",0x00000000,"Vendor_SampleClass4,Vendor_SampleClass6"<br>
|
|
<br>
|
|
;<br>
|
|
; Specify that wmiprop.dll should be a device co installer<br>
|
|
;<br>
|
|
HKLM,System\CurrentControlSet\Control\CoDeviceInstallers,{<***Your Class Guid
|
|
Goes Here***},0x00010008,"WmiProp.dll,WmiPropCoInstaller"<br>
|
|
<br>
|
|
<br>
|
|
[My_Install_Section.NT.Services]<br>
|
|
;<br>
|
|
; The inf should already include a service entry for the device class.<br>
|
|
; It'll look something like the line below. Keep that line in the inf.<br>
|
|
;<br>
|
|
; AddService = MyDriver,2,My_Service<br>
|
|
<br>
|
|
; This is the filter service we're adding.<br>
|
|
AddService = FilterService,,Filter_Service_Inst<br>
|
|
<br>
|
|
<br>
|
|
<br>
|
|
[My_HW_AddReg]<br>
|
|
;<br>
|
|
; This HW-branch AddReg section adds values to the hardware-branch<br>
|
|
; registry key of the device (under HKLM\System\CurrentControlSet\Enum).<br>
|
|
;<br>
|
|
; "LowerFilters" and "UpperFilters" are special values that indicate<br>
|
|
; to the kernel that one or more filter drivers should be loaded along<br>
|
|
; with the driver for this device.<br>
|
|
;<br>
|
|
; You may also include other values here. These values can be read<br>
|
|
; by the driver. The 'SampleFilterParam' value is read by the filter.sys<br>
|
|
; sample driver as an example.<br>
|
|
;<br>
|
|
HKR,,"LowerFilters",0x00010000,"FilterService"<br>
|
|
; or HKR,,"UpperFilters",0x00010000,"FilterService"<br>
|
|
HKR,,"SampleFilterParam",0x00010001,512<br>
|
|
<br>
|
|
<br>
|
|
[Filter_Service_Inst]<br>
|
|
DisplayName = "Filter Service"<br>
|
|
ServiceType = 1 ;%SERVICE_KERNEL_DRIVER%<br>
|
|
StartType = 3 ;%SERVICE_DEMAND_START%<br>
|
|
ErrorControl = 0 ;%SERVICE_ERROR_IGNORE%<br>
|
|
ServiceBinary = %12%\wmifilt.sys<br>
|
|
LoadOrderGroup = extended base<br>
|
|
<br>
|
|
</p>
|
|
|
|
</body>
|
|
|
|
</html>
|