Hi,
I am Pratheesh, a newbie in driver development. I would like to know how
NdisOpenAdapter works internally.
I am using Win2K and I have 2 ATM PCI adapters installed in my system.
I modified NDIS protocol sample driver(atmsmple) given in DDK for my
purpose. But whenever I send packets using my driver, it always select
adapter installed in PCI slot2.
DDK documentation says Adapter to which protocol needs to be bound must
be specified using AdapterName. The sample code uses \device\REG-KEY
corresponding to adapter as adapter name.
But I found this adapter name has no relevance, whatever string as
adaptername I give NdisOpenAdapter selects the adapter in second PCI slot.
If I disable adapter in the second PCI slot NDIS selects adapter in the
first PCI slot. So my conclusion NDIS internally maintains list of
adapters installed and always bind protocol to adapter in the front of the
list. Correct me if I am wrong.
Is there is any other option to specify adapter into which protocol needs
to be bound? Or is it a bug with NDIS?
Thanks for your help in advance.
Regards,
Pratheesh.
You should be able to use a “Notify Object” DLL to manage bindings of your
protocol driver. Lookup “Notify Object” in the DDK documentation.
Do both adapters show up separately in the Network Control Panel?
You may also be able to use the DDK “BindView” sample application (under
“config” I think) to examine (and modify) bindings.
Good luck,
Thomas
“Pratheesh Gangadhar” wrote in message
news:xxxxx@ntdev…
>
> Hi,
>
> I am Pratheesh, a newbie in driver development. I would like to know how
> NdisOpenAdapter works internally.
>
> I am using Win2K and I have 2 ATM PCI adapters installed in my system.
> I modified NDIS protocol sample driver(atmsmple) given in DDK for my
> purpose. But whenever I send packets using my driver, it always select
> adapter installed in PCI slot2.
>
> DDK documentation says Adapter to which protocol needs to be bound must
> be specified using AdapterName. The sample code uses \device\REG-KEY
> corresponding to adapter as adapter name.
>
> But I found this adapter name has no relevance, whatever string as
> adaptername I give NdisOpenAdapter selects the adapter in second PCI slot.
> If I disable adapter in the second PCI slot NDIS selects adapter in the
> first PCI slot. So my conclusion NDIS internally maintains list of
> adapters installed and always bind protocol to adapter in the front of the
> list. Correct me if I am wrong.
>
> Is there is any other option to specify adapter into which protocol needs
> to be bound? Or is it a bug with NDIS?
>
> Thanks for your help in advance.
> Regards,
> Pratheesh.
>
>
>
>
>
>
>
Thanks a lot Thomas, that works.
-----Original Message-----
From: Thomas F. Divine [mailto:xxxxx@hotmail.com]
Sent: Friday, August 22, 2003 7:20 PM
To: Windows System Software Developers Interest List
Subject: [ntdev] Re: NdisOpenAdapter - Multiple adapters
You should be able to use a “Notify Object” DLL to manage bindings of your
protocol driver. Lookup “Notify Object” in the DDK documentation.
Do both adapters show up separately in the Network Control Panel?
You may also be able to use the DDK “BindView” sample application (under
“config” I think) to examine (and modify) bindings.
Good luck,
Thomas
“Pratheesh Gangadhar” wrote in message
news:xxxxx@ntdev…
>
> Hi,
>
> I am Pratheesh, a newbie in driver development. I would like to know how
> NdisOpenAdapter works internally.
>
> I am using Win2K and I have 2 ATM PCI adapters installed in my system.
> I modified NDIS protocol sample driver(atmsmple) given in DDK for my
> purpose. But whenever I send packets using my driver, it always select
> adapter installed in PCI slot2.
>
> DDK documentation says Adapter to which protocol needs to be bound must
> be specified using AdapterName. The sample code uses \device\REG-KEY
> corresponding to adapter as adapter name.
>
> But I found this adapter name has no relevance, whatever string as
> adaptername I give NdisOpenAdapter selects the adapter in second PCI slot.
> If I disable adapter in the second PCI slot NDIS selects adapter in the
> first PCI slot. So my conclusion NDIS internally maintains list of
> adapters installed and always bind protocol to adapter in the front of the
> list. Correct me if I am wrong.
>
> Is there is any other option to specify adapter into which protocol needs
> to be bound? Or is it a bug with NDIS?
>
> Thanks for your help in advance.
> Regards,
> Pratheesh.
>
>
>
>
>
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: pratheesh@ti.com
To unsubscribe send a blank email to xxxxx@lists.osr.com