DeviceIOControl to mouse driver..

Hi,

We are developing a USB mouse driver and also its utility..
If the class name was assigend as USB in the inf file (ie, the deivce
would be listed in the USB in the device manager), we find our utility
could communicate with our own mouse driver without any issue. Well,
if we change the class name from USB to Mouse in the inf file..(ie.,
the device would be listed under Mouse in the device manager).. the
same code "DeviceIOControl" would return an error code "1" (Invalid
function)... Could anyone provide a hint for that.. Thanks.

-chueh8

Maxim
Wed Aug 02 06:06:20 CDT 2006

Why USB mouse requires any additional drivers? I think all necessary
drivers are provided by MS, aren't they?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"chueh8" <steelchueh@gmail.com> wrote in message
news:1154504771.337166.145580@m73g2000cwd.googlegroups.com...
> Hi,
>
> We are developing a USB mouse driver and also its utility..
> If the class name was assigend as USB in the inf file (ie, the deivce
> would be listed in the USB in the device manager), we find our utility
> could communicate with our own mouse driver without any issue. Well,
> if we change the class name from USB to Mouse in the inf file..(ie.,
> the device would be listed under Mouse in the device manager).. the
> same code "DeviceIOControl" would return an error code "1" (Invalid
> function)... Could anyone provide a hint for that.. Thanks.
>
> -chueh8
>

Marc
Wed Aug 02 15:27:44 CDT 2006

A setup class of USB is not appropriate for a mouse.

From the DDK docs: "This class includes USB host controllers and USB hubs,
but not USB peripherals. Drivers for this class are system-supplied."

Microsoft OSs open devices with setup class of MOUSE exclusively.

Marco
________________________
Marc Reinig
UCO/Lick Observatory
Laboratory for Adaptive Optics

"chueh8" <steelchueh@gmail.com> wrote in message
news:1154504771.337166.145580@m73g2000cwd.googlegroups.com...
> Hi,
>
> We are developing a USB mouse driver and also its utility..
> If the class name was assigend as USB in the inf file (ie, the deivce
> would be listed in the USB in the device manager), we find our utility
> could communicate with our own mouse driver without any issue. Well,
> if we change the class name from USB to Mouse in the inf file..(ie.,
> the device would be listed under Mouse in the device manager).. the
> same code "DeviceIOControl" would return an error code "1" (Invalid
> function)... Could anyone provide a hint for that.. Thanks.
>
> -chueh8
>

chueh8
Wed Aug 02 19:05:27 CDT 2006

sorry, not quite get what you said.. perhaps my descriptions are not
complete..
my device is a usb touch screen,, in the inf file, we assign it to
MOUSE class and also include msmouse.inf for the mouclass driver..
after installing it, we would find our device was listed as a mouse
(not HID mouse) in the device manager, the driver details including
our own driver and mouclass.sys.
Since we'd like to send some our own deviceiocontrol command to our
driver for controlling the the touch panel, but in the user utility, we
found devieiocontrol would return system error code with 1.(invalid
function)... once we change the class name to USB in the inf file..
that is no more mouclass.sys included, the same user utiltiy could
communicate with our driver with deviceiocontrol without issue.. Is
the mouclass reject our request? Any hint for that... thanks.



Marc Reinig =E5=AF=AB=E9=81=93=EF=BC=9A

> A setup class of USB is not appropriate for a mouse.
>
> From the DDK docs: "This class includes USB host controllers and USB hubs,
> but not USB peripherals. Drivers for this class are system-supplied."
>
> Microsoft OSs open devices with setup class of MOUSE exclusively.
>
> Marco
> ________________________
> Marc Reinig
> UCO/Lick Observatory
> Laboratory for Adaptive Optics
>
> "chueh8" <steelchueh@gmail.com> wrote in message
> news:1154504771.337166.145580@m73g2000cwd.googlegroups.com...
> > Hi,
> >
> > We are developing a USB mouse driver and also its utility..
> > If the class name was assigend as USB in the inf file (ie, the deivce
> > would be listed in the USB in the device manager), we find our utility
> > could communicate with our own mouse driver without any issue. Well,
> > if we change the class name from USB to Mouse in the inf file..(ie.,
> > the device would be listed under Mouse in the device manager).. the
> > same code "DeviceIOControl" would return an error code "1" (Invalid
> > function)... Could anyone provide a hint for that.. Thanks.
> >
> > -chueh8
> >

Doron
Wed Aug 02 22:58:09 CDT 2006

mouclass is rejecting all unknown ioctls. look at the kbfiltr example in the
KMDF distribution. it shows you how to enumerate a PDO so that your app can
talk to the filter. i would not recommend doing this in WDM either.

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.


"chueh8" <steelchueh@gmail.com> wrote in message
news:1154563527.876411.110280@m79g2000cwm.googlegroups.com...
sorry, not quite get what you said.. perhaps my descriptions are not
complete..
my device is a usb touch screen,, in the inf file, we assign it to
MOUSE class and also include msmouse.inf for the mouclass driver..
after installing it, we would find our device was listed as a mouse
(not HID mouse) in the device manager, the driver details including
our own driver and mouclass.sys.
Since we'd like to send some our own deviceiocontrol command to our
driver for controlling the the touch panel, but in the user utility, we
found devieiocontrol would return system error code with 1.(invalid
function)... once we change the class name to USB in the inf file..
that is no more mouclass.sys included, the same user utiltiy could
communicate with our driver with deviceiocontrol without issue.. Is
the mouclass reject our request? Any hint for that... thanks.



Marc Reinig ??:

> A setup class of USB is not appropriate for a mouse.
>
> From the DDK docs: "This class includes USB host controllers and USB hubs,
> but not USB peripherals. Drivers for this class are system-supplied."
>
> Microsoft OSs open devices with setup class of MOUSE exclusively.
>
> Marco
> ________________________
> Marc Reinig
> UCO/Lick Observatory
> Laboratory for Adaptive Optics
>
> "chueh8" <steelchueh@gmail.com> wrote in message
> news:1154504771.337166.145580@m73g2000cwd.googlegroups.com...
> > Hi,
> >
> > We are developing a USB mouse driver and also its utility..
> > If the class name was assigend as USB in the inf file (ie, the deivce
> > would be listed in the USB in the device manager), we find our utility
> > could communicate with our own mouse driver without any issue. Well,
> > if we change the class name from USB to Mouse in the inf file..(ie.,
> > the device would be listed under Mouse in the device manager).. the
> > same code "DeviceIOControl" would return an error code "1" (Invalid
> > function)... Could anyone provide a hint for that.. Thanks.
> >
> > -chueh8
> >