No prob. Remember that this filter will not work on NT4, only on
W2K/XP/.NET. If you need to filter volumes for NT4 let me know and I’ll
explain how it’s done.
-----Original Message-----
From: Nicholas Kidd [mailto:kidd@cs.wisc.edu]
Sent: Friday, November 22, 2002 1:55 PM
To: File Systems Developers
Subject: [ntfsd] RE: filter driver location question
Nate-
I want to again thank you for all of your help. The filter driver is
up and running 
I think I just misread your previous email when you
said to create the filter as an upper class VOLUME filter. oops.
Thanks again,
-nick
On Fri, Nov 22, 2002 at 09:33:26AM -0700, Nate Bushman wrote:
Nicholas,
Again, you should use an upper filter on the Volume device class. Why
filter DiskDrive devices? That just adds a lot more work for you,
having to distinguish which volume I/O is targeted at. If you filter
volumes then you’re already there. Just use the XP DDK Toaster Filter
sample AS IS and make the necessary settings in the registry so that
the
driver will filter volumes. It already has the code in place to
attach
filter device objects to any volume devices that are created. Build
it,
install it, reboot and then look in DeviceTree and you’ll see the
filter
device objects attached to the volumes. The only device object I can
see you needing to create (to add code for) is one that’s meant to
receive custom IOCTLs that you define for controlling your driver. I
don’t believe the toaster filter creates a control device object, but
it’s been a while since I looked at it. How to do that (securely) is
another story.Nate Bushman
PowerQuest Corp
You are currently subscribed to ntfsd as: xxxxx@powerquest.com
To unsubscribe send a blank email to %%email.unsub%%