Mouclass and legacy pointing device

OSR_Community_User · June 21, 2002, 3:00am

Dear All,

If i have a legacy pointing device, how do i make mouclass to
send INTERNAL_IOCL_MOUSE_CONNECT to my driver?

Is it enough if make a registry entry using CreateService funtion of SDK
mentioning the service as auto-start and kernel type? And then just make
an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver comes
up…OR do i need to do something more to make mouclass locate my
driver?

cheers
Sesha.

OSR_Community_User · June 21, 2002, 3:19am

the input model pre win2k (ie NT4 and before) was entirely load order based. Your driver needs to load and create the named device object before mouclass loads. I can’t remember if mouclass even enumerated the values in the key or it just starts trying to open \Device\PointerPort in a loop. Keep in mind that the legacy method for attaching to an input port may be removed in future versions and IMO, should be converted to a PNP driver (where you don’t have to muck w/load order or named devobjs…).

d

-----Original Message-----
From: Seshagiri Babu [mailto:xxxxx@satyam.com]
Sent: Thu 6/20/2002 11:59 PM
To: NT Developers Interest List
Cc:
Subject: [ntdev] Mouclass and legacy pointing device

Dear All,

If i have a legacy pointing device, how do i make mouclass to
send INTERNAL_IOCL_MOUSE_CONNECT to my driver?

Is it enough if make a registry entry using CreateService funtion of SDK
mentioning the service as auto-start and kernel type? And then just make
an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver comes
up…OR do i need to do something more to make mouclass locate my
driver?

cheers
Sesha.

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

OSR_Community_User · June 21, 2002, 3:30am

D,
My device doesn’t have any hardware id with it. Now, do i need to create
an inf for this and if so what entries should i make in it?

And my driver is supposed to handle multiple devices.

cheers
Sesha.

From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Friday, June 21, 2002 12:16 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

the input model pre win2k (ie NT4 and before) was entirely load order
based. Your driver needs to load and create the named device object
before mouclass loads. I can’t remember if mouclass even enumerated the
values in the key or it just starts trying to open \Device\PointerPort
> in a loop. Keep in mind that the legacy method for attaching to an input
> port may be removed in future versions and IMO, should be converted to a
> PNP driver (where you don’t have to muck w/load order or named
> devobjs…).
>
> d
>
> -----Original Message-----
> From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> Sent: Thu 6/20/2002 11:59 PM
> To: NT Developers Interest List
> Cc:
> Subject: [ntdev] Mouclass and legacy pointing device
>
>
>
> Dear All,
>
> If i have a legacy pointing device, how do i make mouclass
> to
> send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
>
> Is it enough if make a registry entry using CreateService funtion of
> SDK
> mentioning the service as auto-start and kernel type? And then just
> make
> an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver comes
> up…OR do i need to do something more to make mouclass locate my
> driver?
>
> cheers
> Sesha.
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@windows.microsoft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
>

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.

OSR_Community_User · June 21, 2002, 3:38am

you will need to manually create a hardware ID (I would use a GUID, easily very “unique”) for your device and then create an application to install it as a root enumerated device; you cannot add a new pointer class device through add new hardware. There are examples in the DDK (sorry, I can’t remember which) which demonstrate how to do this.

As for the multiple devices, you have 3 choices:

create a root enumerated device for each possible pointer port and report the data independently
create one root enumerated device and your device driver is a bus driver, enumerating children however you detect your multiple input devices
you have one root enumerated device and report all of the devices through the one device object

in the end, if you pick either 1 or 2, the raw input thread will merge the data back into one stream, so one could argue that you can forgo the complexity of the first 2 options and go for number 3.

d

-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Satyam.com]
Sent: Fri 6/21/2002 12:21 AM
To: NT Developers Interest List
Cc:
Subject: [ntdev] RE: Mouclass and legacy pointing device

D,
My device doesn’t have any hardware id with it. Now, do i need to create
an inf for this and if so what entries should i make in it?

And my driver is supposed to handle multiple devices.

