2009/3/30 Jeff Diewald :

I have a boost::asio::serial_port object. What is the specific Windows type returned by native()?

See: /usr/include/boost/asio/detail/win_iocp_serial_port_service.hpp On Windows asio talks to the serial port by opening the special file COM1. The native() call returns a HANDLE to that special file. Chris -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3

I'm having trouble with my serial communication across the serial port, and want to get more diagnostic information by going to the native level. The serial port hangs occasionally on a synchronous read_some call, and I haven't been able to figure out why. Ideally, I'd like to build a timeout into the synchronous call.

AFAIK read_some() should only block if there is no data to read at all. You could check for that with: boost::asio::socket_base::bytes_readable command(true); socket.io_control(command); std::size_t bytes_readable = command.get(); Or you implement your own read() function with async_read() and deadline_timer, like here: http://lists.boost.org/Archives/boost/2007/04/120339.php Chris -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3