From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: external synthrecommendation?
Date: Mon, 30 Oct 2006 10:44:33 -0600 [thread overview]
Message-ID: <05c401c6fc42$ad3d61c0$4ba65c90@vv507j> (raw)
In-Reply-To: <Pine.BSF.4.64.0610280211220.80777@server2.shellworld.net>
I bought an external doubletalk a year ago in April. So it's only a year and
a half old and it appears to hav died. I first started having trouble with
it when it was still less than a year old. I kind of wish I had sent it back
when it first started acting up.
I have 2 questions:
1. Is my experience with the doubletalk LT typical? How long do they usually
last? For $350, I'd expect to get more than a year and a half out of it.
2. Any recommendations for an external synth? Obviously, I want to spend as
little as possible but I'll spend whatever I have to to get a good synth.
PS: The symptoms are as follows: I turn the doubletalk on, it says
"doubletalk ready". But it does not speak when used with a machine running
speakup. I have a tripletalk external synth at workso I know speakup is
working.
When I initialize the doubletalk, I often get kernel error messages. But I
don't think that's particularly meaningful. Probably the ltlk driver just
doesn't know how to handle it whenit detects a synth but the synth doesn't
respond properly.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
debian kernel upgrade Jude DaShiell
` John Heim [this message]
` external synthrecommendation? Kirk Reiser
` John Heim
` Kirk Reiser
` computer builder randy turner
[not found] ` <20061030180902.GA31718@cm.nu>
` external synthrecommendation? Gregory Nowak
` Steve Holmes
` Chuck Hallenbeck
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='05c401c6fc42$ad3d61c0$4ba65c90@vv507j' \
--to=jheim@math.wisc.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).