INFO: Setting LowerRange for NDIS Protocol Drivers in Windows ME (282778)


The information in this article applies to:

  • Microsoft Windows ME Driver Development Kit (DDK)
  • Microsoft Windows Millennium Edition
This article was previously published under Q282778

SUMMARY

A NDIS Protocol Driver in Microsoft Windows ME must have its LowerRange set to "ndis3,ndis4,ndis5". Otherwise, the binding engine refuses to bind the driver.

MORE INFORMATION

The network class installer, NetDI, does not bind an NDIS protocol driver if the LowerRange is specified as Ndis3 alone. The protocol driver's .inf file must have the following entry:

HKR,Ndi\Interfaces,LowerRange,,"ndis3,ndis4,ndis5"
Without this change, your protocol driver appears in the network properties. However, after a review of adapter and miniport bindings, you observe that no other component is bound to the protocol driver.

Also, if you use the debug or checked build of the Windows ME NetDI.dll, the following trace output is emitted: 
NETDI: ==>NdiBind
NETDI:      L:<lower adapter>
NETDI:      U:<your protocol>
NETDI: ==>NdiHasBinding
NETDI:      <protocol DeviceID> -> <Adapter DeviceID>?
NETDI: <==NdiHasBinding = 4b6
NETDI: ==>NdiHasBinding
NETDI:      <protocol DeviceID> -> <Adapter DeviceID>?
NETDI: <==NdiHasBinding = 4b6
NETDI:      QueryBind=4b7 From NdiCompareInterface
NETDI: <==NdiBind = 4b7
NETDI:                Can't bind to this object

REFERENCES

For additional information about using the debug version of NetDI.dll, click the article number below to view the article in the Microsoft Knowledge Base:

282757 HOWTO: Use Network Setup Debug Extensions to NetDI for Windows ME

Modification Type:MinorLast Reviewed:9/28/2004
Keywords:kbinfo kbKMode kbNDIS kbWDM KB282778
©2004 Microsoft Corporation. All rights reserved.