Hi,
Has anyone tried to develope File system driver using class FilterDevice in
Numega’s DriverStudio?
I’ ve used one of the samples to build the FS Filter, but no activity is
filtered. NuMega answered me, that this class is universal for all
types of filters.
If someone tried this, please, show me how.
Hi,
The first problem is that Numega DriverWorks doesn’t support Fast Io; you
have to add Fast IO support yourself.
I am having problems with the KFilterDevice in Windows 2000.
The system used by KFilterDevice to attach a DEVICE_OBJECT doesn’t work
well in Windows NT/2000.
You must obtain the device characteristics before creating the device;
Numega doesn’t do it for you.
I have developed a FSFD with DriverWorks but I use my own class derived
from KDevice; I don’t use KFilterDevice.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
andrew@at.pstu.ac.ru
Sent: martes, 19 de septiembre de 2000 7:12
To: File Systems Developers
Subject: [ntfsd] Driver::Works with FileSystem filters
Hi,
Has anyone tried to develope File system driver using class FilterDevice in
Numega’s DriverStudio?
I’ ve used one of the samples to build the FS Filter, but no activity is
filtered. NuMega answered me, that this class is universal for all
types of filters.
If someone tried this, please, show me how.
You are currently subscribed to ntfsd as: xxxxx@trymedia.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
I have developed a File System Driver using NuMega’s Driver Studio, but I
developed my own filter class based on class KDevice, because the
KFilterDevice class can only attach to a named object (according to my
Docs). A file system filter driver has to derive the device object pointer
in a roundabout means, you cannot just attach to \Device\Fastfat (or
NTFS). Hence the reason for my own class. See FileMon to see how one does
this.
Another point you have to be aware of, is the fast path of the file system.
You should support this thru setting the appropiate pointer in the
PDRIVER_OBJECT->FastIoDispatch, however, if you do this, any other devices
attached to this driver will have this fast path enabled (file system or
not), in this case you should check to make sure that fast path is relevant
to the appropiate class, if not, then return FALSE;
John Tobin
----- Original Message -----
From:
To: “File Systems Developers”
Sent: Monday, September 18, 2000 10:11 PM
Subject: [ntfsd] Driver::Works with FileSystem filters
>
>
>
> Hi,
> Has anyone tried to develope File system driver using class FilterDevice
in
> Numega’s DriverStudio?
> I’ ve used one of the samples to build the FS Filter, but no activity is
> filtered. NuMega answered me, that this class is universal for all
> types of filters.
> If someone tried this, please, show me how.
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@paceap.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
John,
If I have an existing driver, how can I use DriverStudio to just “Bounds
Check” what I have already built?
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of John Tobin
Sent: Tuesday, September 19, 2000 12:49 PM
To: File Systems Developers
Subject: [ntfsd] Re: Driver::Works with FileSystem filters
I have developed a File System Driver using NuMega’s Driver Studio, but I
developed my own filter class based on class KDevice, because the
KFilterDevice class can only attach to a named object (according to my
Docs). A file system filter driver has to derive the device object pointer
in a roundabout means, you cannot just attach to \Device\Fastfat (or
NTFS). Hence the reason for my own class. See FileMon to see how one does
this.
Another point you have to be aware of, is the fast path of the file system.
You should support this thru setting the appropiate pointer in the
PDRIVER_OBJECT->FastIoDispatch, however, if you do this, any other devices
attached to this driver will have this fast path enabled (file system or
not), in this case you should check to make sure that fast path is relevant
to the appropiate class, if not, then return FALSE;
John Tobin
----- Original Message -----
From:
To: “File Systems Developers”
Sent: Monday, September 18, 2000 10:11 PM
Subject: [ntfsd] Driver::Works with FileSystem filters
>
>
>
> Hi,
> Has anyone tried to develope File system driver using class FilterDevice
in
> Numega’s DriverStudio?
> I’ ve used one of the samples to build the FS Filter, but no activity is
> filtered. NuMega answered me, that this class is universal for all
> types of filters.
> If someone tried this, please, show me how.
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@paceap.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
—
You are currently subscribed to ntfsd as: xxxxx@legato.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
If you are talking about BoundsChecker, I haven’t actually used it yet, but
I am planning to use it soon.
I think that boundschecker can bounds check any driver. I don’t think that
it is specific to Driver Studio only drivers.
John
----- Original Message -----
From: “Ken Galipeau”
To: “File Systems Developers”
Sent: Thursday, September 21, 2000 9:44 AM
Subject: [ntfsd] Re: Driver::Works with FileSystem filters
> John,
> If I have an existing driver, how can I use DriverStudio to just “Bounds
> Check” what I have already built?
> Ken
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of John Tobin
> Sent: Tuesday, September 19, 2000 12:49 PM
> To: File Systems Developers
> Subject: [ntfsd] Re: Driver::Works with FileSystem filters
>
>
> I have developed a File System Driver using NuMega’s Driver Studio, but I
> developed my own filter class based on class KDevice, because the
> KFilterDevice class can only attach to a named object (according to my
> Docs). A file system filter driver has to derive the device object pointer
> in a roundabout means, you cannot just attach to \Device\Fastfat (or
> NTFS). Hence the reason for my own class. See FileMon to see how one does
> this.
>
> Another point you have to be aware of, is the fast path of the file
system.
> You should support this thru setting the appropiate pointer in the
> PDRIVER_OBJECT->FastIoDispatch, however, if you do this, any other devices
> attached to this driver will have this fast path enabled (file system or
> not), in this case you should check to make sure that fast path is
relevant
> to the appropiate class, if not, then return FALSE;
>
> John Tobin
>
>
> ----- Original Message -----
> From:
> To: “File Systems Developers”
> Sent: Monday, September 18, 2000 10:11 PM
> Subject: [ntfsd] Driver::Works with FileSystem filters
>
>
> >
> >
> >
> > Hi,
> > Has anyone tried to develope File system driver using class FilterDevice
> in
> > Numega’s DriverStudio?
> > I’ ve used one of the samples to build the FS Filter, but no activity is
> > filtered. NuMega answered me, that this class is universal for all
> > types of filters.
> > If someone tried this, please, show me how.
> >
> >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@paceap.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> >
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@legato.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@paceap.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>