NDIS driver install by snetcfg.exe help!

Hi everyone,

I write a NDIS driver and use "Local area network property" to install
driver, and it 100% success. If I used "snetcfg.exe" for programatical
install my NDIS driver at the computer logon then I get blue screen randomly,
I think about 70% success.
For cases that success, Device Manger->Network adapter showed:

-Network adapters
--Intel(R) PRO/100 S Dual Port Server Adapter
--Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
--Intel(R) PRO/100 S Dual Port Server Adapter #2
--Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual adapter

Everytime the installation failed it give me a Blue Screen and automaticly
reboot the node. Then it kicked off the snetcfg.exe to install again. I
checked in the Device Manager->Network Adapters showed:

-Network adapters
--My Sample Virtual adapter (extra stand alone,I think this is causing blue
screen)
--Intel(R) PRO/100 S Dual Port Server Adapter
--Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
--Intel(R) PRO/100 S Dual Port Server Adapter #2
--Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual adapter

My guess is timing, when snetcfg.exe start install and the network adapters
are there but not fully functioning/binding yet. and when snetcfg install it
couldn't find the adapter to bind and it just install the Ndis driver as a
stand alone network adapter. Please correct me if I'm wrong...

My question is: how do I check if network support is ready/fully functioning
inorder for me to install 100% sucess. OR is there any other hints/method
for me to avoid the blue screen and also the driver work properly by using
snetcfg.exe to install.

Many many thanks for any help!

ttan

Thomas
Tue Aug 01 12:52:31 CDT 2006

There is no excuse for a driver developer to say "I get a blue screen" that
I can think of. Use WinDbg to identify the problem!

Your question is like saying "My car won't start. I have four Bridgstone
tires. Exactly what is wrong with my car?".

Thomas F. Divine, Windows DDK MVP

"ttan" <ttan@discussions.microsoft.com> wrote in message
news:5E13FC4A-875E-43B6-9C0C-1E3E34E5C8DB@microsoft.com...
> Hi everyone,
>
> I write a NDIS driver and use "Local area network property" to install
> driver, and it 100% success. If I used "snetcfg.exe" for programatical
> install my NDIS driver at the computer logon then I get blue screen
> randomly,
> I think about 70% success.
> For cases that success, Device Manger->Network adapter showed:
>
> -Network adapters
> --Intel(R) PRO/100 S Dual Port Server Adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter #2
> --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual
> adapter
>
> Everytime the installation failed it give me a Blue Screen and automaticly
> reboot the node. Then it kicked off the snetcfg.exe to install again. I
> checked in the Device Manager->Network Adapters showed:
>
> -Network adapters
> --My Sample Virtual adapter (extra stand alone,I think this is causing
> blue
> screen)
> --Intel(R) PRO/100 S Dual Port Server Adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter #2
> --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual
> adapter
>
> My guess is timing, when snetcfg.exe start install and the network
> adapters
> are there but not fully functioning/binding yet. and when snetcfg install
> it
> couldn't find the adapter to bind and it just install the Ndis driver as a
> stand alone network adapter. Please correct me if I'm wrong...
>
> My question is: how do I check if network support is ready/fully
> functioning
> inorder for me to install 100% sucess. OR is there any other hints/method
> for me to avoid the blue screen and also the driver work properly by using
> snetcfg.exe to install.
>
> Many many thanks for any help!
>
> ttan
>

ttan
Tue Aug 01 13:25:01 CDT 2006

I used WinDbg to debug the problem and found that the driver is looking for 2
adapters but because of the failed installation it send out 3 adapters (2
real adapters and an extra stand alone one). I added a check to filter out
the 2 real adapters and that help with the blue screen.
But users always confused with the network adapters showed up in the device
manager.

Again my question is: how do I used snetcfg.exe to install network Ndis
driver without showing up the "3rd/extra" phantom adapter? Is there a method
to check for the network support fully function and behave as the "local
network area" property install?

"Thomas F. Divine [DDK MVP]" wrote:

