That's because your driver is unsigned.

-BB

"Soquel Dude" <ImInSoquel@nospam.nospam> wrote in message
news:OQ%23oSl%23WFHA.584@TK2MSFTNGP15.phx.gbl...

I'm looking at a "problem" which may be related to my driver being unsigned.

Here's the deal:

1. I install the IM driver (which is based on the Server 2003 SP1 passthru
sample). I get the windows that say this is an unsigned driver, etc. At the
end, the driver has bound to all NIC drivers installed on the system at that
time and all is well.

2. I install the client utility software for a wireless card. In this case,
it's the client software for the LinkSys Wireless A+G (WPC55AG) version 1.1.

3. When the client software is installed, I pop in the WLAN NIC. The OS
detects the card and installs the driver but does not call the IM driver's
BindAdapter function. So, at this point, the IM driver is not bound to the
NIC's miniport driver. If I restart the system, or simply go the network
properties of the WLAN NIC from the control panel applet, then the OS will
bind the IM driver to the miniport.

This doesn't seem to be a problem with the IM driver per se. I can reproduce
the same problem just by installing the sample passthru driver.

Does anyone know what's going on here?

Thanks!

"Soquel Dude" <ImInSoquel@nospam.nospam> wrote in message
news:OQ%23oSl%23WFHA.584@TK2MSFTNGP15.phx.gbl...
though the user has elected to install the unsigned driver the system does
not handle unsigned IM drivers correctly when additional adapters are
installed later... :-(

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

can we get the notification for the installation of new adapters. can
Notify Object DLL be used.

Bajamani wrote:
Sure, simply return the NCN_ADD and NCN_UPDATE notifications from your
INetCfgComponentNotifyGlobal::GetSupportedNotifica tions() function.

Stephan