From: Mike Carlisle on 5 Dec 2006 15:06 Thanks for your help, that helps me understand what's going a little clearer. "Eliyas Yakub [MSFT]" wrote: > Ctrlcap filter is installed as a class filter. This filter was originally > written for NT4.0 by sysinternals and ported to Win2K. This filter doesn't > work well in scenarios - terminal server, SMS, etc, and I would strongly > discourage you from using this filter. This filter sits above the kbdclass > filter driver. > > The filter driver present in the WDK (both WDF and WDM versions) is a device > filter. This filter is intended to filter just PS/2 device. It sits > between the kbdclass and i8042prt driver. You install such a filter a full > fledged pnp device INF. You cannot install a device filter by right > clicking on the INF file. The information about device filters is added to > the device enum key as opposed to class key for class filters. The sample > contains an INF that shows how to install this filter. > > If you want your filter driver to filter all device types (USB, PS2, etc) > then you can install this filter as class filter using the install app > provided with the ctrlcap but as you figured out by prepending your filter > service before the kdbclass. That way your filter sits below the kbdclass > filter. > > -Eliyas > > >
First
|
Prev
|
Pages: 1 2 Prev: IoReadPartitionTableEx() on Windows Vista Next: WSD port name and IPBusEnumRoot mapping |