cheers
Sesha.

> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 21, 2002 12:16 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Mouclass and legacy pointing device
>
> the input model pre win2k (ie NT4 and before) was entirely load order
> based. Your driver needs to load and create the named device object
> before mouclass loads. I can’t remember if mouclass even enumerated the
> values in the key or it just starts trying to open \Device\PointerPort
> in a loop. Keep in mind that the legacy method for attaching to an input
> port may be removed in future versions and IMO, should be converted to a
> PNP driver (where you don’t have to muck w/load order or named
> devobjs…).
>
> d
>
> -----Original Message-----
> From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> Sent: Thu 6/20/2002 11:59 PM
> To: NT Developers Interest List
> Cc:
> Subject: [ntdev] Mouclass and legacy pointing device
>
>
>
> Dear All,
>
> If i have a legacy pointing device, how do i make mouclass
> to
> send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
>
> Is it enough if make a registry entry using CreateService funtion of
> SDK
> mentioning the service as auto-start and kernel type? And then just
> make
> an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver comes
> up…OR do i need to do something more to make mouclass locate my
> driver?
>
> cheers
> Sesha.
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@windows.microsoft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
>
**************************************************************************
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

OSR_Community_User · June 28, 2002, 2:06am

Doron,
You have mentioned that the driver should be converted to a pnp
driver. If the driver is a legacy one, will the driver pass thru WHQL test
for Windows 2k and XP versions?

From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Friday, June 21, 2002 12:16 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

the input model pre win2k (ie NT4 and before) was entirely load order
based. Your driver needs to load and create the named device object
before mouclass loads. I can’t remember if mouclass even enumerated the
values in the key or it just starts trying to open \Device\PointerPort
> in a loop. Keep in mind that the legacy method for attaching to an input
> port may be removed in future versions and IMO, should be converted to a
> PNP driver (where you don’t have to muck w/load order or named
> devobjs…).
>
> d
>
> -----Original Message-----
> From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> Sent: Thu 6/20/2002 11:59 PM
> To: NT Developers Interest List
> Cc:
> Subject: [ntdev] Mouclass and legacy pointing device
>
>
>
> Dear All,
>
> If i have a legacy pointing device, how do i make mouclass
> to
> send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
>
> Is it enough if make a registry entry using CreateService funtion of
> SDK
> mentioning the service as auto-start and kernel type? And then just
> make
> an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver comes
> up…OR do i need to do something more to make mouclass locate my
> driver?
>
> cheers
> Sesha.
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@windows.microsoft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
>

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.

OSR_Community_User · June 28, 2002, 2:15am

No, it will not pass the tests.

d

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 27, 2002 10:57 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

Doron,
You have mentioned that the driver should be converted to a pnp
driver. If the driver is a legacy one, will the driver pass thru WHQL
test
for Windows 2k and XP versions?

From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Friday, June 21, 2002 12:16 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

the input model pre win2k (ie NT4 and before) was entirely load order
based. Your driver needs to load and create the named device object
before mouclass loads. I can’t remember if mouclass even enumerated
the
values in the key or it just starts trying to open
\Device\PointerPort
> in a loop. Keep in mind that the legacy method for attaching to an
input
> port may be removed in future versions and IMO, should be converted to
a
> PNP driver (where you don’t have to muck w/load order or named
> devobjs…).
>
> d
>
> -----Original Message-----
> From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> Sent: Thu 6/20/2002 11:59 PM
> To: NT Developers Interest List
> Cc:
> Subject: [ntdev] Mouclass and legacy pointing device
>
>
>
> Dear All,
>
> If i have a legacy pointing device, how do i make
mouclass
> to
> send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
>
> Is it enough if make a registry entry using CreateService
funtion of
> SDK
> mentioning the service as auto-start and kernel type? And then
just
> make
> an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver
comes
> up…OR do i need to do something more to make mouclass
locate my
> driver?
>
> cheers
> Sesha.
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@windows.microsoft.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
>
**********************************************************************

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%%

