Hi,

We have developed a NDIS protocol driver. We are
registering the protocol with NDIS by calling the
registerProtocol function. Once executed we expect the
callback function "protocolBindAdapter"(exported in the
driver code) to be called by NDIS for each NIC which
becomes available.
The driver works fine in windows XP environment (setup as
a service) but fails when added as in "embedded XP" image.
Is there any specific component which need to be added in
order to abtain the above functionality ?
Any help in this matter will be highly appreciated.

Thanks,
Sajith

I had a similar problem few day before. I guess that you are trying to
register protocol using the component you have created.
Inf file containing protocol should be registered using snetcfg.exe that
will bind the protocol to all NICs.


In CD under Resources
Add FBA Generic Command
FilePath = %11%\snetcfg.exe
Arguments = -l %17%\( inffilename ).inf -c p -i ( ServiceName )


You should type snetcfg.exe /? for parameters.

Hope this helps,
Slobodan


"Sajith Raman" <(E-Mail Removed)> wrote in message
news:083401c33ae0$5aa69de0$(E-Mail Removed)...
> Hi,
>
> We have developed a NDIS protocol driver. We are
> registering the protocol with NDIS by calling the
> registerProtocol function. Once executed we expect the
> callback function "protocolBindAdapter"(exported in the
> driver code) to be called by NDIS for each NIC which
> becomes available.
> The driver works fine in windows XP environment (setup as
> a service) but fails when added as in "embedded XP" image.
> Is there any specific component which need to be added in
> order to abtain the above functionality ?
> Any help in this matter will be highly appreciated.
>
> Thanks,
> Sajith