Re: setevent problem
- From: "Bruce Eitman \(eMVP\)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 May 2005 09:41:39 -0400
Use named events and create the event in each app.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"sabya" <sabya@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:64B8EA6E-7302-4162-B93B-08420E8A20BE@xxxxxxxxxxxxxxxx
> we have got 3 instances.
> one driver and two applications.
> ok
> setevent() is in the driver only.
>
> now there r two cases which have to be looked for ......
>
> 1. if am passing the address of setevent() and waiting for that event
> (waitforsingleobject)
> in one single application or the same application. it is working fine . no
> problem.....
>
> the trouble comes in the 2nd case......
> 2. passing the address of event and waiting for that event
> (waitforsinglrobject)
> in different thread and then seeting this event in driver in ISR. event is
> not trigerred .....
> in the first point the event setting is happening in normal driver
function
> not in ISR
>
> what can be the problem. .....??????
>
> hope to get a reply soon...
>
> thnaks in advance
>
.
- References:
- setevent problem
- From: sabya
- setevent problem
- Prev by Date: Re: Maybe a Bug in wince500, please help to handle it.
- Next by Date: Re: not able to generate event from the driver
- Previous by thread: Re: setevent problem
- Next by thread: DEBUGMSG and FFUART enabled at the same time
- Index(es):
Relevant Pages
|
|
