Hi Ian, Andreas, there are still some issues with comm support under wine, as you've found out... i've had it working with the public domain terminal program KoalaTerm and my modem. ReadFile and WriteFile timeouts sortof work... not perfectly though. There are some special cases for the timeout values in the COMMTIMEOUTS structure. The palm program may rely on these... WaitCommEvent only works for EV_RXCHAR. Anything that waits using EV_TXEMPTY will loop infinitely... presumably because windows only triggers once when the TX buffer becomes empty, rather than anytime it is empty. Any other wait flags are ignored... so programs relying on see changing CTS, RI or DSR with WaitCommEvent won't work... but that doesn't seem to be the case for your Palm. Thirdly, perhaps it is using ClearCommError to see how many bytes have been sent/received, which may not work very well. Try doing the trace again with -debugmsg +comm,+file and post the results. i'll have a look... Sometime putting a TRACE into ReadFile/WriteFile so you can see what data is being read and written is useful. Mike > I grabbed a CVS tree earlier today and tried to set this up with my Palm > Vx. Results were less encouraging: ------------------------------------------ mailto:[EMAIL PROTECTED] ph +61 2 9427 2196 __________________________________________________________________ Get your own free web email at http://www.looksmart.com.au LookSmart Australia
