From
Native Wifi IHV Service[
^]
Installation
General
After the sample is compiled, you must copy the binaries on to the target system and associate them
with the matching Native Wifi-capable adapter. You can copy the binaries by adding an appropriate
CopyFiles directive in the DDInstall section in the INF file for installing the adapter. You can
associate the binaries by adding an appropriate AddReg directive in the DDInstall section in the INF file
for installing the adapter.
CopyFiles Directive
The CopyFiles Directive should name a File-List-Section. The contents of this section should have the
following:
IHVSpecifiedDLLName,,,2
IHVSpecifiedOtherFile,,,2
There should be an associated entry in the DestinationDirs section that specifies the destination to
copy the file to. This section should have a directive like one of the following:
File-List-Section= 11 ; \system32 directory
DefaultDestDir= 11 ; \system32 directory
AddReg Directive
The AddReg directive should name an Add-Registry-Section.
The contents of the Miniport INF file must include the following, in order for the correct IHV Service
to be started:
HKR,Ndi\IHVExtensions, ExtensibilityDLL,0,"%SystemRoot%\system32\IhvExt.dll"
This registry key is used to determine the location of the
IHVSample.dll.
HKR,Ndi\IHVExtensions,UIExtensibilityCLSID,0, "<CLSID>"
This registry key is used to determine the class ID of the COM interface that extends the 802.11
configuration UI.
HKR,Ndi\IHVExtensions,GroupName,0, "IHV provided group name"
HKR,Ndi\IHVExtensions, AdapterOUI, 0x00010001, 0x00123456
This registry key is used to verify the OUI when the profile is applied to the adapter. If the
AdapterOUI value is 0x??123456 in the registry, it needs to look like the following in the profile:
<OUIHeader>
<OUI>123456</OUI>
<type>??</type>
</OUIHeader>
Note that ?? stands for bits ignored.
HKR,Ndi\IHVExtensions, DiagnosticsID,0, "<Diagnostics ID GUID>"
Uninstallation Instructions
To uninstall this sample, you must undo the AddReg directive and undo the CopyFiles directive.