public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Jayson Smith" <ratguy@bellsouth.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: dectalk question
Date: Tue, 15 Jun 2004 18:47:28 -0400	[thread overview]
Message-ID: <000d01c4532a$bc6b58a0$6500a8c0@h2c8f0> (raw)
In-Reply-To: <20040615205045.GC3373@gmx.net>

The Dectalk Express is set up to receive data sent at 9600 baud, 8 data
bits, 1 stop bit, and no parity.  I'd assume that's what Speakup would
probably expect.  At any rate, that would be a good starting point.
Jayson.

----- Original Message -----
From: "Alex Snow" <alex_snow@gmx.net>
To: "Speakup list" <speakup@braille.uwo.ca>
Sent: Tuesday, June 15, 2004 4:50 PM
Subject: dectalk question


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all. I finally got into the setup interface of my dtc01 to see if I
> can get it to run with speakup. What com parameters does speakup expect
> from the dectalk? I'm asuming the parameters for the "host" are what I
> should change. like the default baud is 1200. is this what speakup
> expects?
>
> - --
> Linux is addictive, I'm hooked!
> -- MaDsen Wikholm's .sig
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAz2El9XVrM3ri110RAi61AJ0QOS1trMCRWx4e/yEGNwue+UWH2gCbBMBJ
> xUMTZpoKoAMw27ktuyt5tiU=
> =CC91
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alex Snow
 ` Jayson Smith [this message]
   ` Alex Snow
 ` Debee Norling
   ` Alex Snow
     ` Debee Norling
 ` Gene Collins
  -- strict thread matches above, loose matches on Subject: below --
 Killing a module Victor Tsaran
 ` Dectalk question Anna Schneider
   ` Ameer Armaly
   ` Terry Klarich
   ` Thomas Ward
     ` Buddy Brannan
       ` Thomas Ward

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='000d01c4532a$bc6b58a0$6500a8c0@h2c8f0' \
    --to=ratguy@bellsouth.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).