Intermediate Driver Query and Set Operations (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.

After it has successfully bound to an underlying miniport driver and initialized its virtual miniports, an intermediate driver queries the operating characteristics of the underlying miniport driver and sets its own internal state. If appropriate, the intermediate driver also negotiates such parameters as lookahead buffer size for the binding with the underlying miniport driver. An intermediate driver with a connectionless lower edge accomplishes this by calling NdisRequest. An intermediate driver with a connection-oriented lower edge accomplishes this by calling NdisCoRequest.

An intermediate driver can also receive query and set requests from higher level drivers through its MiniportQueryInformationand MiniportSetInformationfunctions, respectively. The driver can either respond to those requests or pass them down to the underlying driver. How an intermediate driver responds to queries and sets depends on the implementation.

Note   The behavior of intermediate drivers can also be affected by the power state of the virtual miniport and the underlying miniport driver. To learn more about the effects of the power state on query and set operations, see Handling a Set Power Request.

 

The Network Driver Reference contains information about all the general, connection-oriented, nonmedia-specific OIDs and about required media-specific OIDs of interest to intermediate driver developers.

The following topics provide additional information about issuing and responding to quries and sets in an intermediate driver:

Issuing Set and Query Requests from an Intermediate Driver

Responding to Sets and Queries in an Intermediate Driver

 

 

Send comments about this topic to Microsoft