🚀 go-pugleaf

>>Non-overlapped I/O doesn't work in WinXP.

I should have added the phrase 'in my serial port component'.

> What makes you think that?

Because I tried it before I started messing around with overlapped I/O. When
I started out, with my applications running on Win98 exclusively, I used
non-overlapped I/O and it worked like a charm.

Once we started using WinXP, the application locked up in the status thread
(the WaitCommEvent() to be exact) and wouldn't continue unless something was
received on the COM port.

Some applications rely on the OnDataAvailable event, which is triggered by
the status thread in response to EV_RXCHAR. As far as I know, there is no
other way to get this working than with overlapped I/O (except polling the
serial port, which is not an option for me).

Whether I use overlapped I/O or not is not the issue. What I need advice
about is which errors I need to handle, and how to handle them. Do I need to
call ClearCommError() before/after the call to ReadFile() and WriteFile() to
handle errors? Or is there another way to detect errors in the status thread
and handle them there? WaitCommEvent() doesn't notify me of errors like
CE_RXOVER or CE_TXFULL, does it?

Thanks for your help sofar...

Martin