From: "Tom Moore" <tom@tomstroubleshooting.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: looking for braille n speak chord
Date: Mon, 1 Oct 2007 21:42:05 -0400 [thread overview]
Message-ID: <001001c80495$7047efe0$c500000a@user7600ea7043> (raw)
In-Reply-To: <004801c8048e$75211a70$e6ba6441@tdsportable>
Maybe you should be a little more specific on the model of bns you have.
There are two different types of cables depending on what model you have.
Tom
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Littlefield, Tyler
Sent: Monday, October 01, 2007 8:52 PM
To: Speakup is a screen review system for Linux.
Subject: looking for braille n speak chord
Hello list,
Muy teacher very kindly gave me a BNS to use, and I'd like to use it as a
synth.
Anyone have the cable, that runs from the bns to the back of the comp?
I'm also probably going to be in the market for a bns in the future, as I
have to give this one back soon.
Thanks,
Tyler Littlefield.
Vertigo head coder
"My programs don't have bugs, just randomly added features."
msn: compgeek134@hotmail.com
email: compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.35/1040 - Release Date: 9/30/2007
9:01 PM
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.35/1040 - Release Date: 9/30/2007
9:01 PM
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Tom Moore [this message]
` Littlefield, Tyler
` Leonard Salinas
` Gregory Nowak
` Nick Stockton
` 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='001001c80495$7047efe0$c500000a@user7600ea7043' \
--to=tom@tomstroubleshooting.com \
--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).