Prev: "Fake" Keyboard or Mouse driver
Next: Calling CreateFile / DeviceIOControl from a limited user accou
From: Ron on 9 Mar 2007 05:06
Hi,

I write a HID minidriver with standard Mouse and Keyboard report descriptors.
It is based on vhidmini in Windows Server 2003 DDK.
The driver work fine and I can read/write the report from the device.
The Device Manager shows it is HID-compliant device in HID class, but the
Mouse Class and Keyboard Class have none.
How should I do so that it can be a mouse device and keyboard device?
Should I modify the INF file? My driver's INF is almost same as the
vhidmini's.

Thanks
Ron
From: Owen Smith on 9 Mar 2007 10:03
I'm pretty sure you will need to break up hte device into a Mouse device
and Keyboard device. (i.e two drivers, one with a report descriptor for a
keyboard and one for a mouse)

The inf files should not refer to HID\MyVirtualHidDevice - these id's need
to be picked up from keyboard.inf or msmouse.inf - idealy reporting the
compatible id of HID_SYSTEM_KEYBOARD or HID_SYSTEM_MOUSE (i think)


On Fri, 09 Mar 2007 10:06:14 -0000, Ron <Ron(a)discussions.microsoft.com>
wrote:

> Hi,
>
> I write a HID minidriver with standard Mouse and Keyboard report
> descriptors.
> It is based on vhidmini in Windows Server 2003 DDK.
> The driver work fine and I can read/write the report from the device.
> The Device Manager shows it is HID-compliant device in HID class, but the
> Mouse Class and Keyboard Class have none.
> How should I do so that it can be a mouse device and keyboard device?
> Should I modify the INF file? My driver's INF is almost same as the
> vhidmini's.
>
> Thanks
> Ron



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
From: Doron Holan [MS] on 9 Mar 2007 22:58
you only need one HID minidriver. from it, a keyboard and a mouse can be
enumerated. you just have to put each device into its own top level
collection. If you are having trouble, i would find a USB HID that already
does this and look at its HID descriptor

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.


"Owen Smith" <osmith(a)saitek.com> wrote in message
news:op.toxf4vcimlchdc(a)oas-core2...
> I'm pretty sure you will need to break up hte device into a Mouse device
> and Keyboard device. (i.e two drivers, one with a report descriptor for a
> keyboard and one for a mouse)
>
> The inf files should not refer to HID\MyVirtualHidDevice - these id's need
> to be picked up from keyboard.inf or msmouse.inf - idealy reporting the
> compatible id of HID_SYSTEM_KEYBOARD or HID_SYSTEM_MOUSE (i think)
>
>
> On Fri, 09 Mar 2007 10:06:14 -0000, Ron <Ron(a)discussions.microsoft.com>
> wrote:
>
>> Hi,
>>
>> I write a HID minidriver with standard Mouse and Keyboard report
>> descriptors.
>> It is based on vhidmini in Windows Server 2003 DDK.
>> The driver work fine and I can read/write the report from the device.
>> The Device Manager shows it is HID-compliant device in HID class, but the
>> Mouse Class and Keyboard Class have none.
>> How should I do so that it can be a mouse device and keyboard device?
>> Should I modify the INF file? My driver's INF is almost same as the
>> vhidmini's.
>>
>> Thanks
>> Ron
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/


From: Ron on 10 Mar 2007 10:15
Thanks, it is helpful to me.
Actually, my hid minidriver contain 3 top level collections of report:
keyboard, mouse and cosumer control.
It is just same as the USB composite HID keyboard.
For the real USB device, I know Windows can enumerate it well.
But how the system enumerate the virtual HID device not only a HID class but
also Mouse class and keyboard class?

Ron

"Doron Holan [MS]" wrote:

