In Windows 2000 I am quite sure that you are correct :
“‘NdisReadPciSlotInformation’ doesn’t take bus number as input.” If you
write your driver to the NDIS 5 standards, you don’t get to probe the
hardware for any of the pci devices. NDIS hides what the plug and play
software is doing, all that you get to know about each device is the
information that you get when the OS calls your InitializeHandler function
(which you specify in your DriverEntry function).
If you are writing a device for a “run of the mill” network card, then all
that you need to know if that you don’t need to probe the hardware, since
for every instance of your device that is on the system, the
InitializeHandler function will be called. If your device is not “run of
the mill” , then you may have to do something different (that may not
really fit into the Ndis standard). I don’t know that I can help you if
that is the case.
Good Luck,
Doug McLetchie
xxxxx@yahoo.com
On 11/03/01, “xxxxx@controlnet.co.in” wrote:
Hi,
I have used ‘NdisReadPciSlotInformation’ in my NDIS driver to search for
the network card. I recently found out that this is not working properly
for a machine, on which their are multiple buses and card is on other than
1st bus. ‘NdisReadPciSlotInformation’ doesn’t take bus number as input, so
how I can search the network card using NDIS function and also how I can
read assigned resources?
Please help me as soon as possible. If you have sample algorithm/code,
please send it to me.
Thank you.
Regards,
Mohan
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com