Export (0) Print
Expand All

Registry Keys for Miniport Drivers (Windows Embedded CE 6.0)

1/6/2010

When a miniport driver is installed on a Windows Embedded CE–based platform, the setup application should create several registry keys to expose the miniport driver to Windows Embedded CE properly. Windows Embedded CE loads NDIS drivers listed within the HKEY_LOCAL_MACHINE\Comm key. Sub keys within this key are named for the corresponding miniport driver.

The following list shows the sub keys that are contained in each Miniport\ key:

Name Type Description

DisplayName

SZ

A user-friendly name for the driver

Group

SZ

The literal string "NDIS"

ImagePath

SZ

The name of the DLL containing the miniport driver

Linkage\Route

SZ

A set of Miniport Instance keys, separated by commas

Cxport\NoIdleTimerReset

SZ

If present and non-zero, prevents Windows Embedded CE from suspending while the adapter is plugged into the PC Card socket.

The value of the Linkage\Route key lists additional subkeys of the Comm key for each miniport instance. These subkeys in turn contain a set of keys that describes the parameters of that miniport instance. The following list shows the subkeys that are contained in each Miniport Instance key:

Name Type Description

DisplayName

SZ

A user-friendly description of the miniport instance

Group

SZ

The literal value "NDIS"

ImagePath

SZ

The name of the miniport driver's DLL

Parms

Sub key

Subkeys for the miniport driver's parameters

The following list shows the sub keys that are contained in each Miniport Instance\PARMS key:

Name Type Description

BusNumber

DWORD

The bus number for the miniport instance.

BusType

DWORD

The bus type of the miniport instance as defined by INTERFACE_TYPE

ProtocolsToBindTo

MULTI_SZ

Controls which protocols will be notified about the presence of the miniport adapter.

BusNumber values range from 0 to one less than the number of buses on a Windows Embedded CE–based platform. Valid BusType values are declared in the INTERFACE_TYPE enumeration in the Ceddk.h header file. Use the Miniport Instance\Parms key to store any miniport-specific values because this is the registry location that is accessed when miniport drivers call the NdisOpenConfiguration and NdisReadConfiguration functions. ProtocolsToBindTo lists the protocols that will be notified about the miniport adapter. If the first entry is "NOT", then all protocols except the ones listed will be notified. If this entry is not set, all protocols will be notified.

The following example shows the additional keys that a PC Card network adapter could have.

[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\NICs-R-Us Inc.-Super2000-E6FE]
  DLL="NDIS.DLL"
  Prefix= "NDS"
  Miniport="NE2000"

Ndis.dll sets values for the BusNumber and BusType keys for PC Card–based NICs. The BusNumber key contains the socket and function pair for the network adapter. The BusType key contains the value for the PC Card bus. Finally, if the card information structure (CIS) of the PC Card contains a network address value, Ndis.dll creates a HKEY_LOCAL_MACHINE\Comm\Miniport Instance\Parms\NetworkAddress key to store the network address.

Protocol binding for miniport drivers for PC Card–based NICs occurs automatically when the driver is loaded. Protocol binding for miniport drivers for built-in NICs is controlled by the registry keys stored within HKEY_LOCAL_MACHINE\Comm\IrDA\Linkage and HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage. Each of these Linkage keys should contain a single key called Bind. You can set the Bind key to a list of miniport instances that the corresponding protocol stack binds to. The following example shows the values that the registry could contain to enable the IrDA protocol stack to bind to the IrSIR miniport and the TCP/IP stack to bind to both the PPP and NE2000 miniports.

[HKEY_LOCAL_MACHINE\Comm]
  [IrDA\Linkage]
    Bind=multi_sz:"IrSir1"
  [Tcpip\Linkage]
    Bind=multi_sz: "PPP","NE20001"

Community Additions

ADD
Show:
© 2014 Microsoft