A month or so ago I posted the following, I was wondering if anyone has taken a look at the "disconnect then cannot reconnect" problem in the port. There is an update to the bug I referenced here that will help the situation, but it won't do any good if the FreeBSD port still has the "disconnect then cannot reconnect" problem with the serial ports.
Ted On 4/22/2010 4:04 PM, Ted Mittelstaedt wrote:
Hi All, Host is FreeBSD 8.0-CURRENT Ports are from CVS done 4/17 VirtualBox 3.1.6 OSE with FreeBSD setup as the host OS Hardware is dual Xeon 2.0Mhz Client OS is Windows XP SP3 XP runs great except for the serial ports. I have an app that calls pagers and dials a USR 56k Sportster I can cu -l /dev/cuau0 -s 57600 to the modem and send AT commands to it just fine. When I first tried accessing the serial port from the XP session it failed completely. Then I found a patch on http://www.virtualbox.org/ticket/1548 and applied this and now I can talk to the modem from the XP session. However there is a problem with opening and closing the serial port. I can run VirtualBox, boot the XP session, go into Hyperterminal, open the assigned com port, send at commands to the modem, get responses, dial into my remote, everything works fine. But then once I close the session and disconnect from the COM port from Hyperterminal, when I try to reopen the port I get nothing. If I reboot the XP session within the virtual machine I still get nothing. I have to close VirtualBox down, then restart it before I can access the serial port again. Any suggestions? Ted
_______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
