public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
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 20:57:17 -0800	[thread overview]
Message-ID: <000001c61346$db7f0150$230110ac@main> (raw)
In-Reply-To: <20060107044541.GA19678@server.yelavich.home>

Hi try a copy of the ferm ware dectalk 4.2b it does not need this file.
And you might get further.  
The usa.exe is the core langwige file for the dectalk and was introduced
in 4.2c 


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 Luke Yelavich
Sent: Friday, January 06, 2006 8:46 PM
To: speakup@braille.uwo.ca
Subject: Re: Problems attempting to set up Speakup with a DECtalk PC2.


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Jan 07, 2006 at 08:29:22AM EST, Luke Yelavich wrote:
> Hi all
> I have recently obtained a DECtalk PC2 card, and have successfully set
> it up and used it under Windows 98 with JAWS. I am now attempting to 
> make it work with Speakup under Linux.

I have since been doing some searching on google, and have found a 
couple of other dtload implementations, one of which I have already 
mentioned. I also noticed that one more file gets loaded when the 
DECtalk software loads in DOS. This file is also mentioned in other 
documentation on the web, yet the dec_pc.tgz package does not have this 
file, and it is not mentioned in the config file. The file I am 
referring to is usa.exe

Furthermore, I have noticed that the loader gets further with loading 
the files with the dec_pc.tgz files, than it does with the firmware from

my driver disk.

Through placing some debug messages in the dtload code, I noticed that 
with the firmware in the tarball, the initialization message gets sent, 
but nothing is spoken. Same with speakup, in that the driver and speakup

load fine, volume, pitch, and rate settings are fine, yet nothing gets 
spoken. I am wondering whether this is to do with the usa.exe file 
missing? I tried to add the file from my driver disk, but this causes 
the loader and the system to lock up.

More information as it comes to hand.
- -- 
Luke Yelavich
GPG key: 0xD06320CE 
	 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
ICQ: 18444344
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDv0d1jVefwtBjIM4RAiehAJ9tEziWAf7QkQnkbG4pEVaTf2YrIgCfQgLb
wL1fDgfjqaszdqNeIlzz0ts=
=nUhe
-----END PGP SIGNATURE-----

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup




  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Luke Yelavich
 ` Adam Myrow
   ` Jim Grimsby
     ` Hart Larry
       ` Luke Yelavich
         ` Hart Larry
 ` Luke Yelavich
   ` Jim Grimsby [this message]
     ` 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='000001c61346$db7f0150$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).