OSR_Community_User · June 28, 2002, 2:44am

Do any driver i write for Windows Me need to be a pnp one to pass WHQL test?

From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Thursday, June 27, 2002 11:12 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

No, it will not pass the tests.

d

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 27, 2002 10:57 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

Doron,
You have mentioned that the driver should be converted to a pnp
driver. If the driver is a legacy one, will the driver pass thru WHQL
test
for Windows 2k and XP versions?

> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 21, 2002 12:16 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Mouclass and legacy pointing device
>
> the input model pre win2k (ie NT4 and before) was entirely load order
> based. Your driver needs to load and create the named device object
> before mouclass loads. I can’t remember if mouclass even enumerated
the
> values in the key or it just starts trying to open
\Device\PointerPort
> > in a loop. Keep in mind that the legacy method for attaching to an
> input
> > port may be removed in future versions and IMO, should be converted to
> a
> > PNP driver (where you don’t have to muck w/load order or named
> > devobjs…).
> >
> > d
> >
> > -----Original Message-----
> > From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> > Sent: Thu 6/20/2002 11:59 PM
> > To: NT Developers Interest List
> > Cc:
> > Subject: [ntdev] Mouclass and legacy pointing device
> >
> >
> >
> > Dear All,
> >
> > If i have a legacy pointing device, how do i make
> mouclass
> > to
> > send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
> >
> > Is it enough if make a registry entry using CreateService
> funtion of
> > SDK
> > mentioning the service as auto-start and kernel type? And then
> just
> > make
> > an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver
> comes
> > up…OR do i need to do something more to make mouclass
> locate my
> > driver?
> >
> > cheers
> > Sesha.
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@windows.microsoft.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> > b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
> >
>
>
> 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@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.
********

OSR_Community_User · June 28, 2002, 11:10am

Windows ME is a different beast; there are no restrictions in that space
(with regard to pnp) if I remember correctly.

D

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 27, 2002 11:35 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

Do any driver i write for Windows Me need to be a pnp one to pass WHQL
test?

From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Thursday, June 27, 2002 11:12 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

No, it will not pass the tests.

d

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Satyam.com]
Sent: Thursday, June 27, 2002 10:57 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Mouclass and legacy pointing device

Doron,
You have mentioned that the driver should be converted to a pnp
driver. If the driver is a legacy one, will the driver pass thru WHQL
test
for Windows 2k and XP versions?

> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 21, 2002 12:16 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Mouclass and legacy pointing device
>
> the input model pre win2k (ie NT4 and before) was entirely load
order
> based. Your driver needs to load and create the named device object
> before mouclass loads. I can’t remember if mouclass even
enumerated
the
> values in the key or it just starts trying to open
\Device\PointerPort
> > in a loop. Keep in mind that the legacy method for attaching to an
> input
> > port may be removed in future versions and IMO, should be converted
to
> a
> > PNP driver (where you don’t have to muck w/load order or named
> > devobjs…).
> >
> > d
> >
> > -----Original Message-----
> > From: Seshagiri Babu [mailto:xxxxx@satyam.com]
> > Sent: Thu 6/20/2002 11:59 PM
> > To: NT Developers Interest List
> > Cc:
> > Subject: [ntdev] Mouclass and legacy pointing device
> >
> >
> >
> > Dear All,
> >
> > If i have a legacy pointing device, how do i make
> mouclass
> > to
> > send INTERNAL_IOCL_MOUSE_CONNECT to my driver?
> >
> > Is it enough if make a registry entry using CreateService
> funtion of
> > SDK
> > mentioning the service as auto-start and kernel type? And then
> just
> > make
> > an entry in HKLM\Hardware\DeviceMap\PointerPort when my driver
> comes
> > up…OR do i need to do something more to make mouclass
> locate my
> > driver?
> >
> > cheers
> > Sesha.
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@windows.microsoft.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> > b.?&v?'?j?ij?&N`rzgujy?^j?]V^X,?&
> >
>
**********************************************************************
>
> 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@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 %%email.unsub%%