Fist of all -- great product! I really appreciate being to connect serial ports to pipes to get 2-way traffic instead of just output to a file! Would I be correct in thinking that if I have to VM's that point to the same pipe, with one as server and one as client, then they would effectivly be connective via serial port. In this fashion, for example, hyperterminals on each end would be connected and could type back and forth to each other. If this is so, what is done with control lines (flow control) and baud rate? What is the operating difference between being the client and being the server (from a serial standpoint)? I understand named pipes to be one-way. How does a single name become a two-way pipe? I want to access the VM serial ports from MacOS and need to understand how to connect to the pipe from my own programs (that emulate external serial equipment fro VM testing). Finally - if possible, it would be great if an option for serial port connection could include the standard MacOS IO toolkit. That way any Mac serial port could be captured by the VM. This could probably be done separately via the pipe mechanism, but built-in would be a great benefit to the many existing Mac products (Keyspan, etc.) Thanks! Matt
