🚀 go-pugleaf

The device at the other end is a LCD module which doesnt have any kind of software/hardware flow control.

Well ive found the problem... its a Windows bug:
http://www.alumni.caltech.edu/~dank/overlap.htm

Looks like it effects Windows XP as well.
What a pain.

Not sure how im going to get around it yet.

Any sugestions?

"Ed Mulroy [TeamB]" <ed@mulroyREMOVETHESECHARS.org> wrote:
>Check the device at the other end of the serial cable.  It has probably
>dropped a signal, possible one of CTS, DCD or DTR.
>
>If you changed to an asynchronous write then it would return after the call
>and you would have an opportunity to insert code to help determine the
>source of the problem.
>
>..  Ed
>
>> MWP wrote in message
>> news:3ec25f43$1@newsgroups.borland.com...
>>
>> Im am doing the following simple line that is running about 40
>> times a second: WriteFile(ComHandle, Block, Length,
>> &BytesWritten, NULL);
>>
>> ComHandle is pointing to a COM port opened at 19200.
>> Length is never more than 20 (verified).
>>
>> It will work for a random amount of time then, WriteFile gets
>> called but doesnt return... ever.
>>
>> Anyone know what the problem could be?
>
>