Article View: borland.public.cppbuilder.nativeapi
Article #10263Re: Problem with WaitCommEvent in thread
From: Leo Havm�ller
Date: Tue, 11 May 2004 11:00
Date: Tue, 11 May 2004 11:00
11 lines
1198 bytes
1198 bytes
"Martin Nijhoff" <dont@mail.me> wrote in message news:40a092fd$1@newsgroups.borland.com... > I wrote a serial communications component, which uses non-overlapped I/O and > creates a second thread to monitor events like the reception of a character, > parity error, etc. Wont work. You must use overlapped I/O for this. Leo Havm�ller.
Technical Details
Message-ID:
<40a0b26b@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<40a092fd$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: 10cc67,4298e6c7d8d30497 X-Google-Attributes: gid10cc67,public From: "Leo Havm�ller" <leh@-nospam-rtx.dk> Newsgroups: borland.public.cppbuilder.nativeapi References: <40a092fd$1@newsgroups.borland.com> Subject: Re: Problem with WaitCommEvent in thread Date: Tue, 11 May 2004 13:00:59 +0200 Lines: 13 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 80.63.27.146 Message-ID: <40a0b26b@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1084273259 80.63.27.146 (11 May 2004 04:00:59 -0700) Path: arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail