All:
This is a follow up to a post made earlier.
The author reported that IoGetDeviceProperty for a PCMCIA card pdo with
the DevicePropertyUINumber returned Slot 0, no matter the card was. He
reported this under Windows 98.
I have found the same issue under Windows 2000 using a CardBus drive.
Using a CardBus driver there are Pcmcia0 and Pcmcia1 driver objects (one
for each slot). In this regard, I suppose it makes since to return slot
zero for each driver, but this doesn’t allow a driver to supply helpful
information to the user who only knows there are two slots available.
I though I had a fix for this. I compare my pdo->NextDevice to the
device returned by IoGetDeviceObjectPointer for \Device\Pcmcia0 and
\Device\Pcmcia1 but this test always indicates the device is connected
to Pcmcia0; even when its in the Pcmcia1 slot. (D’oh!)
I need to know what slot my driver is serving. Any hints would be
greatly
appreciated. Thanks in advance
Thomas McCormick
Centennial Technologies
e-mail: xxxxx@cent-tech.com
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
>This is a follow up to a post made earlier.
The author reported that IoGetDeviceProperty for a PCMCIA card pdo with
the DevicePropertyUINumber returned Slot 0, no matter the card was.
I had noticed this problem with W2K last year. An idea I never tried was to
determine if the BUS number might have some relationship to the card slot.
The thought was perhaps it was correct to return the slot as always being
zero on a PCI controller (where each slot seems to have it’s own
controller), but only if the BUS number was unique. Of course then there
was the problem of how to map a bus number to some actual physical PCMCIA
slot. The lack of correct slot number is a really serious problem if you
have two identical PCMCIA cards installed.
Another idea was to open the PCMCIA0\1 controller device and make old style
queries. This also didn’t solve the problem if you had two identical cards
installed, as there was still no way to connect a specific PDO/FDO with a
specific logical slot.
My stand would be the Microsoft driver is broken, and they should fix it.
One of the queryable fields is clearly the user interface perceived slot
number, and this is bogus.
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