> There is no excuse for a driver developer to say "I get a blue screen" that
> I can think of. Use WinDbg to identify the problem!
>
> Your question is like saying "My car won't start. I have four Bridgstone
> tires. Exactly what is wrong with my car?".
>
> Thomas F. Divine, Windows DDK MVP
>
> "ttan" <ttan@discussions.microsoft.com> wrote in message
> news:5E13FC4A-875E-43B6-9C0C-1E3E34E5C8DB@microsoft.com...
> > Hi everyone,
> >
> > I write a NDIS driver and use "Local area network property" to install
> > driver, and it 100% success. If I used "snetcfg.exe" for programatical
> > install my NDIS driver at the computer logon then I get blue screen
> > randomly,
> > I think about 70% success.
> > For cases that success, Device Manger->Network adapter showed:
> >
> > -Network adapters
> > --Intel(R) PRO/100 S Dual Port Server Adapter
> > --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> > --Intel(R) PRO/100 S Dual Port Server Adapter #2
> > --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual
> > adapter
> >
> > Everytime the installation failed it give me a Blue Screen and automaticly
> > reboot the node. Then it kicked off the snetcfg.exe to install again. I
> > checked in the Device Manager->Network Adapters showed:
> >
> > -Network adapters
> > --My Sample Virtual adapter (extra stand alone,I think this is causing
> > blue
> > screen)
> > --Intel(R) PRO/100 S Dual Port Server Adapter
> > --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> > --Intel(R) PRO/100 S Dual Port Server Adapter #2
> > --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual
> > adapter
> >
> > My guess is timing, when snetcfg.exe start install and the network
> > adapters
> > are there but not fully functioning/binding yet. and when snetcfg install
> > it
> > couldn't find the adapter to bind and it just install the Ndis driver as a
> > stand alone network adapter. Please correct me if I'm wrong...
> >
> > My question is: how do I check if network support is ready/fully
> > functioning
> > inorder for me to install 100% sucess. OR is there any other hints/method
> > for me to avoid the blue screen and also the driver work properly by using
> > snetcfg.exe to install.
> >
> > Many many thanks for any help!
> >
> > ttan
> >
>
>

Stephan
Sun Aug 06 03:58:22 CDT 2006

In WinDbg, type "!analyze -v" and carefully inspect the results. Make
sure to
have the symbol server set up correctly in WinDbg (see
http://www.microsoft.com/whdc/devtools/debugging/).

Stephan
---
ttan wrote:

> Hi everyone,
>
> I write a NDIS driver and use "Local area network property" to install
> driver, and it 100% success. If I used "snetcfg.exe" for programatical
> install my NDIS driver at the computer logon then I get blue screen randomly,
> I think about 70% success.
> For cases that success, Device Manger->Network adapter showed:
>
> -Network adapters
> --Intel(R) PRO/100 S Dual Port Server Adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter #2
> --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual adapter
>
> Everytime the installation failed it give me a Blue Screen and automaticly
> reboot the node. Then it kicked off the snetcfg.exe to install again. I
> checked in the Device Manager->Network Adapters showed:
>
> -Network adapters
> --My Sample Virtual adapter (extra stand alone,I think this is causing blue
> screen)
> --Intel(R) PRO/100 S Dual Port Server Adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter - My Sample Virtual adapter
> --Intel(R) PRO/100 S Dual Port Server Adapter #2
> --Intel(R) PRO/100 S Dual Port Server Adapter #2 - My Sample Virtual adapter
>
> My guess is timing, when snetcfg.exe start install and the network adapters
> are there but not fully functioning/binding yet. and when snetcfg install it
> couldn't find the adapter to bind and it just install the Ndis driver as a
> stand alone network adapter. Please correct me if I'm wrong...
>
> My question is: how do I check if network support is ready/fully functioning
> inorder for me to install 100% sucess. OR is there any other hints/method
> for me to avoid the blue screen and also the driver work properly by using
> snetcfg.exe to install.
>
> Many many thanks for any help!
>
> ttan