RE: [NTDev] Whistler problems with a 2000 driver ...

Failure to set Status and Information is for sure not the problem. I have
looked at the IRP and StackLocations both in the FDO and the PDO, when the
IRP_MN_FILTER_RESOURCE_REQUIREMENTS is received. The FDO leaves
IoStatus.Status set to STATUS_SUCCESS, does not touch IoStatus.Information,
skips the current SL, and calls the PDO. In turn the PDO, does not change
Status or Information, but does complete the IRP. However, no
IRP_MN_START_DEVICE is received. Information is set to what appears to be a
valid memory address, and is not touched by either my FDO or PDO.

Once at the desktop and in the Device Manager, the driver is enabled, but
the ICON for it has a yellow circle with a black exclamation point inside
it. The Device status says:

"This device cannot find enough resources that it can use.
(Code 12)

If you want to use the device, you will need to disable one of the devices
on this system."

Further investigation revealed the SAME status for Communications Port
(COM1). However, COM1 is the debug port connected to WinDbg on the host. Is
it normal, under Whistler, for COM1, when used as the debug port, to be
flagged as mentioned above?

I did find that the USB driver was installed but not needed since there is
no USB hardware in the box. I disabled and uninstalled it, but my FDO’s
still do not receive a “start device”. Sheesh, must I sacrifice my first
man-child to make Whistler happy?

This is a functional, Win2K driver that successfully negotiates 2000 PnP
start up.

Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com

-----Original Message-----
From: Eliyas Yakub [mailto:xxxxx@microsoft.com]
Sent: Saturday, March 10, 2001 9:41 AM
To: NT Developers Interest List
Subject: RE: [ntdev] [NTDev] Whistler problems with a 2000 driver …

Make sure you are not resetting the Irp->IoStatus.Information field to zero.

-Eliyas

-----Original Message-----
From: Gary Little
Sent: Fri 3/9/2001 6:09 PM
To: NT Developers Interest List
Cc:
Subject: [ntdev] [NTDev] Whistler problems with a 2000 driver …

I have a function driver that installs under Whistler, and loads, but never
gets an IRP_MN_START_DEVICE. The last thing it gets is an
IRP_MN_FILTER_RESOURCE_REQUIREMENTS, which I am handling according to the
docs. The function driver passes it down to the bus driver which completes
it with STATUS_SUCCESS.

Does Whistler require something else, other than what 2000 requires in this
IRP?

Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.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