Hi,
I am writing a lower class disk filter driver.
My requirement is to not attach the disk.sys to the
Disk PDO.
It is working fine in Windows 2000 but in .NET if I
fail the SRB_FUNCTION_CLAIM_DEVICE, I am receiving
IRP_MN_REMOVE_DEVICE for the disk FiDo.
Is there any work around for it in .net.
TIA
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook™.
http://calendar.yahoo.com
> I am writing a lower class disk filter driver.
My requirement is to not attach the disk.sys to the
Disk PDO.
It is working fine in Windows 2000 but in .NET if I
fail the SRB_FUNCTION_CLAIM_DEVICE, I am receiving
IRP_MN_REMOVE_DEVICE for the disk FiDo.
Is there any work around for it in .net.
We also noticed that issue when moving our drivers to 2003.
To work around the problem we ended up putting a filter on
the ScsiPort. Then traped IRP_MN_QUERY_DEVICE_RELATIONS
You can walk through all the relations yourself and then call
your own AddDevice routine for the LUN. In your add device
do you claim, devicecreate, attach, etc… Then you need to
make sure you don’t expose the LUN as a GenDisk.