Prev: NdisMSetMiniportAttributes Fails With NDIS 6.1 Miniport
Next: WINDDK help fails to start w/ cannot open the file ...\winddk.col
From: francois on 27 Mar 2008 06:19 In the AddDevice() handler from our driver for USB device, we call the IoGetDeviceProperty() and it returns STATUS_OBJECT_NAME_NOT_FOUND. We use the same PhysicalDeviceObject given as a parameter in the AddDevice() handler. Can you see one possible reason for this ? Our driver is BDA driver with USB WDM lower edge. The strange thing is that problem occurs only on Windows 2000 platform with USB composite device. On Windows XP/Vista, or if the device exposes only one single USB interface, the call to IoGetDeviceProperty() is successful. Thanks for your help Francois
From: chris.aseltine on 27 Mar 2008 10:23 On Mar 27, 5:19 am, francois <fkanounnik...(a)yahoo.fr> wrote: > Our driver is BDA driver with USB WDM lower edge. The strange thing is > that problem occurs only on Windows 2000 platform with USB composite > device. On Windows XP/Vista, or if the device exposes only one single > USB interface, the call to IoGetDeviceProperty() is successful. Which property are you trying to pull?
From: francois on 27 Mar 2008 10:52 We are trying to pull "DevicePropertyBusTypeGuid" property
From: Doron Holan [MSFT] on 27 Mar 2008 14:25 is it a multi function device and usbccgp is your parent driver? -- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "francois" <fkanounnikoff(a)yahoo.fr> wrote in message news:9f7069d1-654f-4457-a75f-6b787a8a41c5(a)d4g2000prg.googlegroups.com... > We are trying to pull "DevicePropertyBusTypeGuid" property >
From: francois on 27 Mar 2008 16:37
Yes, it is a multifunction USB device. The parent driver is usbccgp.sys on Windows XP. On Windows 2000, it should be usbhub.sys. |