RE: Passing event notification from driver to application again

NTDEV
1

There can be many reasons; hard to say without seeing the code. No, don’t
post it. You can better find it youself. My hint is to use traces. Use
DbgPrint in kernel and OutputDebugString in user mode and report every
important event as attempt to set event, return from this call, return from
wait with result etc. Use SoftICE or System Internal DebugView or any other
utility which is able to display both kernel and user mode traces and you’ll
see soon where is a problem (my preference is DebugView because of its
colored highligh filters).

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

From: xxxxx@nexland.com[SMTP:xxxxx@nexland.com]
Reply To: xxxxx@lists.osr.com
Sent: Wednesday, September 04, 2002 9:11 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] Passing event notification from driver to
application again

Hello everybody,

I was sending 64 events handles to the driver from application. The events
were referenced successfully in the driver. To notify the application for
each incoming packet, I used a circular buffer to hold the events, when
ever
a packet comes in, the driver clears and set a event, the counter will do
a
mod 64 increment.

On the application side, I was using

WaitForMultipleObjectsEx(MAX_READS, hEvents, FALSE, INFINITE, FALSE)

here MAX_READS is 64, hEvents is HANDLE hEvents[64].

Seems I got substantially more notifications than the actual ones. (maybe
64
times). I don’t understand why, can anyone give me some hints?

Thanks a lot!
Yuanhui

You are currently subscribed to ntdev as: michal.vodicka@st.com
To unsubscribe send a blank email to %%email.unsub%%