Hello,
Yes, I use an INF file to install my driver. I support all the required
OIDs and I checked my INF file against a standard example in the DDK.
I can’t seem to figure out why TCP/IP wouldn’t want to bind to my
miniport / adapter?
Ravi
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Amitabh
Mathrawala
Sent: Tuesday, March 15, 2005 5:29 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] NDIS and how it works?
Hi Ravi.
There are a couple of websites that might give you information if the
DDK isn’t enough.
www.ndis.com http:</http:> && www.wd-3.com
http:</http:> .
I don’t know if they address your specific problem but you might find
related information there.
I am assuming that you installed your miniport using a .inf file on the
second machine. When you register your
Driver as a miniport, the NDIS wrapper calls the ProtocolBindAdapter
function of all protocol drivers to ask them
if they want to bind themselves to your adapter. It seems to me that
none of the protocols want to bind to your
adapter. Compare your inf file with the miniport samples and see if
there a flag is incorrectly specified or something like that.
Good luck.
Amitabh Mathrawala | Senior Software Engineer | Server Group |
xxxxx@viack.com | 425 605 7483
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Murty, Ravi
Sent: Tuesday, March 15, 2005 4:06 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] NDIS and how it works?
Hello All,
Is there a web-site/documentation out there that talks about what
happens when you install an NDIS miniport. Here’s the problem I face.
I am writing this miniport for a new card and it installs okay. I was
debugging my SendPackets routine, but for some reason decided to move to
a new machine.
This essentially took me back to the point where the miniport comes up,
I see some OIDs but no “Network Connections” icon and consequently no
OIDs like GEN_LINK_SPEED etc. Why is this so difficult?
Should NDIS or some Microsoft automatically install TCP/IP and other
components of the stack after I indicate that this is a new device and
it is of type 802_3?
Clearly this driver was working on the previous machine. I simply moved
my card to this newly installed windows XP machine and I am back to
where I was a week ago!
Would really like to get to know why this is so peculiar or if I am just
plain missing something stupid.
thanks
Ravi
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com