Indicating Miniport Driver Status (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.

To report a change in the status of a connection-oriented NIC or a change in the status of a particular VC active on the NIC, a connection-oriented miniport driver calls NdisMCoIndicateStatus. If the miniport driver is reporting a change in the status of a particular VC, it supplies an NdisVcHandlethat identifies the VC.

The following figure shows a miniport driver indicating status.

The next figure shows an MCM driver indicating status.

The call to NdisMCoIndicateStatuscauses NDIS to call the ProtocolCoStatusfunction of all protocol drivers bound to the NIC if no NdisVcHandleis supplied. If the miniport driver supplies an NdisVcHandle, NDIS calls only those protocol drivers with which the miniport driver shares the VC handle. When an MCM driver calls NdisMCoIndicateStatus, NDIS calls the ProtocolCoStatusfunction only of bound connection-oriented clients since there is no call manager bound to the MCM driver.

The ProtocolCoStatusfunction can log the change in status and possibly take corrective action. For example, when a miniport driver calls NdisMCoIndicateStatusto report operational problems in its NIC, a protocol might call NdisReset(or NDIS itself can call the miniport driver's MiniportResetfunction) to try restoring the NIC to a working condition (see Reset).

 

 

Send comments about this topic to Microsoft