“Roddy, Mark” wrote in message news:xxxxx@ntdev…
>
> No, it is not a bug. The fact that the event was created in ‘kernel mode’
is
> not relevant. What is important to the OS is that the event was created by
> process X, and when process X terminates, all open handles associated with
> all threads of process X are closed, including all the handles to your
event
> (unless some other application opens it before the creating process (X)
> terminates.)
>
> Spawn a worker thread and create the event using the system process. Do
this
> in IRP_MJ_CREATE if you so desire. The event created using the system
> process will persist as long as the system process does not close the
> associated handle.
>
Might you instead simply set OBJ_PERMANENT in the Attributes field? I’m not
certain, but I think this has the desired effect, no?
P
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Ack, I can’t eat and type at the same time.
What I meant to say was you could, but you would not be using the
documented ddk interfaces for creating named events in the kernel.
Haven’t we had this discussion before?
=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Viscarola
Sent: Wednesday, February 06, 2002 5:53 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Bug with NamedEvent in Windows2000 and WindowsXP ?
“Roddy, Mark” wrote in message
news:xxxxx@ntdev…
>
> No, it is not a bug. The fact that the event was created in ‘kernel
> mode’
is
> not relevant. What is important to the OS is that the event was
> created by process X, and when process X terminates, all open handles
> associated with all threads of process X are closed, including all the
> handles to your
event
> (unless some other application opens it before the creating process
> (X)
> terminates.)
>
> Spawn a worker thread and create the event using the system process.
> Do
this
> in IRP_MJ_CREATE if you so desire. The event created using the system
> process will persist as long as the system process does not close the
> associated handle.
>
Might you instead simply set OBJ_PERMANENT in the Attributes field? I’m
not certain, but I think this has the desired effect, no?
P
—
You are currently subscribed to ntdev as: xxxxx@hollistech.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com