The PurgeComm function can discard all characters from the output or input buffer of a specified communications resource. It can also terminate pending read or write operations on the resource.
BOOL PurgeComm(
HANDLE hFile, |
// handle of communications resource |
DWORD dwFlags |
// action to perform |
); |
Value |
Meaning |
PURGE_TXABORT |
Terminates all outstanding write operations and returns immediately, even if the write operations have not been completed. |
PURGE_RXABORT |
Terminates all outstanding read operations and returns immediately, even if the read operations have not been completed. |
PURGE_TXCLEAR |
Clears the output buffer (if the device driver has one). |
PURGE_RXCLEAR |
Clears the input buffer (if the device driver has one). |
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
If a thread uses PurgeComm to flush an output buffer, the deleted characters are not transmitted. To empty the output buffer while ensuring that the contents are transmitted, call the FlushFileBuffers function (a synchronous operation). Note, however, that FlushFileBuffers is subject to flow control but not to write time-outs, and it will not return until all pending write operations have been transmitted.
file: /Techref/os/win/api/win32/func/src/f69_4.htm, 3KB, , updated: 2000/4/7 11:19, local time: 2024/11/24 06:47,
18.118.144.98:LOG IN
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://massmind.org/techref/os/win/api/win32/func/src/f69_4.htm"> PurgeComm</A> |
Did you find what you needed? |
Welcome to massmind.org! |
Welcome to massmind.org! |
.