From: Thomas Ward <tward@bright.net>
To: Angelo Sonnesso <asonnesso@coastalnet.com>
Cc: <speakup@braille.uwo.ca>
Subject: Re: Making progress
Date: Tue, 20 Nov 2001 00:44:36 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111200041100.12574-100000@localhost.localdomain> (raw)
In-Reply-To: <011f01c17181$92499420$6c78f5cd@n6m3o7>
Hi, I think freedom scientific still has a copy of the Jaws for Dos
shareware on their site. If not I'll send you a copy of the shareware
version, and it might help solve the zipspeak problem.
http://www.freedomscientific.com
I used it quite a bit myself in looking for errors in loadlin.
On Mon, 19 Nov 2001, Angelo Sonnesso wrote:
> where did you find those files?
>
> ----- Original Message -----
> From: "Thomas Ward" <tward@bright.net>
> To: <speakup@braille.uwo.ca>
> Sent: Monday, November 19, 2001 5:24 PM
> Subject: Re: Making progress
>
>
> > Hi, if you have an old dos screen reader such as Jaws For Dos or Vocal
> Eyes
> > you can load that before running loadlin and that usually worked in
> getting
> > error messages
> > spoken. However, if it is a kernel panic error of some kind or an error
> > encountered after your machine loads Linux you will need to get those
> errors
> > with sited assistance assuming that Speakup hasn't loaded.
> >
> >
> >
> > ----- Original Message -----
> > From: "Glenn Ervin" <gervin@kdsi.net>
> > To: "linux - speakup" <speakup@braille.uwo.ca>
> > Sent: Monday, November 19, 2001 12:14 AM
> > Subject: Making progress
> >
> >
> > > Hello group,
> > > I downloaded zipslack.zip.
> > > I have a removable drive D:, and I unzipped it into that drive.
> > > I have downloaded many speakup files and I have put them into the
> d:\linux
> > > directory.
> > > This harddrive is a little over 200MB.
> > > I am using a DECtalk express on Comm1.
> > > I also edited the linux.bat file to have one of the lines to read:
> > > d:\linux\loadlin
> > > I rebooted into DOS and ran linux.bat and it ran for a few seconds, and
> it
> > > may have been ready to work, but I could not know what was on the
> screen.
> > > Question:
> > > How do I tell it to recognize the DECtalk on Com1?
> > > I hope I do not have to use sighted assistance to get this going.
> > > I look forward to any input.
> > > Thanks.
> > >
> > >
> > > Sincerely,
> > > O. Glenn Ervin-- (Lenny) N0YJV
> > > Northeast Nebraska
> > > gervin@kdsi.net
> > > or My Work e-mail:
> > > gervin@ncbvi.state.ne.us
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> 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: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Glenn Ervin
` Thomas Ward
` Angelo Sonnesso
` Thomas Ward [this message]
` Georgina
` playing audio cds randy turner
` Adam Myrow
` randy turner
` Gregory Nowak
` randy turner
` Gregory Nowak
` randy turner
` Gregory Nowak
` randy turner
` 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=Pine.LNX.4.33.0111200041100.12574-100000@localhost.localdomain \
--to=tward@bright.net \
--cc=asonnesso@coastalnet.com \
--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).