Install filter-driver for existing driver...
Tobias Erichsen
I扉e taken the TOASTER-example from the W2K-DDK and adapted it
to my needs (as far as I can tell) since I could not start it yet... I悲
like to
know how I can install this beast for an existing driver... are there any
(simple) example-infs or a description of what reg-keys must be set?
The filter.inf from the toaster-example is not really easy to understand,
but it seems that it wants to reinstall the toaster-driver...
Tobias
--
Gott hat gemeiert und sagte: 42!
Walter Oney
> I扉e taken the TOASTER-example from the W2K-DDK and adapted it
> to my needs (as far as I can tell) since I could not start it yet... I悲
> like to
> know how I can install this beast for an existing driver... are there any
> (simple) example-infs or a description of what reg-keys must be set?
> The filter.inf from the toaster-example is not really easy to understand,
> but it seems that it wants to reinstall the toaster-driver...
If you have my WDM book, the FILTER sample in ch. 9 has a DLL that will
"inject" a filter into the registry for any device you wish. Refer to
the FILTER.HTM file for details about how to use the DLL in an INF file.
[Actually, the sample is there whether or not you have the book...] I'm
not quite sure why, but Microsoft expects that people will only install
filters in conjunction with the function driver, which is (I guess) why
they've never provided tools to do it any other way.
--
Walter Oney
http://www.oneysoft.com
miheeh
I've tried what you posted.
I've installed IOCTL.sys and filter driver as explained in filter.html.
But I don't see any message from filter driver.
I tested IOCTL.sys with test.exe. I could find messages from IOCTL.sys but
filter.sys.
I can't sure whether filter driver is working or not.
I want to write filter driver for serial comm port.
thanks,
mihee
"Walter Oney" <walt...@oneysoft.com> wrote in message
news:3B9366E6...@oneysoft.com...
Walter Oney
> I've installed IOCTL.sys and filter driver as explained in filter.html.
> But I don't see any message from filter driver.
> I tested IOCTL.sys with test.exe. I could find messages from IOCTL.sys but
> filter.sys.
> I can't sure whether filter driver is working or not.
Well, FILTJECT.DLL won't produce any error messages, and even a minor
misspelling in the device description string would make it fail. Take a
quick look in the hardware key for IOCTL (enum\sample\xxxx) to see if
the UpperFilters or LowerFilters value got set. I'd suggest cutting and
pasting the device description string from the hardware key to you
FILJECT call to make sure everything is spelled right.
miheeh
It seems installed successfully. I can find UpperFilters has "filter" in
IOCTL key.
What I wonder, I've installed checked version of filter.sys, so I am
expecting messages
from filter.sys when ioctl.sys is processing IRP_MJ_CREATE, IRP_MJ_CLOSE,
IRP_MJ_PNP etc.
Am I wrong?
Also I want to know whether it is applicable for serial comm port filter
driver.
If so, Do I have to install upper filter for serial.sys??
Mihee
"Walter Oney" <walt...@oneysoft.com> wrote in message
news:3BA0B239...@oneysoft.com...
Tobias Erichsen
news:3BA0B239...@oneysoft.com...
> Well, FILTJECT.DLL won't produce any error messages, and even a minor
> misspelling in the device description string would make it fail. Take a
> quick look in the hardware key for IOCTL (enum\sample\xxxx) to see if
> the UpperFilters or LowerFilters value got set. I'd suggest cutting and
> pasting the device description string from the hardware key to you
> FILJECT call to make sure everything is spelled right.
OK - I finally received your book (2 times since amazon finally also
managed to deliver after I ordered it from another source ;-)
I tried to use your dll and a changed inf-file to do this. But it doesn´t
seem to work. Perhaps the driver I´m trying to filter is no WDM but
rather a standard NT/W2K-driver... I´m not sure if your script/dll
would also work in this case, or what I would need to tweak to get it
going... is there any registry-key I could check to see if the device
is WDM? Or is there any registry-key I could add to get it running?
Walter Oney
> I tried to use your dll and a changed inf-file to do this. But it doesn“t
> seem to work. Perhaps the driver I“m trying to filter is no WDM but
> rather a standard NT/W2K-driver... I“m not sure if your script/dll
> would also work in this case, or what I would need to tweak to get it
> going... is there any registry-key I could check to see if the device
> is WDM? Or is there any registry-key I could add to get it running?
You'd want to look in the Enum key in the registry. This is either under
HKEY_LOCAL_MACHINE (Windows systems) or
HKEY_LOCAL_MACHINE\CurrentControlSet (Win2K and Xp systems). The first
level of subkey is the enumerator (a/k/a bus driver in most cases), with
"root" being the enumerator for legacy devices. FILTJECT will add or
modify a binary (Windows systems) or MULTI_SZ (Win2K and Xp systems)
value named UpperFilters or LowerFilters. The first thing you should do
is to check to see if that happened. If not, the likely cause is a
difference in spelling of the device description or friendly name
string. If it *is* happening, then the filter should be loaded the next
time the device starts. In Windows, you'd need to reboot. In Win2K/Xp,
you could disable and re-enable the device in the Device Manager.