Enhanced Run-time Reconfiguration Abilities

NDIS 6.0 introduced the ability to pause and restart a driver stack without having to tear down the stack and build a new one. All NDIS 6.0 and later drivers must support pause and restart services.

Pausing the stack eliminates synchronization problems by putting all drivers in a known state before reconfiguration occurs. The ability to pause also gives NDIS the opportunity to query driver characteristics, and reconfigure other characteristics of the stack.

NDIS can pause a driver stack, for example, to temporarily stop data flow before performing a Plug and Play operation, such as adding or removing a filter driver, or binding or unbinding a protocol driver. NDIS restarts the stack after the reconfiguration takes place.

Miniport and filter drivers handle pause and restart services through function interfaces. Protocol drivers handle pause and restart services through Plug and Play event notifications.

For more information about pause and restart operations, see Driver Stack Management.

 

 

Send comments about this topic to Microsoft

Show:
© 2015 Microsoft