I am trying to write a FS filter driver that will notify when a file is opened, closed and written. Currently I am handeling only IRP_MJ_CREATE, IRP_MJ_WRITE, IRP_MJ_CLOSE and all other IRP, I pass to next driver. But I dont know why it throw an exception after some time. Is there any issues that I must consider during driver writing?
On Fri, 18 May 2007 03:09:32 -0400 (EDT), xxxxx@yahoo.com
wrote:
Hi All,
I am trying to write a FS filter driver that will notify when a file is opened, closed and written. Currently I am handeling only IRP_MJ_CREATE, IRP_MJ_WRITE, IRP_MJ_CLOSE and all other IRP, I pass to next driver. But I dont know why it throw an exception after some time. Is there any issues that I must consider during driver writing?
Without knowing what type of exception happened, I don’t think anyone
here will be able too help you. You haven’t provided
enough info.
Given how you worded your question I assume your writing a legacy
filter; you really should be building a minifilter
instead. If you were, you could modify just a few lines in the scanner
sample and do exactly what your wanting too do with
a lot less hassle. Just modify the struct that is passed to usermode to
hold a wchar and strip out the fltreadfile code and
replace that with a fltgetfilename (something along those lines)…
I am trying to write a FS filter driver that will notify when a file is opened, closed and written. Currently I am handeling only IRP_MJ_CREATE, IRP_MJ_WRITE, IRP_MJ_CLOSE and all other IRP, I pass to next driver. But I dont know why it throw an exception after some time. Is there any issues that I must consider during driver writing?