I’ve had to grovel the registry using Zw* and Rtl* routines to read the configuration of another NIC from my miniport driver. NdisOpenConfiguration() seems to work only for the current miniport driver. Has anyone else had to do the same and come up with another way to do so?
Thx!
-Chaitanya
Chaitanya,
NdisOpenProtocolConfiguration() can actually be used to open an arbitrary
registry key and supply an NDIS Configuration Handle for use with the other
configuration functions. That does not help you actually *find* the
registry key name that represents the NIC configuration but I assume you
must have some way of knowing which NIC you are trying to spy configuration
information from.
It would be somewhat irresponible of me to not ask what you are trying to
accomplish by accessing another NICs configuration. Perhaps the underlying
problem you are trying to solve would benefit from another approach. So,
why do you want to read NIC A’s configuration while (presumably) handling
NIC B’s MiniportInitialize?
Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, September 20, 2006 7:18 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Reading another NIC’s configuration from a miniport
I’ve had to grovel the registry using Zw* and Rtl* routines to read the
configuration of another NIC from my miniport driver.
NdisOpenConfiguration() seems to work only for the current miniport driver.
Has anyone else had to do the same and come up with another way to do so?
Thx!
-Chaitanya
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I want to copy over certain network settings on NIC A when NIC B is initialized.