Problem receiving IOCTLS

Hi All,
I have a USB Client Driver which uses Mouse Class Service.Basically I
have got a .inf file,in which i have specified Mouse Class as the service
installer for my USB Device.The problem is I don’t receive IOCTLS from the
Application.The Error Code which the application receives on issuing
DeviceIoControl is 1(ERROR_INVALID_FUNCTION).I have checked for the
registration of IRP_MJ_DEVICE_CONTROL in my driver.Can any body please let
me know why does the application receive this ?.

Thanks.
Best Regards,
Sai Prasad
**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************

Mouclass does not allow random IOCTLs down the stack; if you are using
HID, you are better off creating a 2ndary top level collection whose
features correspond to your IOCTLs and communicating to your driver this
way.

d

-----Original Message-----
From: Sai_Prasad [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 20, 2002 10:18 PM
To: NT Developers Interest List
Subject: [ntdev] Problem receiving IOCTLS

Hi All,
I have a USB Client Driver which uses Mouse Class Service.Basically I
have got a .inf file,in which i have specified Mouse Class as the
service
installer for my USB Device.The problem is I don’t receive IOCTLS from
the
Application.The Error Code which the application receives on issuing
DeviceIoControl is 1(ERROR_INVALID_FUNCTION).I have checked for the
registration of IRP_MJ_DEVICE_CONTROL in my driver.Can any body please
let
me know why does the application receive this ?.

Thanks.
Best Regards,
Sai Prasad
************************************************************************
**
This email (including any attachments) is intended for the sole use of
the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
or
distribution or forwarding of any or all of the contents in this message
is
STRICTLY PROHIBITED. If you are not the intended recipient, please
contact
the sender by email and delete all copies; your cooperation in this
regard
is appreciated.
************************************************************************
**


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to %%email.unsub%%

Hi Doron,
Actually I am not using HID.Is there any way by which I can make the
application target the IOCTL’s directly to my driver.

Thanks.
Best Regards,
Sai Prasad


From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Friday, June 21, 2002 10:59 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Problem receiving IOCTLS

Mouclass does not allow random IOCTLs down the stack; if you are using
HID, you are better off creating a 2ndary top level collection whose
features correspond to your IOCTLs and communicating to your driver this
way.

d

-----Original Message-----
From: Sai_Prasad [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 20, 2002 10:18 PM
To: NT Developers Interest List
Subject: [ntdev] Problem receiving IOCTLS

Hi All,
I have a USB Client Driver which uses Mouse Class Service.Basically I
have got a .inf file,in which i have specified Mouse Class as the
service
installer for my USB Device.The problem is I don’t receive IOCTLS from
the
Application.The Error Code which the application receives on issuing
DeviceIoControl is 1(ERROR_INVALID_FUNCTION).I have checked for the
registration of IRP_MJ_DEVICE_CONTROL in my driver.Can any body please
let
me know why does the application receive this ?.

Thanks.
Best Regards,
Sai Prasad
************************************************************************
**
This email (including any attachments) is intended for the sole use of
the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
or
distribution or forwarding of any or all of the contents in this message
is
STRICTLY PROHIBITED. If you are not the intended recipient, please
contact
the sender by email and delete all copies; your cooperation in this
regard
is appreciated.
************************************************************************
**


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@bla.satyam.com
To unsubscribe send a blank email to %%email.unsub%%

**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************

create a 2ndary devobj in your driver that is not attached to the pnp device stack (ie, you just make another call to IoCreateDevice in start device). this devobj must have a name and a symbolic link associated with it; you cannot use a device interface for the 2ndary devobj b/c you need a PDO for that. After that, you must route irps appropriate in each dispatch function (you will even get PNP irps to the non PNP devobj to find target relations). The usual method of doing this is sharing a common header between both device extensions and a field in the header indicates the type of devobj the IRP is destined for.

d

-----Original Message-----
From: Sai_Prasad [mailto:xxxxx@Satyam.com]
Sent: Thu 6/20/2002 11:21 PM
To: NT Developers Interest List
Cc:
Subject: [ntdev] RE: Problem receiving IOCTLS

Hi Doron,
Actually I am not using HID.Is there any way by which I can make the
application target the IOCTL’s directly to my driver.

Thanks.
Best Regards,
Sai Prasad
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 21, 2002 10:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Problem receiving IOCTLS
>
> Mouclass does not allow random IOCTLs down the stack; if you are using
> HID, you are better off creating a 2ndary top level collection whose
> features correspond to your IOCTLs and communicating to your driver this
> way.
>
> d
>
> -----Original Message-----
> From: Sai_Prasad [mailto:xxxxx@Satyam.com]
> Sent: Thursday, June 20, 2002 10:18 PM
> To: NT Developers Interest List
> Subject: [ntdev] Problem receiving IOCTLS
>
> Hi All,
> I have a USB Client Driver which uses Mouse Class Service.Basically I
> have got a .inf file,in which i have specified Mouse Class as the
> service
> installer for my USB Device.The problem is I don’t receive IOCTLS from
> the
> Application.The Error Code which the application receives on issuing
> DeviceIoControl is 1(ERROR_INVALID_FUNCTION).I have checked for the
> registration of IRP_MJ_DEVICE_CONTROL in my driver.Can any body please
> let
> me know why does the application receive this ?.
>
> Thanks.
> Best Regards,
> Sai Prasad
> ************************************************************************
> **
> This email (including any attachments) is intended for the sole use of
> the
> intended recipient/s and may contain material that is CONFIDENTIAL AND
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
> or
> distribution or forwarding of any or all of the contents in this message
> is
> STRICTLY PROHIBITED. If you are not the intended recipient, please
> contact
> the sender by email and delete all copies; your cooperation in this
> regard
> is appreciated.
> ************************************************************************
> **
>
> —
> You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
> —
> You are currently subscribed to ntdev as: xxxxx@bla.satyam.com
> To unsubscribe send a blank email to %%email.unsub%%
>
**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com