From: "Glenn at home" <GlennErvin@cableone.net>
To: <jaffar@jeffstudio.net>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: Strange garbles from dectlk
Date: Sun, 12 Jun 2005 10:49:59 -0500 [thread overview]
Message-ID: <053001c56f66$63b43930$6a00a8c0@desktop> (raw)
In-Reply-To: <000601c56f65$54c2f4d0$2343d4da@jaffar57b5aa42>
What happens when you send text directly to tty0, such as directing the ls
command to the port?
There must be an equivalent to the msDOS command:
dir>com1
would it be?
ls tty0
Glenn
----- Original Message -----
From: <jaffar@jeffstudio.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 12, 2005 10:42 AM
Subject: Strange garbles from dectlk
Hi All. My struggles with installing fedora still continues. After I type
in the command text speakup_synth=dectlk, It doesn't speak but goes straight
to the choice of whether I should skip checking my disk or proceed with the
installation. When I proceed, My nephew telles me that the screen shows
something like the Anaconda installer is active. It is at this point that
Dectalk garbles something like c cerdilla, atleast 20 times in succession,
then stops altogether. Incidentally, I did do a check on the disk, and
Anaconda says that my disk passed the check test. My conclusion is that My
dectalk is trying to respond, but that it is not able to connect with
speakup. I wonder if there is anything else I need to do? Any help will be
greatly appreciated. I have already disabled the non-existent tty2 from my
bios so that I have tty0 left. Cheers!
_______________________________________________
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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
jaffar
` Glenn at home [this message]
` Arthur Pirika
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='053001c56f66$63b43930$6a00a8c0@desktop' \
--to=glennervin@cableone.net \
--cc=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).