3.4.4 BindForm Net Rule

The syntax for the bindform entry is defined as follows:

bindform : REG_SZ: ObjectName    [yes|no] [yes|no]    [container|simple|streams]

ObjectName 

Specifies the name of the object in the Windows NT namespace. This name must be unique so that it can be exported.

yes|no

The initial yes XOR no specifies whether the binding information will appear in this component's Linkage key of the registry. A value must be explicitly specified.

The subsequent yes XOR no specifies whether the device name appears in binding strings generated by the binding engine. A value must be explicitly specified. NIC drivers always select no because NIC driver names never appear as the …\Linkage\Export value for such a driver. Instead, a NIC driver exports the name(s) of the NIC(s) that the driver controls as described later in Section 3.5.

container|simple|streams 

Specifies how binding string names are formed for the …\Linkage\Export and …\Linkage\Bind entries. A value must be explicitly specified, as follows:

container

Indicates that component-supplied values in the Linkage key are expressed as \Device\ComponentX\ComponentY where the components are delimited by backslashes. If this option is selected, the Object Manager must be called to create container objects of this name format.

simple

Indicates that component-supplied values in the Linkage key are expressed as \Device\ComponentX_ComponentY where the components are delimited by underscores. If this option is selected, the Object Manager is not called to create names.

streams

Indicates that the word Streams appears in the binding string immediately ahead of the component that selected this option.

Examples of Bindform Net Rule

The following examples show how bindform is specified in the registry for certain system network drivers, some also shown in the preceding use rule examples, under their respective ..\NameOfComponent\NetRules keys:

1. The NIC driver for the ee16 adapter has the entry
   bindform : REG_SZ: “Ee16Sys” yes no container

2. The Nbf transport has the entry
   bindform : REG_SZ : “Nbf” yes yes simple

3. The TCP/IP transport has the entry
   bindform : REG_SZ : “Tcpip” yes yes container