Microsoft KB Archive/282778

{|
 * width="100%"|

INFO: Setting LowerRange for NDIS Protocol Drivers in Windows ME

 * }

Q282778

-

The information in this article applies to:


 * Microsoft Windows ME Driver Development Kit (DDK)
 * Microsoft Windows Millennium Edition

-

SUMMARY
A NDIS Protocol Driver in Microsoft Windows ME must have its LowerRange set to &quot;ndis3,ndis4,ndis5&quot;. 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,,&quot;ndis3,ndis4,ndis5&quot; 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: NETDI:      U: NETDI: ==>NdiHasBinding NETDI:      -> ? NETDI: <==NdiHasBinding = 4b6 NETDI: ==>NdiHasBinding NETDI:      -> ? NETDI: <==NdiHasBinding = 4b6 NETDI:     QueryBind=4b7 From NdiCompareInterface NETDI: <==NdiBind = 4b7 NETDI:               Can't bind to this object