Installation Requirements for Network MUX Intermediate Drivers
This topic summarizes the installation requirements for network MUX intermediate drivers. For more information about installation requirements for MUX intermediate drivers, see Installing an Intermediate Driver.
Two INF files are required to install a network MUX intermediate driver :
Driver protocol ( Class= NetTrans)
Driver device ( Class= Net)
Protocol INF File for a Network MUX Intermediate Driver
INF File Section | Status | Comments |
---|---|---|
Required |
Class= NetTrans ClassGuid= {4D36E975-E325-11CE-BFC1-08002BE10318} |
|
INF SourceDisksNames Section and INF SourceDisksFiles Section |
Required if ... |
Required if the INF file is not distributed with Windows 2000. If the INF file is distributed with Windows 2000, a LayoutFile entry must be specified in the Version section, and the SourceDisksNames and SourceDisksFiles sections are not used. No network-specific requirements. |
Required |
No network-specific requirements. |
|
Optional |
No network-specific requirements. |
|
Required |
No network-specific requirements. |
|
Required |
The hw-id should consist of a provider name followed by an underscore and a manufacturer name or the product name--for example: MS_DLC. |
|
Required |
Characteristics entry: NCF_HAS_UI is required. The device INF must be copied to the system INF directory, see Copying INFs. |
|
Optional |
No network-specific requirements. |
|
Required |
Creating the Ndi Key UpperRange: noupper LowerRange: ethernet, atm, tokenring, serial, fddi, baseband, broadband, arcnet, isdn, localtalk, wan |
|
Optional |
Setting static parameters for the component Requiring the Installation of Another Network Component |
|
Optional |
||
Required |
No network-specific requirements. |
Device INF File for a Network MUX Intermediate Driver
INF File Section | Status | Comments |
---|---|---|
Required |
Class= Net ClassGuid= {4D36E972-E325-11CE-BFC1-08002BE10318} |
|
Required |
This section must contain an ExcludeFromSelect entry for the device. |
|
Required |
No network-specific requirements. |
|
Required |
The hw-id should consist of a provider name followed by an underscore and a manufacturer name or the product name--for example: MS_DLC. |
|
Required |
Characteristics entry: NCF_VIRTUAL is required. NCF_HIDDEN and NCF_NOT_USER_REMOVABLE are optional. |
|
Required |
No network-specific requirements. |
|
Required |
Creating the Ndi Key Specifying service-related values Allowable binding interfaces: UpperRange: ndis5, ndisatm, ndiswan, ndiscowan, noupper, ndis5_atalk, ndis5_dlc, ndis5_ip, ndis5_ipx, ndis5_nbf, ndis5_streams LowerRange: nolower |
|
Optional |
||
Required |
No network-specific requirements. |