Protocol driver bind problem !

[Sajith Raman]

Hi,

We have developed a protocol driver and also an installer
using InetCfg Class.
My problem is that is binds to all the underlying network
adapters which I would like to avoid.

Is there anyway to install the protocol driver and not let
it bind to any components ?

Any help would be highly appreciated.
Regards,
Sajith

 

[Slobodan Brcin]

First I think that you must bind it to at least one adapter (component), if
you don't then it is not a protocol driver, and you can't use NDIS.

Since you have developed protocol driver you should be able to ignore
bindings to other adapters programmatically, I mean to filter out request on
them.

I you are writing driver to exclusively run under the XPE, and you have
known and unchangeable hardware configuration. You could make the component
in CD that will populate registry with binding information you manually
entered. Drawback to this is that you can't use installers and possibly PnP,
and if you are planning too change hardware you must make another
components.

One last solution is to make an application that will do PnP binding by
writing in registry directly. This is not recommended for drivers that will
be installed by third party.

And always there is the solution that this can be done using some API
functions unknown to me.


Best regards,
Slobodan