Dear All,
I couldn’t find any documentation for this RIT on the internet or
elsewhere. Can anyone tell me the functionality of RIT. Is it true that RIT
is the one which sends IRP_MJ_READ requests to drivers like mouclass and
kbdclass…
cheers
Sesha.
**************************************************************************
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.
**************************************************************************
Yes, the raw input thread is the one that sends the reads for to
mouclass and kbdclass for keyboard and mouse input. If you want to add,
remove, or alter input data check out kbfiltr and moufiltr in the DDK.
It documents how do that with the appropriate interfaces. If you really
want to know how the RIT reads the data from the class drivers, both
mouclass and kbdclass are in the DDK as well.
d
-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
Sent: Friday, June 14, 2002 5:59 AM
To: NT Developers Interest List
Subject: [ntdev] RIT (Raw Input Thread)
Dear All,
I couldn’t find any documentation for this RIT on the internet
or elsewhere. Can anyone tell me the functionality of RIT. Is it true
that RIT is the one which sends IRP_MJ_READ requests to drivers like
mouclass and kbdclass…
cheers
Sesha.
************************************************************************
**
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 D,
Then i can assume the code of RIT to be like this :
no.of class objects = no.of kbdclass objects +
no. of mouclass objects
RITEntry()
{
for(i=0;i<no.of.classobjects> {
1. Allocate a Irp and fill the makor function as Read
2. Register a Completion routine
3. Send Irp to class object i
}
}
RITCompletionRoutine(…)
{
1. Do processing for kbd/mou data obtained , ie, put it on the global
input message queue
2. Allocate or Reuse Irp
3. Register completion routine
4. pass Irp to the class object
}
Are my assumptions true???
cheers
Sesha.
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 14, 2002 9:27 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Yes, the raw input thread is the one that sends the reads for to
> mouclass and kbdclass for keyboard and mouse input. If you want to add,
> remove, or alter input data check out kbfiltr and moufiltr in the DDK.
> It documents how do that with the appropriate interfaces. If you really
> want to know how the RIT reads the data from the class drivers, both
> mouclass and kbdclass are in the DDK as well.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 5:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RIT (Raw Input Thread)
>
>
> Dear All,
> I couldn’t find any documentation for this RIT on the internet
> or elsewhere. Can anyone tell me the functionality of RIT. Is it true
> that RIT is the one which sends IRP_MJ_READ requests to drivers like
> mouclass and kbdclass…
>
> cheers
> Sesha.
>
>
> 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.
********</no.of.classobjects>
> elsewhere. Can anyone tell me the functionality of RIT. Is it true
that RIT
is the one which sends IRP_MJ_READ requests to drivers like mouclass
and
kbdclass…
Yes.
RIT is inside win32k.sys.
RIT extracts the keyboard and mouse events from class drivers, and
then sends them to message queues of the particular threads who own
the appropriate windows.
IIRC some window manager’s hooks are also called by RIT.
Max
Not exactly :). All you need to know about the RIT is that it sends
down read requests as fast and as often as possible so that it can to
minimize latency for input.
d
-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
Sent: Friday, June 14, 2002 11:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
Hi D,
Then i can assume the code of RIT to be like this :
no.of class objects = no.of kbdclass objects +
no. of mouclass objects
RITEntry()
{
for(i=0;i<no.of.classobjects> {
1. Allocate a Irp and fill the makor function as Read
2. Register a Completion routine
3. Send Irp to class object i
}
}
RITCompletionRoutine(…)
{
1. Do processing for kbd/mou data obtained , ie, put it on the
global
input message queue
2. Allocate or Reuse Irp
3. Register completion routine
4. pass Irp to the class object
}
Are my assumptions true???
cheers
Sesha.
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 14, 2002 9:27 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Yes, the raw input thread is the one that sends the reads for to
> mouclass and kbdclass for keyboard and mouse input. If you want to
add,
> remove, or alter input data check out kbfiltr and moufiltr in the DDK.
> It documents how do that with the appropriate interfaces. If you
really
> want to know how the RIT reads the data from the class drivers, both
> mouclass and kbdclass are in the DDK as well.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 5:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RIT (Raw Input Thread)
>
>
> Dear All,
> I couldn’t find any documentation for this RIT on the internet
> or elsewhere. Can anyone tell me the functionality of RIT. Is it true
> that RIT is the one which sends IRP_MJ_READ requests to drivers like
> mouclass and kbdclass…
>
> cheers
> Sesha.
>
**********************************************************************
>
> 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 %%email.unsub%%</no.of.classobjects>
This is the perfect answer. You have more in this serie ? How much do I need
to know, or Im allowed to know ?
Best regards, Dan
----- Original Message -----
From: “Doron Holan”
To: “NT Developers Interest List”
Sent: Sunday, June 16, 2002 8:49 PM
Subject: [ntdev] RE: RIT (Raw Input Thread)
Not exactly :). All you need to know about the RIT is that it sends
down read requests as fast and as often as possible so that it can to
minimize latency for input.
d
-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
Sent: Friday, June 14, 2002 11:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
Hi D,
Then i can assume the code of RIT to be like this :
no.of class objects = no.of kbdclass objects +
no. of mouclass objects
RITEntry()
{
for(i=0;i<no.of.classobjects> {
1. Allocate a Irp and fill the makor function as Read
2. Register a Completion routine
3. Send Irp to class object i
}
}
RITCompletionRoutine(…)
{
1. Do processing for kbd/mou data obtained , ie, put it on the
global
input message queue
2. Allocate or Reuse Irp
3. Register completion routine
4. pass Irp to the class object
}
Are my assumptions true???
cheers
Sesha.
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 14, 2002 9:27 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Yes, the raw input thread is the one that sends the reads for to
> mouclass and kbdclass for keyboard and mouse input. If you want to
add,
> remove, or alter input data check out kbfiltr and moufiltr in the DDK.
> It documents how do that with the appropriate interfaces. If you
really
> want to know how the RIT reads the data from the class drivers, both
> mouclass and kbdclass are in the DDK as well.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 5:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RIT (Raw Input Thread)
>
>
> Dear All,
> I couldn’t find any documentation for this RIT on the internet
> or elsewhere. Can anyone tell me the functionality of RIT. Is it true
> that RIT is the one which sends IRP_MJ_READ requests to drivers like
> mouclass and kbdclass…
>
> cheers
> Sesha.
>
**********************************************************************
>
> 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 %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@rdsor.ro
To unsubscribe send a blank email to %%email.unsub%%</no.of.classobjects>
I am not trying to be obtuse, but basing a driver on how the RIT
operates is a recipe for disaster and does not port from release to
release. The algorithm for which the RIT reads from input devices
changes from release to release. Currently the basic algorithm uses a
mizture ZwReadFile, APCs, and a thread (hence the RIT 
).
What is of concern for input drivers is that reads come down fast and
quick and that they are completed as soon as data is available.
D
-----Original Message-----
From: Dan Partelly [mailto:xxxxx@rdsor.ro]
Sent: Tuesday, June 18, 2002 5:09 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
This is the perfect answer. You have more in this serie ? How much do I
need to know, or Im allowed to know ?
Best regards, Dan
----- Original Message -----
From: “Doron Holan”
To: “NT Developers Interest List”
Sent: Sunday, June 16, 2002 8:49 PM
Subject: [ntdev] RE: RIT (Raw Input Thread)
Not exactly :). All you need to know about the RIT is that it sends
down read requests as fast and as often as possible so that it can to
minimize latency for input.
d
-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
Sent: Friday, June 14, 2002 11:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
Hi D,
Then i can assume the code of RIT to be like this :
no.of class objects = no.of kbdclass objects +
no. of mouclass objects
RITEntry()
{
for(i=0;i<no.of.classobjects> {
1. Allocate a Irp and fill the makor function as Read
2. Register a Completion routine
3. Send Irp to class object i
}
}
RITCompletionRoutine(…)
{
1. Do processing for kbd/mou data obtained , ie, put it on the
global
input message queue
2. Allocate or Reuse Irp
3. Register completion routine
4. pass Irp to the class object
}
Are my assumptions true???
cheers
Sesha.
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 14, 2002 9:27 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Yes, the raw input thread is the one that sends the reads for to
> mouclass and kbdclass for keyboard and mouse input. If you want to
add,
> remove, or alter input data check out kbfiltr and moufiltr in the DDK.
> It documents how do that with the appropriate interfaces. If you
really
> want to know how the RIT reads the data from the class drivers, both
> mouclass and kbdclass are in the DDK as well.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 5:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RIT (Raw Input Thread)
>
>
> Dear All,
> I couldn’t find any documentation for this RIT on the internet or
> elsewhere. Can anyone tell me the functionality of RIT. Is it true
> that RIT is the one which sends IRP_MJ_READ requests to drivers like
> mouclass and kbdclass…
>
> cheers
> Sesha.
>
**********************************************************************
>
> 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 %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@rdsor.ro To
unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to %%email.unsub%%</no.of.classobjects>
I do understand your reasons, as enumerated here. Nor do I need to know
whats a PFN to write a driver.
Yet I try to learn.Because some ppl may be curious about things, simply
because they want to learn how
they are implemented, what particular solution was choosen, etc. Its
pasionating to learn new things about
OS internals, especially when you dedicate a large slice of your time
writting drivers for it.
Hence, I go berserk every time I heard “this is all you need…”.
Best regards, Dan
----- Original Message -----
From: “Doron Holan”
To: “NT Developers Interest List”
Sent: Wednesday, June 19, 2002 3:34 AM
Subject: [ntdev] RE: RIT (Raw Input Thread)
I am not trying to be obtuse, but basing a driver on how the RIT
operates is a recipe for disaster and does not port from release to
release. The algorithm for which the RIT reads from input devices
changes from release to release. Currently the basic algorithm uses a
mizture ZwReadFile, APCs, and a thread (hence the RIT ).
What is of concern for input drivers is that reads come down fast and
quick and that they are completed as soon as data is available.
D
-----Original Message-----
From: Dan Partelly [mailto:xxxxx@rdsor.ro]
Sent: Tuesday, June 18, 2002 5:09 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
This is the perfect answer. You have more in this serie ? How much do I
need to know, or Im allowed to know ?
Best regards, Dan
----- Original Message -----
From: “Doron Holan”
To: “NT Developers Interest List”
Sent: Sunday, June 16, 2002 8:49 PM
Subject: [ntdev] RE: RIT (Raw Input Thread)
Not exactly :). All you need to know about the RIT is that it sends
down read requests as fast and as often as possible so that it can to
minimize latency for input.
d
-----Original Message-----
From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
Sent: Friday, June 14, 2002 11:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
Hi D,
Then i can assume the code of RIT to be like this :
no.of class objects = no.of kbdclass objects +
no. of mouclass objects
RITEntry()
{
for(i=0;i<no.of.classobjects> {
1. Allocate a Irp and fill the makor function as Read
2. Register a Completion routine
3. Send Irp to class object i
}
}
RITCompletionRoutine(…)
{
1. Do processing for kbd/mou data obtained , ie, put it on the
global
input message queue
2. Allocate or Reuse Irp
3. Register completion routine
4. pass Irp to the class object
}
Are my assumptions true???
cheers
Sesha.
> ----------
> From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> Reply To: NT Developers Interest List
> Sent: Friday, June 14, 2002 9:27 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Yes, the raw input thread is the one that sends the reads for to
> mouclass and kbdclass for keyboard and mouse input. If you want to
add,
> remove, or alter input data check out kbfiltr and moufiltr in the DDK.
> It documents how do that with the appropriate interfaces. If you
really
> want to know how the RIT reads the data from the class drivers, both
> mouclass and kbdclass are in the DDK as well.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 5:59 AM
> To: NT Developers Interest List
> Subject: [ntdev] RIT (Raw Input Thread)
>
>
> Dear All,
> I couldn’t find any documentation for this RIT on the internet or
> elsewhere. Can anyone tell me the functionality of RIT. Is it true
> that RIT is the one which sends IRP_MJ_READ requests to drivers like
> mouclass and kbdclass…
>
> cheers
> Sesha.
>
**********************************************************************
>
> 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 %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@rdsor.ro To
unsubscribe send a blank email to %%email.unsub%%
—
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@rdsor.ro
To unsubscribe send a blank email to %%email.unsub%%</no.of.classobjects>
Hi D,
I was curious to know if it works that way :-). That was just one
more question from me acutally 
cheers
Sesha.
From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
Reply To: NT Developers Interest List
Sent: Tuesday, June 18, 2002 5:34 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
I am not trying to be obtuse, but basing a driver on how the RIT
operates is a recipe for disaster and does not port from release to
release. The algorithm for which the RIT reads from input devices
changes from release to release. Currently the basic algorithm uses a
mizture ZwReadFile, APCs, and a thread (hence the RIT ).
What is of concern for input drivers is that reads come down fast and
quick and that they are completed as soon as data is available.
D
-----Original Message-----
From: Dan Partelly [mailto:xxxxx@rdsor.ro]
Sent: Tuesday, June 18, 2002 5:09 PM
To: NT Developers Interest List
Subject: [ntdev] RE: RIT (Raw Input Thread)
This is the perfect answer. You have more in this serie ? How much do I
need to know, or Im allowed to know ?
Best regards, Dan
----- Original Message -----
From: “Doron Holan”
> To: “NT Developers Interest List”
> Sent: Sunday, June 16, 2002 8:49 PM
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
>
> Not exactly :). All you need to know about the RIT is that it sends
> down read requests as fast and as often as possible so that it can to
> minimize latency for input.
>
> d
>
> -----Original Message-----
> From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> Sent: Friday, June 14, 2002 11:00 PM
> To: NT Developers Interest List
> Subject: [ntdev] RE: RIT (Raw Input Thread)
>
> Hi D,
> Then i can assume the code of RIT to be like this :
>
> no.of class objects = no.of kbdclass objects +
> no. of mouclass objects
>
> RITEntry()
> {
> for(i=0;i<no.of.classobjects>> {
> 1. Allocate a Irp and fill the makor function as Read
> 2. Register a Completion routine
> 3. Send Irp to class object i
> }
> }
>
> RITCompletionRoutine(…)
> {
> 1. Do processing for kbd/mou data obtained , ie, put it on the
> global
>
> input message queue
> 2. Allocate or Reuse Irp
> 3. Register completion routine
> 4. pass Irp to the class object
> }
>
> Are my assumptions true???
>
> cheers
> Sesha.
> > ----------
> > From: Doron Holan[SMTP:xxxxx@windows.microsoft.com]
> > Reply To: NT Developers Interest List
> > Sent: Friday, June 14, 2002 9:27 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: RIT (Raw Input Thread)
> >
> > Yes, the raw input thread is the one that sends the reads for to
> > mouclass and kbdclass for keyboard and mouse input. If you want to
> add,
> > remove, or alter input data check out kbfiltr and moufiltr in the DDK.
>
> > It documents how do that with the appropriate interfaces. If you
> really
> > want to know how the RIT reads the data from the class drivers, both
> > mouclass and kbdclass are in the DDK as well.
> >
> > d
> >
> > -----Original Message-----
> > From: Seshagiri_Babu [mailto:xxxxx@Bla.Satyam.com]
> > Sent: Friday, June 14, 2002 5:59 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RIT (Raw Input Thread)
> >
> >
> > Dear All,
> > I couldn’t find any documentation for this RIT on the internet or
> > elsewhere. Can anyone tell me the functionality of RIT. Is it true
> > that RIT is the one which sends IRP_MJ_READ requests to drivers like
> > mouclass and kbdclass…
> >
> > cheers
> > Sesha.
> >
> **********************************************************************
> >
> > 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 %%email.unsub%%
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro To
> unsubscribe send a blank email to %%email.unsub%%
>
>
>
> —
> 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.
</no.of.classobjects>