Microsoft KB Archive/323458

= INFO: Known issues with NDIS Intermediate (IM) driver samples =

PSS ID Number: 323458

Article Last Modified on 2/13/2004

-

The information in this article applies to:


 * Microsoft Windows 2000 Driver Development Kit (DDK)
 * Microsoft Windows XP Driver Development Kit (DDK)
 * Microsoft Windows Server 2003 Driver Development Kit (DDK)

-



This article was previously published under Q323458





Issue A: Binding a Network Adapter
After you install and bind a network device interface specification (NDIS) intermediate (IM) driver to all the available network adapters, the IM driver does not bind automatically to any newly installed network adapters.

Issue B: Removing a Network Adapter
If you remove a network adapter that an NDIS IM driver was bound to while the system is hibernating, the computer may stop responding when it resumes.



Issue A: Binding a Network Adapter
When you add a new network adapter, the network class installer tries to install a virtual miniport that corresponds to the physical network adapter that the IM miniport is binding to. The network class installer tries to do this in a &quot;server-side installation&quot; context with no user intervention. If the IM driver is not digitally signed, the server-side installation will fail, and the following entries appear in the SetupAPI log:

#I124 Doing copy-only install of &quot;ROOT\MS_PASSTHRUMP\0002&quot;.
 * 1) -011 Installing section [PassthruMP.ndi] from &quot;c:\windows\inf\oem14.inf&quot;.
 * 2) E358 An unsigned or incorrectly signed file &quot;c:\windows\inf\oem14.inf&quot; for driver &quot;Passthru Miniport&quot; blocked (server install). Error 1168: Element not found.
 * 3) E122 Device install failed. Error 1168: Element not found.&quot;

Issue B: Removing a Network Adapter
After the computer resumes from hibernation, the plug-and-play (PnP) subsystem discovers that a network adapter has been removed. The system then tries to surprise remove (or tear down) the device stack of the network adapter. Any bound IM driver that has reached the D0 (&quot;dee-zero&quot;) power state (that is, the working state) before this surprise remove occurs might try to send an NDIS request. Therefore, the bound IM driver will block indefinitely when the request is finished. This behavior appears as an unresponsive system.



Issue A: Binding a Network Adapter
To resolve this problem, obtain a digital signature for the IM driver.

A new self-testing process to obtain digital signatures for IM drivers is available from Windows Hardware Quality Labs (WHQL). For more information and to download the self-extracting executable that contains a Word document, visit the following Microsoft Download Center Web site:

http://download.microsoft.com/download/whistler/Install/1.0/NT5XP/EN-US/NDIS_IM_Driver_Self_test.exe

For more information about WHQL signing processes, visit the following Microsoft Web sites:

Windows Quality Online Services

https://winqual.microsoft.com

Windows Hardware and Driver Central

http://www.microsoft.com/whdc/hwtest/default.mspx

Issue B: Removing a Network Adapter
The NDIS IM samples (both the MUX sample and the Passthru sample) in Microsoft Windows Server 2003 DDK have been updated to resolve this issue. If you have based your driver code on either of these samples, you must modify your code accordingly.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

Keywords: kbDDK kbNDIS KB323458

Technology: kbAudDeveloper kbwin2000DDK kbwin2000Search kbWinDDK kbWinDDKSearch kbWinServ2003DDK kbWinServ2003Search kbWinXPDDKSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.