![]() ![]() ![]() My setup uses com0com to create a pair of virtual serial ports, where the RX/TX of the first port is connected to TX/RX of the second (same as a hardware echo). I'm experiencing similar flow control problems on Windows 7 圆4 (v5.2.0) This problem has been present in at least the past 8-10 releases, and I suspect before that.Įdit: Issue described in a closed ticket: #5135 There's still quite a bit of use left for serial device I/O, so I would expect this to work 100% in a product of VirtualBox's maturity. So this is definitely related to the "bridge" between the COM port emulator running on the Host side of things. In that case, NetSerial is emulating a COM port and using Windows XP Guest Network to reach the Internet. In almost exactly the same scenario, if I "move" NetSerial so that it runs inside the guest (Windows XP), there is no problem whatsoever. Flow control issues, etc.Įvery application that I have tested with is requesting flow control to be CTS/RTS (hardware) and not XON/XOFF. When booting a FreeDOS Guest in this setup, I get similar results to the above. On the Guest, however, nothing is received. I can also see data being sent FROM NetSerial into the COM port. Using it's "monitor", I can see data being received from the Client terminal emulator. ![]() Opening a Linux terminal emulator (any will do) using /dev/ttyS0, data IS being sent to NetSerial on the Windows Host. When booting a Linux Guest in this setup, doing "dmesg |grep tty" does reveal that Linux has detected a 16550A UART on COM1, which is good thus far. But somwhere between the Guest and the Host, data is lost or delayed indefinitely. He sets the correct flags for flow control, etc. I've been talking to the author of NetSerial and have been testing with beta versions of NetSerial as well. But there seems to be flow control issues between the Guest and the Host. When Guest OS is launched, the results vary. In VB Guest Config, I set up the serial port as needed. NetSerial will behave as a COM port and as a "modem emulator" to allow "ATDTfoo.bar" to establish a Telnet session to foo.bar. Using NetSerial ( ) to emulate a COM port. Guest can be "anything", but I've tested with FreeDOS, Ubuntu Linux 16/17, and Windows XP. ![]() Host running Windows 10 Pro (64-bit) on computer with no physical COM ports (Lenovo T470p laptop). But some others I've been in touch with seem to have this with other configurations too. I've only personally seen this in a Windows 10 Pro (64-bit) host environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |