NdisReadPciSlotInformation failed under xp

Hi all,

I am writing a NIC driver for windows2k and XP.
NdisReadPciSlotInformation API gets falied under xp but it works fin under 2k.
Please guide me how to resolve problem.

--
With regards
thanks
Anand Choubey

Stephan
Mon Jan 01 10:50:12 CST 2007

Anand Choubey wrote:
> I am writing a NIC driver for windows2k and XP.
> NdisReadPciSlotInformation API gets falied under xp but it works fin under 2k.
> Please guide me how to resolve problem.

What do you mean by "failed"? Zero length returned or invalid
information returned in the buffer?

Stephan

anand
Mon Jan 01 23:29:15 CST 2007

Hi,

Thanks for reply. NdisReadPciSlotInformation api returns vedorid and
DeviceID are returned 0.

Anand Choubey
Stephan Wolf [MVP] wrote:
> Anand Choubey wrote:
> > I am writing a NIC driver for windows2k and XP.
> > NdisReadPciSlotInformation API gets falied under xp but it works fin under 2k.
> > Please guide me how to resolve problem.
>
> What do you mean by "failed"? Zero length returned or invalid
> information returned in the buffer?
>
> Stephan

Alireza
Tue Jan 02 03:49:45 CST 2007

So the returned length is correct (it is the same as the number of bytes you
tried to read) but the information is invalid?
Sorry, I could not tell for sure what you meant by your answer below.

-ali

--
This posting is provided "AS IS" with no warranties, and confers no rights.

<anand.choubey@gmail.com> wrote in message
news:1167715755.495160.145880@i12g2000cwa.googlegroups.com...
> Hi,
>
> Thanks for reply. NdisReadPciSlotInformation api returns vedorid and
> DeviceID are returned 0.
>
> Anand Choubey
> Stephan Wolf [MVP] wrote:
>> Anand Choubey wrote:
>> > I am writing a NIC driver for windows2k and XP.
>> > NdisReadPciSlotInformation API gets falied under xp but it works fin
>> > under 2k.
>> > Please guide me how to resolve problem.
>>
>> What do you mean by "failed"? Zero length returned or invalid
>> information returned in the buffer?
>>
>> Stephan
>

anand
Thu Jan 04 01:56:31 CST 2007

Hi,

NdisReadPciSlotInformation method returns Zero length returned at XP
machine.
But this works fiine on Windows 2k machine.
XP and 2k mchines are installed on different mother board. Is this
problem with hardware or OS issue?
Please guide me.

Thanks
Anand Choubey
Stephan Wolf [MVP] wrote:
> Anand Choubey wrote:
> > I am writing a NIC driver for windows2k and XP.
> > NdisReadPciSlotInformation API gets falied under xp but it works fin under 2k.
> > Please guide me how to resolve problem.
>
> What do you mean by "failed"? Zero length returned or invalid
> information returned in the buffer?
>
> Stephan

Stephan
Thu Jan 04 04:20:18 CST 2007

This is actually kind of weird. Back in the non-PnP days, i.e. in NT4
and below, the 'SlotNumber' parameter passed to
NdisReadPciSlotInformation() could be just any number and the function
returned the PCI information for this sepcific slot.

In PnP systems, i.e. W2K and above, the 'SlotNumber' is ignored because
NDIS already knows for which device instance it loads the miniport
driver. So this sounds like contradictory to me, i.e., NDIS load the
driver for a particular PCI device here, so the device must have been
detected by the PnP mechanism. But then NdisReadPciSlotInformation()
claims to not have any PCI configuration info about this same device?
No way.

Something must be wrong in your system here. Try and open Device
Manager and verify the properties of your device. Inspect the system
event log. Also try on some other XP system.

Stephan
---
anand.choubey@gmail.com wrote:
> Hi,
>
> NdisReadPciSlotInformation method returns Zero length returned at XP
> machine.
> But this works fiine on Windows 2k machine.
> XP and 2k mchines are installed on different mother board. Is this
> problem with hardware or OS issue?
> Please guide me.
>
> Thanks
> Anand Choubey

Alireza
Thu Jan 04 05:41:02 CST 2007

Chances are this is a hardware (motherboard/PCI bridge) issue.

-ali
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Stephan Wolf [MVP]" <stewo68@hotmail.com> wrote in message
news:1167906016.567250.37900@31g2000cwt.googlegroups.com...
> This is actually kind of weird. Back in the non-PnP days, i.e. in NT4
> and below, the 'SlotNumber' parameter passed to
> NdisReadPciSlotInformation() could be just any number and the function
> returned the PCI information for this sepcific slot.
>
> In PnP systems, i.e. W2K and above, the 'SlotNumber' is ignored because
> NDIS already knows for which device instance it loads the miniport
> driver. So this sounds like contradictory to me, i.e., NDIS load the
> driver for a particular PCI device here, so the device must have been
> detected by the PnP mechanism. But then NdisReadPciSlotInformation()
> claims to not have any PCI configuration info about this same device?
> No way.
>
> Something must be wrong in your system here. Try and open Device
> Manager and verify the properties of your device. Inspect the system
> event log. Also try on some other XP system.
>
> Stephan
> ---
> anand.choubey@gmail.com wrote:
>> Hi,
>>
>> NdisReadPciSlotInformation method returns Zero length returned at XP
>> machine.
>> But this works fiine on Windows 2k machine.
>> XP and 2k mchines are installed on different mother board. Is this
>> problem with hardware or OS issue?
>> Please guide me.
>>
>> Thanks
>> Anand Choubey
>