From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: triple talk internal/external
Date: Wed, 22 Aug 2001 22:50:14 -0400 [thread overview]
Message-ID: <007f01c12b7e$56061f40$3590fea9@starbase> (raw)
In-Reply-To: <auto-000021043205@dc-mx07.cluster1.charter.net>
Hi, you shouldn't have any problems with the Double Talk LT.
As far as Linux Zip Speak is probably the way to go here.
Mandrake can be installed to a fat 32 partition, but takes lots of help from
someone sighted to get going with speech.
Although, Mandrake has a lot of nice features you don't see everywhere else,
but the accessability angle is a pain.
Zip Speak can be unzipped right onto the hard drive, edit a couple of files,
and run loadlin, and you should be well on your way to go.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Jim Ruby
` Saqib Shaikh
` Jim Ruby
` Buddy Brannan
` Janina Sajka
` Saqib Shaikh
` Jim Ruby
` Kirk Wood
` Amanda Lee
` Kirk Reiser
` Amanda Lee
[not found] ` <Pine.LNX.4.33.0108231901480.24151-100000@ns.shellworld.net >
` Charles Crawford
` Thomas D. Ward [this message]
Gregory Nowak
` Buddy Brannan
` Kirk Wood
` Gregory Nowak
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='007f01c12b7e$56061f40$3590fea9@starbase' \
--to=tward@bright.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).