From: Chris Norman <chris.norman4@ntlworld.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Accessible virtual machine: preferably debian
Date: Thu, 07 Feb 2008 08:09:11 +0000 [thread overview]
Message-ID: <1202371751.9863.9.camel@sparky> (raw)
In-Reply-To: <001e01c8695c$b88cebd0$80f210ac@cheryld3c31ebe>
On Thu, 2008-02-07 at 01:40 -0600, Cheryl Homiak wrote:
> I don't have a problem between vmware and macosx. There are menu buttons in
> vmware when I start the virtual machine, at least in windows, for
> connecting/disconnecting various drivers. I have one braillelite that I
> allow to connect when I access windows an another that stays disconnected so
> I can use the terminal. I should then be able to install espeak and/or
> brltty by the terminal. But I am still a little confused about how I access
> the dhcp database; do you mean one on the macos end?
I have my machines set up so they will use NAT, this means that my
physical machine has the address 192.168.0.130, and the virtual one has
192.168.128.129.
The problem I had for a while was that when looking for a list of
services, I saw a DHCP client, and a DHCP server, and I set the server
one to manual start, reckoning that if it was anything to do with
VMWare, then it would start when needed. I was wrong, something to keep
in mind, if you're as stupid as I am, and try and fix stuff before it's
even broken.
HTH.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Kerry Hoath
` Cheryl Homiak
` Kerry Hoath
` Chris Norman [this message]
` Cheryl Homiak
` Kerry Hoath
` Chris Norman
` ubuntu and speakup Frank Carmickle
` Luke Yelavich
` Chris Norman
` Accessible virtual machine: preferably debian Don Raikes
` Tyler Spivey
` Alex Snow
` Cheryl Homiak
` Gaijin
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=1202371751.9863.9.camel@sparky \
--to=chris.norman4@ntlworld.com \
--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).