From: "Jim Grimsby" <jimgrims@pacbell.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Problems attempting to set up Speakup with a DECtalk PC2.
Date: Fri, 6 Jan 2006 16:15:44 -0800 [thread overview]
Message-ID: <002501c6131f$87efa020$230110ac@main> (raw)
In-Reply-To: <Pine.LNX.4.64.0601061701160.28652@dell.midsouth.rr.com>
Hi, this does not sound like a speakup driver issue this sounds like a
dt loader issue. Remember the only thing that changed between pc 1 and
pc 2 was the firmware and the chip on the card. The communication did
not change at all nither did the in line commands. It sounds like the
issue is with loading the dt firmware on the card.
Hth
jim grimsby
msn: jim.grimsby@att.net
email: jimgrims@pacbell.net
skype: jim.grimsby
-----Original Message-----
From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Adam Myrow
Sent: Friday, January 06, 2006 3:08 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Problems attempting to set up Speakup with a DECtalk PC2.
I tried using the Dectalk PC 2 long ago with the Speakup driver, and had
similar problems. I found that what I often had to do is load it from
DOS, then do a soft reboot with control-alt-delete. I also had problems
where the Linux clock would lose time severely whenever the Dectalk PC 2
was active. I eventually gave up and went back to the Accent PC I had
gotten when the manufacturer was dumping his remaining stock. Once I
got
a new PC, I switched to the Dectalk USB in RS232 mode, and haven't
looked
back. The bottom line is that the Speakup driver may well work with the
original Dectalk PC, but seems not to work well with the later PC 2. I
don't have the slightest idea of what the cause is.
_______________________________________________
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: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Luke Yelavich
` Adam Myrow
` Jim Grimsby [this message]
` Hart Larry
` Luke Yelavich
` Hart Larry
` Luke Yelavich
` Jim Grimsby
` Luke Yelavich
` Jim Grimsby
` Luke Yelavich
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='002501c6131f$87efa020$230110ac@main' \
--to=jimgrims@pacbell.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).