> you only need one HID minidriver. from it, a keyboard and a mouse can be
> enumerated. you just have to put each device into its own top level
> collection. If you are having trouble, i would find a USB HID that already
> does this and look at its HID descriptor
>
> 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.
>
>
> "Owen Smith" <osmith(a)saitek.com> wrote in message
> news:op.toxf4vcimlchdc(a)oas-core2...
> > I'm pretty sure you will need to break up hte device into a Mouse device
> > and Keyboard device. (i.e two drivers, one with a report descriptor for a
> > keyboard and one for a mouse)
> >
> > The inf files should not refer to HID\MyVirtualHidDevice - these id's need
> > to be picked up from keyboard.inf or msmouse.inf - idealy reporting the
> > compatible id of HID_SYSTEM_KEYBOARD or HID_SYSTEM_MOUSE (i think)
> >
> >
> > On Fri, 09 Mar 2007 10:06:14 -0000, Ron <Ron(a)discussions.microsoft.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I write a HID minidriver with standard Mouse and Keyboard report
> >> descriptors.
> >> It is based on vhidmini in Windows Server 2003 DDK.
> >> The driver work fine and I can read/write the report from the device.
> >> The Device Manager shows it is HID-compliant device in HID class, but the
> >> Mouse Class and Keyboard Class have none.
> >> How should I do so that it can be a mouse device and keyboard device?
> >> Should I modify the INF file? My driver's INF is almost same as the
> >> vhidmini's.
> >>
> >> Thanks
> >> Ron
> >
> >
> >
> > --
> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>
>
>
From: Doron Holan [MS] on 10 Mar 2007 15:12
each top level collection is enumerated as its own child stack based on the
HID descriptor. if that is not happening for your HID miniport, there is a
bug in your HID descriptor

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.


"Ron" <Ron(a)discussions.microsoft.com> wrote in message
news:B6D01ABC-7524-4DB5-A5D3-E9C14508B396(a)microsoft.com...
> Thanks, it is helpful to me.
> Actually, my hid minidriver contain 3 top level collections of report:
> keyboard, mouse and cosumer control.
> It is just same as the USB composite HID keyboard.
> For the real USB device, I know Windows can enumerate it well.
> But how the system enumerate the virtual HID device not only a HID class
> but
> also Mouse class and keyboard class?
>
> Ron
>
> "Doron Holan [MS]" wrote:
>
>> you only need one HID minidriver. from it, a keyboard and a mouse can be
>> enumerated. you just have to put each device into its own top level
>> collection. If you are having trouble, i would find a USB HID that
>> already
>> does this and look at its HID descriptor
>>
>> 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.
>>
>>
>> "Owen Smith" <osmith(a)saitek.com> wrote in message
>> news:op.toxf4vcimlchdc(a)oas-core2...
>> > I'm pretty sure you will need to break up hte device into a Mouse
>> > device
>> > and Keyboard device. (i.e two drivers, one with a report descriptor for
>> > a
>> > keyboard and one for a mouse)
>> >
>> > The inf files should not refer to HID\MyVirtualHidDevice - these id's
>> > need
>> > to be picked up from keyboard.inf or msmouse.inf - idealy reporting the
>> > compatible id of HID_SYSTEM_KEYBOARD or HID_SYSTEM_MOUSE (i think)
>> >
>> >
>> > On Fri, 09 Mar 2007 10:06:14 -0000, Ron <Ron(a)discussions.microsoft.com>
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> I write a HID minidriver with standard Mouse and Keyboard report
>> >> descriptors.
>> >> It is based on vhidmini in Windows Server 2003 DDK.
>> >> The driver work fine and I can read/write the report from the device.
>> >> The Device Manager shows it is HID-compliant device in HID class, but
>> >> the
>> >> Mouse Class and Keyboard Class have none.
>> >> How should I do so that it can be a mouse device and keyboard device?
>> >> Should I modify the INF file? My driver's INF is almost same as the
>> >> vhidmini's.
>> >>
>> >> Thanks
>> >> Ron
>> >
>> >
>> >
>> > --
>> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>>
>>
>>


 |  Next  |  Last
Pages: 1 2
Prev: "Fake" Keyboard or Mouse driver
Next: Calling CreateFile / DeviceIOControl from a limited user accou