From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Getting Speakup to work with Decktalk.
Date: Tue, 12 Mar 2002 11:48:53 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0203121145420.2688-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0203111803390.3991-100000@drizzle.com>
Hi, the one you will want is dectlk.
They will have to append a line to lilo.conf that looks like this:
append="hdc=ide-scsi speakup_synth=dectlk"
That will load the dectalk express. Speakup should just pickup the dectalk
on it's own.
To be ssafe hook your dectalk to com 1 or /dev/ttyS0
On Mon, 11 Mar 2002, Anna Schneider wrote:
>
> Okay, so the Pogo Linux people will install Speakup for me. *yay* They
> don't need my Decktalk to do this right if mine is an external and if they
> have the correct synthesizer code
>
> So my next question is, is the Decktalk Epress only the internal one? My
> is an external, but the tape about it says Decktalk Express and the
> express and the external have different code right?
>
> They will need to define the ports and then pick one to be the Decktalk's,
> corrrect?
>
> And they will need todo the speaku_synth=(synth code) right, and the two
> synth codes I've seen that might be the ones are dectlk and decext but I'm
> not sure which I use.
>
> Um, have I got everything here? I just need to know the right code and I
> think I understand what to tell them? But I may have missed something, my
> brain is quite disorganized at the moment.
>
> Uh, I know a couple people have said that if the Pogo Linux technitians
> have questions, they can feel free to ask. If any of you read this and
> answer and wouldn't mind me passing along your e-mail addresses, I would
> apprecaite that too.
>
> And I really hope this made some sort of sense. It is not at all in
> order.
>
> Anna
>
>
> _______________________________________________
> 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: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16iFnS-00080f-00@speech.braille.uwo.ca>
` help with a new Modem Adam Myrow
` Gregory Nowak
` Kirk Wood
` PCI interrupts and how they work Kerry Hoath
` Getting Speakup to work with Decktalk Anna Schneider
` Thomas D. Ward [this message]
` Janina Sajka
` Ameer Armaly
[not found] ` <Pine.LNX.4.44.0203121152190.3666-200000@toccata.grg.afb.ne t>
` Ed Barnes
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=Pine.LNX.4.33.0203121145420.2688-100000@localhost.localdomain \
--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).