>>First, is 0x60 really the open handle to the comm device ? >>If that's the case, then you should try to find out why this >>*system error message* happens (add further debug traces to wine to find >>out >>what request exactly is failing and why etc. etc.). >Why go to that trouble? It obviously happens because no comm data is >immediately available for reading, and nonblocking overlapped I/O is used. >Have you never heard about nonblocking I/O? Hmm ok, but what can be donne about this? Is there an easy way out? The1trex -- Philosophers have tried to interpret the world in different ways; the important thing is to change it. - Karl Marx _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
