From: "Zachary Kline" <klinez@onid.orst.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup and hald conflict in Slackware 12.2
Date: Tue, 16 Dec 2008 09:27:45 -0800 [thread overview]
Message-ID: <E67CC7C05D32473881EF9CDB96FC9527@ZKDESKTOP> (raw)
In-Reply-To: <20081216163804.GA20869@gmx.net>
Hi Alex,
Yes, this is with Virtualbox 2.0.6. If I may ask, how are you trying to
get it to use a serial port? vboxmanage is currently broken in that regard.
I used the GUI settings pages to configure mine. It's a little difficult:
the QT accessibility library is somewhat lacking. Nevertheless, I got it
working.
Essentially, you have to go into the VM settings dialogue and use the
tab control to get over to the serial ports section. It starts off with a
checkbox to decide whether to activate the ports.
Actually, this part is quite doable with vboxmanage. If you prefer
that, you want a command something like:
vboxmanage modifyvm "Vmname" -uart1 0x3f8 4.
The only part that requires the GUI is assigning the port to a physical
device. Go into that settings panel as above mentioned and you'll
eventually find that serial tab. The checkbox and port number are already
set, so tab over until you find a series of what are essentially radio
buttons. There's one about connecting to a pipe, which you'll recognize
because once you select that there's another checkbox which becomes active
asking if you want Virtualbox to create the pipe itself. At any rate, you
want the other radio button: there's only a box asking for "Port Path" with
that one. Just put in the device name, e.g. COM3 in my case, and you should
be set.
Hope this helps.
Best,
Zack.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Igor Gueths
` Gregory Nowak
` Michael Whapples
` Adam Myrow
` Adam Myrow
` Gregory Nowak
` Zachary Kline
` Gregory Nowak
` Zachary Kline
` Garrett Klein
` Gregory Nowak
` Alex Snow
` Zachary Kline
` Alex Snow
` Zachary Kline [this message]
` Alex Snow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E67CC7C05D32473881EF9CDB96FC9527@ZKDESKTOP \
--to=klinez@onid.orst.edu \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).