you don’t really filter a “driver” in Windows, you filter a device. For
each device the system discovers it looks into the registry and loads
one or more installed drivers and calls each to attach itself to the
device stack. Your filter could be one of these drivers.
During this attachment process, each driver calls the NTIO manager to
attach to the stack and gets back a pointer to the device below them.
They generally send all I/O to this device, so an upper level drivers’s
is automatically routed through yours for that device stack.
I’m not sure what you mean by “without distrubing the flow” - my guess
is that you want to do this even if clients are already using the disk.
There is no supported mechanism to attach your driver to a stack without
shutting down and restarting the device, which requires all clients to
close their handles to the device.
-p
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Amitrajit
Banerjee.
Sent: Thursday, June 09, 2005 4:28 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] attaching to disk.sys
hi ppl,
I want to write a filter driver that attaches itself to Disk.sys. Can
any one tell me how to go abt it. How do I get the registered name of
Disk.Sys and then How do I attach my driver to the stack without
disturbing the flow?
Once my driver is loaded, will all other drivers that used to load above
disk.sys automatically start pointing to my driver, or do I have to
write code to do so.
Please help. Source code examples would be very helpful.
amitr0
Note:-
- Spelling Mistakes and Grammatical Errors, If Any, Are Regretted.
- Kindly Acknowledge This Mail At The Earliest.
- This E-Mail Might contain Confidential information. If You Are Not
Entitled
To View it, Please Delete The Message Immediately And Inform Me.
Thanking You,
Amitrajit Banerjee.
http: — Questions?
First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently subscribed
to ntdev as: unknown lmsubst tag argument: ‘’ To unsubscribe send a
blank email to xxxxx@lists.osr.com</http:>