3.4.3 Use Net Rule

The syntax for the use entry is defined as follows:

use: REG_SZ : ComponentRole    {yes|no|none}    {yes|no|none}

ComponentRole

Can be one of service, transport, driver, or adapter.

A NIC driver identifies its use as driver.

yes|no|none

Optionally specifies whether a driver group name is used in place of specific driver dependencies, as one of the following values:

yes 

Specifies that this driver’s load order is dependent on the ServiceLoadOrder of the component to which it binds.

no

Specifies that this driver component is dependent specifically on underlying named drivers to which it binds. This is the assumed value if nothing is specified.

none 

Specifies that no dependencies should be generated for this driver.

yes|no|none

Optionally specifies whether transport group names are used in place of specific transport dependencies, as one of the following values:

yes

Specifies that this transport protocol’s load order is dependent on the ServiceLoadOrder of the component to which it binds.

no

Specifies this transport driver component is dependent specifically on underlying named components to which it binds. This is the assumed value if nothing is specified.

none

Specifies that no dependencies should be generated for this transport protocol.

NIC drivers typically specify only driver as the value of their respective use net rules.

Examples of the Use Net Rule

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

1. The NIC driver for the elnkii adapter has the entry
   use : REG_SZ : driver

2. The NIC driver for the ee16 adapter also has the entry
   use : REG_SZ : driver

3. The nbf transport has the entry
   use : REG_SZ : transport none none