From: <jaffar@jeffstudio.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Speakup or dectalk, and the answer?
Date: Sun, 22 May 2005 22:33:49 +0800 [thread overview]
Message-ID: <001201c55edb$449c4d30$8842d4da@jaffardesktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Hi Friends. So I am back with the same problem. With the help of my sighted nephew, I can confirm the installation of Fedora takes place when I boot from Disk 1 of the Fedora Distro. Problem is, speakup or dectalk won't communicate that info to me. My nephew saw two options onscreen when the install starts, press enter for the graphical installation or type linux for a textual installation. I tried text speakup_synth=dectlk, but with no success. Dectalk or speakup, i don't know which, just shuts up on me. If the worse came to the worse, if I were to get my nephew's assistance during the install process, how then can i get speakup to work after the install stage? Also, and I don't know if this would solve the problem, the com port 1 and the non-existent com port 3 is sharing the same IRq allocation. Could it be that speakup, because of this shared resource allocation cannot determine exactly on which port my dectalk express is connected too? All solutions to this on running puzzle is very much appreciated. Cheers!
[-- Attachment #2: "AVG certification" --]
[-- Type: text/plain, Size: 142 bytes --]
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 5/20/2005
next reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
jaffar [this message]
` Glenn at home
` Gregory Nowak
` David Bruzos
` Janina Sajka
` Chris Hofstader
` Charles Hallenbeck
` jaffar
` Gregory Nowak
` Janina Sajka
` Jim Grimsby
` Janina Sajka
` Sean McMahon
` Sean McMahon
` 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='001201c55edb$449c4d30$8842d4da@jaffardesktop' \
--to=jaffar@jeffstudio.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).