Re: Upper filter driver - attaching to devices by Doron
Doron
Fri Mar 21 12:59:55 CDT 2008
for a device upper filter, yes an INF. for a class filter you can hand edit
the registry for testing, for deployment an installer is needed. note that
the name you quote below is not guaranteed to be the same from boot to boot.
what type of device are you trying to filter? what are you trying to do in
your filter?
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
<km7kumar@gmail.com> wrote in message
news:24c1a768-f5a3-4ae7-9da9-4f5b24ba3ee3@s19g2000prg.googlegroups.com...
> On Mar 21, 9:21 am, "Doron Holan [MSFT]" <dor...@online.microsoft.com>
> wrote:
>> why are you not specifying your filter through the device node or class
>> key
>> and then pnp will automatically load your driver in the right context for
>> you to attach. what type of names are you using?
>>
>> d
>>
>> --
>> Please do not send e-mail directly to this alias. this alias is for
>> newsgroup purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> <km7ku...@gmail.com> wrote in message
>>
>> news:46b9645c-e3e7-4a01-b162-6476a568f4c7@d21g2000prf.googlegroups.com...
>>
>> > I'm using IoAttachDevice. It returns OBJECT_NAME_NOT_FOUND. I'm using
>> > the same device name as shown by irptracker and devicetree utilities.
>>
>> > Any ideas? Also, are they any other methods to attach to a lower
>> > device?
>>
>> > Thanks
>> > /kmk
>
> I'm using "\\Device\\000000c9". This is what DeviceTree utility shows
> when I browse to the
> driver I am trying to filter.
>
>>> why are you not specifying your filter through the device node or class
>>> key
>> and then pnp will automatically load your driver in the right context for
>> you to attach.
>
> How do I do this? through .inf file?
>
> thanks