|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
Windows CE 3.0 provides protocol drivers for TCP/IP, PPP, and IrDA. A protocol driver exports a set of Protocol Xxxfunctions at its lower edge. It communicates with NDIS to send and receive network packets and to bind to an underlying miniport network adapter driver or intermediate NDIS driver that exports a Miniport Xxxinterface at its upper edge.
Protocol drivers that communicate with underlying NDIS drivers call NDIS library functions to send and receive packets. To send a packet to an underlying NDIS driver, a protocol driver must call the NdisSendfunction. Unlike Windows NT, Windows CE 3.0 does not support the NdisSendPacketsfunction, which allows for multiple packets to be sent to underlying drivers. To forward a request to the underlying driver that it query the capabilities or status of its network adapter or that it set the state of its network adapter, a protocol driver must call the NdisRequestfunction.
Windows CE NDIS protocol drivers are exposed to applications through the Windows Sockets (Winsock) API. In the Windows CE protocol-driver architecture, a protocol driver communicates with the overlying Winsock APIs through a private interface. The NDIS protocol driver uses the NDIS interface to communicate with the underlying miniport driver and bind to the network adapter.
Last updated on Tuesday, July 13, 2004