🚀 go-pugleaf

I know that page has the title of Overlapped IO, but ive also seen other pages that sugest it occours also with non-overlapped IO.

Either way, im still having the problem they describe.
WriteFile should always return... its as simple as that.
Im my case its not, so it cant be anything but a Windows bug.

What a pain...
Any idea where else would be a good place to ask this question?

"Ed Mulroy [TeamB]" <ed@mulroyREMOVETHESECHARS.org> wrote:
>That page addresses overlapped I/O but you're not using overlapped (although the problem may persist).
>
>My experience with LCD's is that they can't take fast data very well.  Maybe your's is different.
>
>In any case, it sounds as if the remedies mentioned in that page might be
>worth trying.  Also, a big comm buffer or a flush of the comm buffer prior
>to the next send might be something to try.
>
>I hope you get past it (now if you could only solve my it-nukes-XP problem with the USB port! <g>).
>
>Thanks for the link.  I'm bookmarking that one.
>
>..  Ed
>
>> MWP wrote in message
>> news:3ec26741$1@newsgroups.borland.com...
>>
>> 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.
>
>