From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Bootdisk for Redhat 7.2 with Speakup1.0
Date: Sat, 1 Dec 2001 01:51:10 -0500 [thread overview]
Message-ID: <00dd01c17a34$8fc31760$0100a8c0@polaris> (raw)
In-Reply-To: <000d01c17994$b031a9d0$0100a8c0@cybertsar>
Hi, you must make absolutely sure when you are doing the install to choose
either the Speakup.map or speakup_lt.map.
If you choose something such as US.map You will not beable to use
speakup'snumpad during the install or after the install has finished.
----- Original Message -----
From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: "Speakup List" <speakup@speech.braille.uwo.ca>
Sent: Friday, November 30, 2001 5:07 AM
Subject: Bootdisk for Redhat 7.2 with Speakup1.0
> Hello, listers!
> I tried to update my existing Redhat 7.1 to 7.2 using the bootdisk, loaded
> with Speakup1.0. However, strange things started to happen. First of all,
> the numpad keys stopped working on the first or second step of the
> installation. Second, I had to once even reinitialize the update procedure
> because Speakup completely stopped speaking.
> I am using DoubleTalk LT and this is the first time I experienced such a
> behavior from Speakup.
> Any ideas?
> Best regards,
> Vic
>
>
>
> _______________________________________________
> 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: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Victor Tsaran
` Thomas Ward [this message]
` Victor Tsaran
` Thomas Ward
` Darrell Shandrow
` Victor Tsaran
` Darrell Shandrow
` Victor Tsaran
` Darrell Shandrow
` Darrell Shandrow
` Victor Tsaran
` Darrell Shandrow
` Victor Tsaran
` William F. Acker WB2FLW +1-303-777-8123
` Thomas Ward
[not found] ` <Pine.LNX.4.43.0112012231300.11896-100000@wb2flw.octothorp. org>
` Darrell Shandrow
` 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='00dd01c17a34$8fc31760$0100a8c0@polaris' \
--to=tward@bright.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).