From: Kenny Hitt <kennyhitt@knology.net>
To: speakup@braille.uwo.ca
Subject: Re: reinit dectalk driver
Date: Thu, 13 Mar 2003 07:24:30 -0600 [thread overview]
Message-ID: <20030313132430.GC16552@potpal> (raw)
In-Reply-To: <Pine.LNX.4.44.0303122114180.13172-100000@igueths>
Hi. When you plug the deqtalk back into the computer you need to get
speakup to reset the synth. After you plug the synth back up but before
you turn it on you need to press several speakup review keys and wait a
minute. Pressing the review keys makes sure speakup knows there is no
synth.
After you make sure speakup knows the synth is gone, you can turn it on
and press insert-enter. You should hear speakup re-initilize the synth.
Your rate pitch voice and tone will be back to the default when speakup
first booted, so you will need to reset them.
Hope this helps.
Kenny
On Wed, Mar 12, 2003 at 09:19:22PM -0500, Igor Gueths wrote:
> Hi all. Numerous times I have had to switch my Dectalk to a different
> machine. Then once I replug it back in, everything seems to speak ok.
> However, when I do an ls, I get extremely long pauses between
> filename/extention. For example, instead of getting file.foo, I would get
> something like: file........foo. Does this have to do with the serial line
> to the Dectalk not handshaking properly? And the only way I can think to
> solve this problem is to reboot the machine. Does anyone have any other
> sollutions? Thanks!
>
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
>
>
> _______________________________________________
> 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: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Travis Siegel
` Luke Davis
` Kirk Reiser
` Kenny Hitt [this message]
igueths
` Kenny Hitt
igueths
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=20030313132430.GC16552@potpal \
--to=kennyhitt@knology.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).