Programatically install NDIS protocol driver in W2K

[Dave Canfield]

Hopefully somebody out there can help me:

I'm working on a product installation wizard that
needs to install three drivers, one of which is
an NDIS protocol driver. There are a couple of
knowledge base articles that describe how to do
this on NT 4.0. But I now need to figure out how
to do this on W2k as well.

I have been able to successfully install my protocol
driver manually using the Network and Dial-up Connections
applet, so I believe my INF file is ok.

After many hours of experimenting with the SetupDiXXX
functions I have managed to "sort of" install the driver,
but the registry entries of my driver under the Enum
branch of the registry don't look the same as when I
install the driver using the control panel applet.

The most significant difference I noticed is that when
installed using the control panel applet the classGUID
value is changed from NetTrans to LegacyDriver.

The RC2 version of the DDK says that LegacyDriver is
used for Non-Plug and Play Drivers, and that it
should not be used to install devices (or drivers).

Anybody have any ideas...

Thanks,
Dave Canfield

[eli...@microsoft.com]

In article <37FBE607...@cmd.com>,

The netcfg sample under src\network\config\netcfg directory shows how
to programmatically install Protocol, Service and Client components.
Just follow that and you are set!

For reasons unknown to me, all the protocols drivers remains as legacy
drivers on Windows2000. But they are notified about PnP and Power
Management events through callback functions.

Good Luck,
Eliyas

Sent via Deja.com http://www.deja.com/
Before you buy.