Installation Requirements for Network Protocols

This topic summarizes the installation requirements for network protocols.

INF File Section	Status	Comments
Version Section	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.
INF DestinationDirs Section	Required	No network-specific requirements.
ControlFlags Section	Optional	No network-specific requirements.
INF Manufacturer Section	Required	No network-specific requirements.
Models Section	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.
DDInstall Section	Required	Characteristics entry Allowable values: NCF_HIDDEN NCF_NO_SERVICE NCF_NOT_USER_REMOVABLE NCF_HAS_UI
DDInstall.Services Section	Optional	No network-specific requirements.
Add-registry-sections	Required	Required: Creating the Ndi Key Specifying Binding Interfaces Allowable binding interfaces: UpperRange: netbios, ipx, tdi, winsock, noupper LowerRange: ndis5, ndisatm, nolower
	Optional	Setting static parameters for the component Requiring the Installation of Another Network Component Specifying service-related values Adding a HelpText Value Adding Registry Values for a Notify Object
Remove Section	Optional
Winsock Sections	Optional	For a protocol that provides a Winsock interface, a Winsock-install section is required and a Winsock-remove section is optional.
INF Strings Section	Required	No network-specific requirements.