From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup on an Echo
Date: Tue, 5 Jul 2005 13:31:12 -0500 [thread overview]
Message-ID: <000701c5818f$b8b0fb40$250110ac@chihuahual1> (raw)
In-Reply-To: <20050705162814.GA18599@lava-net.com>
Hi, It would be nice to hear the echo synthsizer. bye
My web page is at http://www.nickgawronski.com
----- Original Message -----
From: "Igor Gueths" <igueths@lava-net.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, July 05, 2005 11:28 AM
Subject: Speakup on an Echo
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi all. I recently got a hold of a recording that Garrett Klein did of
> his encounter with the PC version of an Echo. He managed to get it
> working with Speakup using the BNS driver. I'm not sure how interested
> people would be in this, however yesterday I uploaded
> speakup_on_an_echo2.mp3. That was the entire file. However,
> speakup_on_an_echo.mp3 is only a bit of the file since my connection
> dropped and I had to restart the upload process. I checked to see if
> speakup_on_an_echo2.mp3 had been moved to the goodies directory, however
> I didn't see it. Should I re-upload the whole file to /pub/incoming? I
> will say that the file right now is a little loud, however if there is
> substancial interest for the re-upload I'll try again to turn down the
> volume a bit.
> - --
> How many chunks could checkchunk check if checkchunck could check chunks?
> - -- Alan Cox
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
>
> iQIVAwUBQsq1Hqe2pgKIdGq4AQqUahAAiqxND8bzyK8HTpiH61rdRZgeMbCcqJ16
> fLL1UBlnZDJ4hxJS4WOp+R/CNVnU0MqgsRKVIdCaFMyvIwCUCxaml/7jSqGtd0rt
> tbzOzl0Y/cXTWPcBhtvci4wCxhorG/IFlscIWoXu4RLXL/G3EQA7xKD7xbNPJLaf
> xazhzbxp/IuOzzHPYJmPXH/Bru7qzEGYFPbEzCW26JjsPymeIdWDQ+nqCS2bXE9o
> CbSPuhnYHkSWfnzdJ/CiXZlOEsvC/CJkM/uRP/tt5px6BhtvXg4YIkXgtxS/7ech
> ADO3ph5B38Ywv5tAJHLloSvkI4633XOilAIjpD6snf2UQ/7BF5FKZNe3EzqzXGHQ
> bjCj2w2hl0fqC3F6Eh40t2hfWsizqPa08RdS8g5ZEyd+hrE226g8l8u7smMlmY82
> noodyWR5oAobQJ+PaqlcfAeFpvPeCHa91WimQzrv+Qv3ExnCwyKLwnnoa3/0W4D4
> mAOR5HRX/0dH/UYvZH5pU+TrLttCTzMHIuwgRk35llhS782XwB6FQMEvI5U+UKPq
> 3nIpy7nQUCQkP13aNgxE1l4ujeuzsTdCRyKjW0KDl3lYeljcfqLM2lckrJXHExPJ
> w+wYYXMwzrsfLCQBDcg7FXUj+NgIA6DcVZb294cNnUN5VtFrxswxMXwZ6WFTgJnk
> YDN5iXZYAmM=
> =rmb7
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> 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
Igor Gueths
` hank smith
` Jim Grimsby
` Nick Gawronski [this message]
` Garrett Klein
` Adam Myrow
` Gregory Nowak
` hank smith
` Jim Grimsby
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='000701c5818f$b8b0fb40$250110ac@chihuahual1' \
--to=nick@nickgawronski.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).