From: Lee Maschmeyer <Lee_Maschmeyer@wayne.edu>
To: blinux-list@redhat.com
Subject: Re: Diagnosing ABT320 Braille Terminal
Date: Fri, 9 May 2003 11:24:33 -0400 [thread overview]
Message-ID: <20030509152433.GB1336@wayne.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0305090822480.28940-100000@jumbo.chpi.org>
IMHO, one thing that adversely affects the Alva is that the left and
right keys are not typematic. I doubt this matters on an 80-character
display, but on a 40 it's a pain and I bet it's worse on a 20. Thanks to
Nicolas I found the place in the source where I could change it, but it
still seems an unfortunate default.
However, the Linux Alva driver seems more sluggish than (my memory of)
the DOS program, so I don't think it's the serial port settings since
DOS presumably uses the same ones. What are the BrailleLite's?
Lee
On Fri, May 09, 2003 at 08:25:31AM -0500, John J. Boyer wrote:
> Lee, the Alva works with brltty. But it's not nearly as good as the
> Braille Lite 40 that I normally use. At least I now have a backup
> braille display. I looked at the parameters after brltty had run and
> they do seem to be > 9600,n81. > Thanks, John On Fri, 9 May 2003, Lee
> Maschmeyer wrote: > > John, > > >
> It's not necessary to set anything on Linux. On the ABT, at least if
> the > > firmware is 970101, use the status menu to make sure the
> serial port > > you're using is set to pc. (If you have to change it,
> the setup menu > > choice is "Alva".) This can be done on the fly;
> use the > > Prog+Home+Status keys and follow the prompts. BRLTTY will
> recover > > properly when you exit the menu. > > > > Make sure the
> serial cable is a null-modes cable. BRLTTY will take care > > of the
> rest. > > > > I think Travis's settings are right; I think I saw it
> in the source for > > the Alva driver; but as I say, brltty does it
> all. > > > > I have no idea about Gnopernicus. Someone awhile ago
> listed the Braille > > devices supported and (at that time) Alva
> wasn't one of them. > > > > HTH, > > > > Lee > > > > > > >
> _______________________________________________ > > Blinux-list
> mailing list > > Blinux-list@redhat.com > >
> https://listman.redhat.com/mailman/listinfo/blinux-list > > > > -- >
> Computers to Help People, Inc. > http://www.chpi.org > 825 East
> Johnson; Madison, WI 53703 > > > > >
> _______________________________________________ > Blinux-list mailing
> list > Blinux-list@redhat.com >
> https://listman.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Travis Roth
` Lee Maschmeyer
` John J. Boyer
` Nicolas Pitre
` Lee Maschmeyer [this message]
` John J. Boyer
` Nicolas Pitre
` John J. Boyer
` Nicolas Pitre
` to John J. Boyer <director@chpi.org> Nicolas Pitre
` Diagnosing ABT320 Braille Terminal Tom Masterson
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=20030509152433.GB1336@wayne.edu \
--to=lee_maschmeyer@wayne.edu \
--cc=blinux-list@redhat.com \
/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).