I have a driver that is a lower level filter on the Disk Class driver
running under Win2000. Its purpose is to hide the disk device by claiming
it, thereby preventing the Disk Class driver from doing so. The “hiding”
is selective based on Vendor/Product ID and VPD information returned.
Under Win2000 this works fine but in XP it causes PnP to tear down the
device stack. I’m looking for any suggestions on what I can do to get
around this problem.
One thought is to create a new Device class and add Vendor/Product ID
information in the INF file to have PnP load my
driver instead of disk.sys. Can anyone else lend some suggestions?
Thanks!
Bob
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
How is that going to work? The disk PDOs are created belonging to the
existing disk class, not your new disk class.
If you are implying that you create the PDOs, then sure you can assign
them to anything you like. You’ve now bought off on supplying your own
disk class driver, increasing the complexity of your software by a fair
amount.
I’m working on a project in the storage space that is currently working
around this whistler ‘feature’ by refusing to let our FDO’s get removed
if we think the removal is due to whistler’s odd behavior. But we also
have committed radical surgery on the storage stack, so the situation is
somewhat different. We know when it would be appropriate to allow
removal and when it wouldn’t.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@lsil.com
Sent: Friday, September 21, 2001 9:36 PM
To: NT Developers Interest List
Subject: [ntdev] Question for WinXP developers
I have a driver that is a lower level filter on the Disk Class driver
running under Win2000. Its purpose is to hide the disk
device by claiming
it, thereby preventing the Disk Class driver from doing so.
The “hiding”
is selective based on Vendor/Product ID and VPD information returned.
Under Win2000 this works fine but in XP it causes PnP to tear
down the
device stack. I’m looking for any suggestions on what I can
do to get
around this problem.
One thought is to create a new Device class and add Vendor/Product ID
information in the INF file to have PnP load my
driver instead of disk.sys. Can anyone else lend some suggestions?
Thanks!
Bob
You are currently subscribed to ntdev as:
xxxxx@hollistech.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
The Disk Class driver is creating the PDO’s. After re-reading my question
I see where I didn’t make that clear. I played around with same approach
you described without complete success.
Thanks for the response!
Bob
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