🚀 go-pugleaf

Well, I am using overlapped I/O.  The problem is that I don't want my code
to lock up.
If the other unit does not respond, I want the read function to quit, but
what is a good time to quit?
How about if I dishout an application that works well with this unit, under
the environment I am in, but
when the user gets it, the unit or my application seems that it is lockout
(because he/she has a pentium 100, operating on Win95)?  <---- Just an
example.

I was using the WaitForSingleObject(), but it did not make a difference,
where I enabled it or not?

Anyways, lets see if I can display a snippet from my code.

Thank you,
Neil P.

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:427fce92$1@newsgroups.borland.com...
>
> "Neil P." <nporve01@hotmail.com> wrote in message
> news:427fca8b$1@newsgroups.borland.com...
>
> > I use ClearCommError(hComm, &dwErrorMask, & Comstat)
> >
> > to view what is coming in the cbInQue,
>
> When do you call it, though?  Are you checking for errors?  Please show a
> code snippet of what you are actually doing.
>
> Rather than using ClearCommError(), why not just read immediately after
> writing?  You are already expecting a byte to be written, so just read
> immediately and let the reading block until the byte actually arrives.  It
> also looks like you are using overlapped I/O, which played directly in my
> suggestion as well, since ReadFile() will return immediately and then you
> can use WaitForSingleObject() to wait for the reading to signal the event
> object that you place in your OVERLAPPED structure.
>
>
> Gambit
>
>