From: "Brent Harding" <bharding@doorpi.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: VmWare
Date: Wed, 18 Apr 2007 08:56:48 -0500 [thread overview]
Message-ID: <004001c781c1$689adfc0$224a5c46@brent827e59cc1> (raw)
In-Reply-To: <4625baba.6e525a32.027e.41b5@mx.google.com>
I tried this with VMWare Player. I was going to load up the Ubuntu 6.10 iso
and install it on a virtual machine this way. I used easyvmx.com to generate
the proper files and chose the ES whatever sound card it would use by
default. Everything seemed to go OK until Orca loaded, and I got odd
static-like noises instead of speech. I think sound is definitely broken
some how in VMWare Player. I might uninstall that and try server instead.
----- Original Message -----
From: "Jeremy" <l84ad8r@gmail.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, April 18, 2007 2:27 AM
Subject: Re: VmWare
> Late reply to one of the earlier posts on this subject. I had asked a
> question about how to get a installation of linux running in a vm,
> and, I have to say that I did get it working. It Turned out to be
> very easy, but, I was wondering about sound support in the vm as I
> was just using speakup through my serial port. It was kind of cool
> when I got it working as I was on skype on the windows host and it
> never gave me any trouble, but, I am guessing that getting some sort
> of software synth working would not work unless I had another
> soundcard to rout it through? I am not even sure if I can find
> drivers for my soundcard that is built into this laptop, but, that is
> a question for another time I suppose. If someone can tell me more
> about how this kind of thing works, that would be wonderful. I
> noticed that someone did get software speech going with a vm, so,
> figured I would ask.
> Thanks bunches.
>
>
> _______________________________________________
> 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: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
VmWare Zachary Kline
` VmWare Gregory Nowak
` VmWare Alex Snow
` VmWare Zachary Kline
` VmWare Gregory Nowak
` VmWare Tyler Spivey
` VmWare Zachary Kline
` VmWare Brent Harding
` VmWare Zachary Kline
` VmWare Alex Snow
` VmWare Doug Smith
` VmWare Christopher Moore
` VmWare Alex Snow
` VmWare Doug Smith
` VmWare Jeremy
` VmWare Alex Snow
` Brent Harding [this message]
` VmWare Ricky Enger
` VmWare Zachary Kline
` VmWare Brent Harding
` VmWare Alex Snow
` VmWare Gregory Nowak
` Re[2]: VmWare Farhan
` VmWare Alex Snow
` VmWare Jeremy
` VmWare Brent Harding
-- strict thread matches above, loose matches on Subject: below --
VmWare Jeremy
vmware Dawes, Stephen
vmware Sergey Fleytin
vmware Scott Howell
` vmware Geoff Shang
` vmware Scott Howell
` vmware Kerry Hoath
` vmware scott howell
` vmware Bart Bunting
` vmware John Covici
` vmware Kris Van Hees
` vmware cpt.kirk
` vmware Scott Howell
` vmware cpt.kirk
` vmware Count Zero
` vmware Victor Tsaran
` vmware Scott Howell
` vmware Bart Bunting
` vmware John Covici
` vmware scott howell
` vmware John Covici
` vmware scott howell
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='004001c781c1$689adfc0$224a5c46@brent827e59cc1' \
--to=bharding@doorpi.net \
--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).