Protocol Driver Entry and Initialization (Windows Embedded CE 6.0)

1/6/2010

The Device.exe file loads NDIS protocol drivers through the registry. You must set the registry values for the **HKEY_LOCAL_MACHINE\Drivers\BuiltIn\**MyDriver registry key. This key is commonly named after the customized driver and contains the subkeys that appear in the following table.

Subkey	Content	Description
DLL	Mydriver.dll	Name of your driver's dynamic-link library .dll file.
Order	dword:3	Value that determines when the driver is loaded. This value must be greater than the order value for NDIS.
Keep	dword:1	Set to 1 to have the driver load at boot time.
Entry	MyDriverInitialize	The entry point for initializing the driver, which will be called at boot time.

Note

Be 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 the NdisRegisterProtocol function within the MyDriverInitialize function.

To register a protocol driver as a stream interface driver, you must call the RegisterDevice function. For a list of the required entry points for stream interface driver DLLs, see Stream Interface Driver Development Concepts.

See Also

Reference

NdisRegisterProtocol
RegisterDevice

Concepts

Protocol Drivers
Stream Interface Driver Development Concepts