From: Duke Yasuda [dukey@calculex.com] Sent: Monday, June 28, 1999 4:39 PM To: 'NTDEV (Post)' Subject: RE: [ntdev] QueueUserApc Hi Heldai, Here it is: The QueueUserApc function adds a user-mode asynchronous procedure call (APC) object to the APC queue of the specified thread. DWORD QueueUserApc( PAPCFUNC pfnAPC, // pointer to APC function HANDLE hThread, // handle to the thread DWORD dwData // argument for the APC function ); Parameters pfnAPC Pointer to the application-supplied APC function to be called when the specified thread performs an alertable wait operation. hThread Specifies the handle to the thread. The handle must have THREAD_SET_CONTEXT access. dwData Specifies a single DWORD argument that is passed to the APC function pointed to by the pfnAPC parameter. Return Values If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. There are no error values defined for this function that can be retrieved by calling GetLastError. Remarks The APC support provided in the operating system allows an application to queue an APC object to a thread. Each thread has its own APC queue. The queuing of an APC is a request for the thread to call the APC function. The operating system issues a software interrupt to direct the thread to call the APC function. When a user-mode APC is queued, the thread is not directed to call the APC function unless it is in an alertable state. After the thread is in an alertable state, the thread handles all pending APCs in first in, first out (FIFO) order, and the wait operation returns WAIT_IO_COMPLETION. A thread enters an alertable state by using SleepEx, SignalObjectAndWait, WaitForSingleObjectEx, WaitForMultipleObjectsEx, or MsgWaitForMultipleObjectsEx to perform an alertable wait operation. If an application queues an APC before the thread begins running, the thread begins by calling the APC function. After the thread calls an APC function, it calls the APC functions for all APCs in its APC queue. When the thread is terminated using the ExitThread or TerminateThread function, the APCs in its APC queue are lost. The APC functions are not called. Note that the ReadFileEx, SetWaitableTimer, and WriteFileEx functions are implemented using an APC as the completion notification callback mechanism. QuickInfo Windows NT: Requires version 4.0 or later. Windows 95/98: Requires Windows 95 or later. Windows CE: Unsupported. Header: Declared in winbase.h. Import Library: Use kernel32.lib. See Also Synchronization Overview, Synchronization Functions, MsgWaitForMultipleObjectsEx, ReadFileEx, SetWaitableTimer, SleepEx, WaitForMultipleObjectsEx, WaitForSingleObjectEx, WriteFileEx Built on: Monday, November 16, 1998 ---------- From: Heldai Lemos Ferreira[SMTP:heldai@seil.com.br] Sent: Monday, June 28, 1999 11:35 AM To: ntdev@atria.com Subject: [ntdev] QueueUserApc Hi all, Someone know the QueueUserApc prototipe ? Thanks in advance Heldai Lemos Ferreira heldai@seil.com.br - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [ To unsubscribe, send email to ntdev-request@atria.com with body UNSUBSCRIBE (the subject is ignored). ] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [ To unsubscribe, send email to ntdev-request@atria.com with body UNSUBSCRIBE (the subject is ignored). ]