Soory for my late response . I rechecked my use of IoGetDeviceInterfaces()
.
This api is used by me with NULL for PhysDeviceObject since I do not know
my DeviceObject inside
my miniport . I intend to get the whole list of interfaces (if more than
one ) and filter them.
The api is called from DriverEntry . Also I tried it from a woker thread .
In both cases I get a Bluse screen
with 0xc0000005 . Any explanation ? Or is there a way to know my
PhysDeviceObject inside my miniport to avoid the usage of NULL
as a non specified (optional) parameter ?
Zvi Dubitzky
Storage Systems Technology Email: dubi@il.ibm.com
IBM Haifa Research Laboratory Phone: +972-4-8296182
Haifa, 31905, ISRAEL
If you are discussing a scsi miniport driver, find the driver-object of your
miniport driver and you will get the PDOs of those scsi devices. But, the
PDO of the adapter is not there - it’s created by \Driver\PCI.
Regards,
Ray Yang xxxxx@ybwork.com
----- Original Message -----
From: “Zvi Dubitzky” To: “Windows System Software Devs Interest List” Sent: Friday, July 02, 2004 7:55 PM Subject: [ntdev] IoGetEeviceInterfaces
> Hi there > > Soory for my late response . I rechecked my use of IoGetDeviceInterfaces() > . > This api is used by me with NULL for PhysDeviceObject since I do not know > my DeviceObject inside > my miniport . I intend to get the whole list of interfaces (if more than > one ) and filter them. > The api is called from DriverEntry . Also I tried it from a woker thread . > In both cases I get a Bluse screen > with 0xc0000005 . Any explanation ? Or is there a way to know my > PhysDeviceObject inside my miniport to avoid the usage of NULL > as a non specified (optional) parameter ? > > Zvi Dubitzky > Storage Systems Technology Email: dubi@il.ibm.com > IBM Haifa Research Laboratory Phone: +972-4-8296182 > Haifa, 31905, ISRAEL > > > > — > Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 > > You are currently subscribed to ntdev as: xxxxx@ybwork.com > To unsubscribe send a blank email to xxxxx@lists.osr.com >