|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.|
All NDIS miniport and intermediate drivers must provide a DriverEntryfunction. When a miniport driver is loaded, NDIS calls DriverEntry, which creates an association between the miniport driver and the NDIS library, and registers the miniport with NDIS.
The DriverEntryfunction requires the following syntax:
NTSTATUS DriverEntry( IN PDRIVER_OBJECT pDriverObject_ , IN PUNICODE_STRING pRegistryPath_ );
The following parameters are passed into the DriverEntryfunction:
The DriverEntryfunction must call the NdisMInitializeWrapperfunction and then the NdisMRegisterMiniportfunction. DriverEntryfirst calls NdisMRegisterMiniportwith the parameters that are passed to DriverEntry, which returns a wrapper handle. DriverEntrythen passes the handle to NdisMRegisterMiniport.
Windows CE does not support the common network .inf file format for dynamic installation and registry configuration of miniport drivers that are used in Windows NT. Instead, Windows CE uses the registry for dynamic installation and binding of device drivers. Therefore, your driver installation program must make sure to create the appropriate registry settings for your miniport driver in the Windows CE registry.
The following diagram shows the process for registering a miniport driver and initializing the NDIS library.
Last updated on Tuesday, July 13, 2004