Enabling and Disabling NDK Functionality
The *NetworkDirect keyword determines whether the miniport driver's NDK functionality can be enabled.
If this keyword value is set to 1 ("Enabled"), NDK functionality can be enabled.
If it is set to 0 ("Disabled"), NDK functionality cannot be enabled.
When the miniport driver is installed, its INF file sets this keyword value to 1 ("Enabled") by default. For more information, see INF Requirements for NDKPI.
After the miniport driver is installed, administrators can update the *NetworkDirect keyword value by setting a new value in the Advanced property page for the adapter. For more information about advanced properties, see Specifying Configuration Parameters for the Advanced Properties Page.
Note The miniport driver is automatically restarted after a change is made in the Advanced property page for the adapter.
This state change can be triggered by an OID_NDK_SET_STATE OID request, or by a success or failure in the adapter itself.
To enable or disable its NDK functionality, the miniport driver must send a NetEventNDKEnable or NetEventNDKDisable Plug and Play (PnP) event to NDIS.
To send the PnP event, the miniport driver calls the NdisMNetPnPEvent function, setting the NetPnPEvent member of the NET_PNP_EVENT_NOTIFICATION structure that the NetPnPEvent parameter points to as follows:
NetEventNDKEnable if NDK functionality is to be enabled.
NetEventNDKDisable if NDK functionality is to be disabled.
The NetEventNDKDisable PnP event triggers NDIS and upper layer drivers to start closing their opened NDK_ADAPTER instances over the adapter where the NDK functionality is being disabled. The PnP event will remain pending until all of the opened NDK_ADAPTER instances over the adapter are closed.
Build date: 11/16/2013