Microsoft Windows CE 3.0  

NDIS Protocol Driver Initialization

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.

NDIS protocol drivers are loaded through the registry. You must set the registry values for the following registry key: HKEY_LOCAL_MACHINE\Drivers\BuiltIn\MyDriverThis key commonly is named after the customized driver and contains the subkeys that appear in the following table.

Subkey Contents
DLL "Mydriver.dll"
Order dword:3
Keep dword:1
Entry MyDriverInitialize
Note   Make sure to set the "Order" subkey to a value that causes the protocol driver to load after NDIS.

To register the protocol driver with NDIS, the driver should call NdisRegisterProtocolwithin the "MyDriverInitialize" function.

To register a protocol driver as a stream interface driver, you must call the RegisterDevicefunction. For a list of the required entry points for stream interface driverDLLs, see the Windows CE DDK.

 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved.