Alexandre Julliard julliard@winehq.org wrote:
I assume it's a real hardware and not a VM? Is this with a real COM port, or USB-serial cable? If the latter one what driver is it using?
Looking at the failure messages above once again, I can say that WriteFile failure is definitely not caused by this patch. Does running the test several times cause the same failures? In any case it would be interesting to see the +comm log with "ntdll: Add a trace for transmitter's buffer empty flag." applied.
The WriteFile error is a timing thing, it doesn't always happen (and that test is clearly broken, ticks can be incremented at any point). The other errors always happen. It's a real COM port.
Could you please generate a log with additional trace for the empty flag?