Specifying the Reflector in an INF File

To add the reflector (WUDFRd.sys) to the kernel-mode device stack, the INF file of a UMDF driver must include an AddService directive in an INF DDInstall.Services section. The reflector can be an upper filter, a lower filter, or the service for the device, depending on the configuration of the user-mode stack.

The following code example shows how the INF file for a UMDF function driver might add the reflector.


[Skeleton_Install.Services]
AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall

In this example, the driver specifies the 0x2 (SPSVCINST_ASSOCSERVICE) flag (ORed into the flags parameter above) to assign the reflector as the function driver in the kernel-mode device stack.

The AddService directive also sets the 0x000001f8 flags to prevent overwriting any preexisting configuration for the service. For more information about these flags, see the flags parameter of the AddService directive.

The following code example, taken from the WUDFVhidmini sample, shows an AddService directive for a UMDF filter driver.


[hidumdf.win8.NT.Services]
AddService=WUDFRd,0x000001f8,WUDFRD_ServiceInstall  
AddService=mshidumdf, 0x000001fa, mshidumdf.AddService

[WudfVhidmini_AddReg]
HKR,,"LowerFilters",0x00010008,"WUDFRd" ; FLG_ADDREG_TYPE_MULTI_SZ | FLG_ADDREG_APPEND

In this case, the mshidumdf service is associated with the FDO for the device stack, and the reflector is a lower filter.

Providing a service-install-section

The AddService directive references an service-install-section similar to the following code example. The ServiceType entry specifies 1 or 0x00000001, which indicates that the INF installs support for one or more devices. The StartType entry specifies when to start the driver. The ErrorControl entry specifies the level of error control that the driver provides. The ServiceBinary entry specifies the path to the binary (the reflector) for the service.


[WUDFRD_ServiceInstall]
DisplayName = "Windows Driver Frameworks - User-mode Driver Framework Reflector"
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\WUDFRd.sys

Specifying a unique service name

Although it is not required to do so, a UMDF driver that runs only on Windows 8 and later operating systems can specify a unique service name for the WUDFRd (reflector) service.

The following example shows how to specify a unique service name instead of WUDFRd.


[Echo_Install.NT.Services]
AddService=WudfEchoDriver,0x00000002,WUDFEchoDriver_ServiceInstall

[WUDFEchoDriver_ServiceInstall]
DisplayName = %WudfEchoDriverDisplayName%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WUDFRd.sys
StartName = \Driver\WudfRd


In the above example, the driver specifies a unique value for the service name in the AddService directive. (In this case, it's WudfEchoDriver, which is the name of the driver.) Next, the driver specifies a unique DisplayName value for the service. Finally, the driver adds the StartName entry and sets it to \Driver\WudfRd.

UMDF drivers cannot specify a unique service name for the reflector on operating systems earlier than Windows 8. If your driver specifies a unique service name but must also work on operating systems earlier than Windows 8, use operating system specific sections in the INF file, as shown in the following example.


[Manufacturer]
%MSFT% = Microsoft,NTx86.6.0,NTx86.6.2
[Microsoft.NTx86.6.0]
%Sensors.DeviceDesc% = Sensors_Install_VistaWin7,HID_DEVICE_UP:0020_U:0001
[Microsoft.NTx86.6.2]
%Sensors.DeviceDesc% = Sensors_Install_Win8,HID_DEVICE_UP:0020_U:0001
[Sensors_Install_VistaWin7]
--- Install the device this way on Vista/Win7 ---
[Sensors_Install_Win8]
--- Install the device in a different way on Win8 ---

If the reflector is not added, UMDF is never loaded. The device might start, but the host process is not present and the device will not operate properly.

 

 

Send comments about this topic to Microsoft

Anzeigen:
© 2014 Microsoft