MUX Intermediate Driver Installation (NDIS 5.1)
Note NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.
This topic provides an overview of MUX intermediate driver installation issues. For additional information about the structure of intermediate driver INF files, see Installation Requirements for Network MUX Intermediate Drivers.
A MUX Intermediate driver requires two INF files. The protocol INF file defines the installation parameters for the protocol lower edge. The miniport INF file defines the installation parameters for the virtual miniport upper edge. Set the ClassINF file entry to Netin the virtual miniport INF file and NetTransin the protocol INF file. A sample Classentry for the protocol INF file follows:
Class = NetTrans
The DDInstallsection in a MUX intermediate driver INF file must have a Characteristicsentry. Define the Characteristicsentry in your protocol INF file as demonstrated in the following sample:
Characteristics = 0x80
NCF_HAS_UI (0x80) is required to enable custom property pages, which in this case is the notify object
Define the Characteristicsentry in your miniport INF file as demonstrated in the following sample:
Characteristics = 0x21
The Characteristicsvalue 0x21 indicates the NCF_VIRTUAL (0x1) and NCF_NOT_USER_REMOVABLE (0x20) flags are set. NCF_VIRTUAL specifies that the device is a virtual adapter. NCF_NOT_USER_REMOVABLE is optional and specifies that the user cannot remove the intermediate driver. If you want to hide the virtual miniport from the user (you should not do this if your user must install devices manually) you can define the NCF_HIDDEN (0x8) flag. The NCF_* flags are defined in netcfgx.h. For more information about the Characteristicsentry and NCF_* flags, see Ddinstall Section.
The DDInstallsection of the protocol INF file for a MUX intermediate driver must include an Addregdirective for an Ndikey. For more information, see Adding Service-Related Values to the Ndi Keyand DDInstall.Services Section.
In addition to the INF files, you must also provide a notify object with a MUX Intermediate driver. The notify object is responsible for installation of virtual miniports. Reference the notify object with the ComponentDllentry in the protocol INF as follows:
HKR, Ndi, ComponentDll, , mux.dll
The user installs the protocol INF file which defines configuration parameters, copies installation files and also installs the notify object DLL. The user adds virtual miniports through the user interface provided by the notify object. The miniport INF file should define the ExcludeFromSelectentry to prevent the user from installing the miniport INF file instead of the protocol INF file.
The protocol name registered by the driver must match the service name.
HKR, Ndi, Service, 0, MUXP
The UpperRangeand LowerRangeINF file entries determine the bindings for a MUX intermediate driver. The protocol INF file must define the protocol edge bindings as follows:
HKR, Ndi\Interfaces, UpperRange, 0, "noupper"
HKR, Ndi\Interfaces, LowerRange, 0, "ndis5"
The miniport INF file must define the upper edge bindings as follows:
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5"
HKR, Ndi\Interfaces, LowerRange, 0, "nolower"
You should replace "ndis5" in the preceding examples with the protocol bindings required by your driver. For more information about intermediate driver bindings and the UpperRange/ LowerRangeentries, see Intermediate Driver UpperRange And LowerRange INF File Entries.