From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: speakup 1.0 and slackware 8.0
Date: Sat, 29 Dec 2001 19:04:29 -0500 [thread overview]
Message-ID: <004801c190c5$8dd220c0$0100a8c0@tward> (raw)
In-Reply-To: <Pine.LNX.4.33.0112291539130.5573-100000@garnet.exorzero.com>
However, if he plans to install to the fat 32 msdos file system he will need
the msdos diskette.
----- Original Message -----
From: Keith Creasy <keith@garnet.exorzero.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, December 29, 2001 3:44 PM
Subject: Re: speakup 1.0 and slackware 8.0
> I found slackware 8.0 and the talking installation disk images by going to
> www.slackware.com/getslack and choosing one of the FTP mirrors. I think it
> was sunsite.
>
> there was a text file in the slackware 8.0 directory that described how to
> download and install slackware 8.0 with speakup. Basically I downloaded
> the slackware 8.0 ISO, the slackware.i boot image, and the color.gz root
> diske image.
>
> One thing I overlooked the first time I tried it was that you have to
> enter a command to get speakup to find your synthesizer awhen you boot
> with the diskette. When the diskette stops I had to enter "ramdisk
> speakup_synth=dtlk". this enabled it to talk through my doubletalk card.
> The rest of the installation was pretty much the normal series of steps.
>
> Good luck!
>
> Keith
>
>
> On Sat, 29 Dec 2001, Reinhard Stebner wrote:
>
> > > Slackware 8 does come with talking boot disks and kernel.
> >
> > The only thing I found on the speakup web site was slackware 7.1 with
> > speaking boot disks. Am I missing something?
> >
> > Thank you so much for your help it means a lot to me. Here are some
more
> > newbee questions. Could someone please explain how the man page works?
(by
> > taking a man page and saying what all of the [] {} and <> mean in
context?
> >
> > How dows one read one screen at a time instead of one line at a time?
> >
> > Is there a way to copy that page and save it and then braille out than
man
> > page?
> >
> > Is there any way to have a braille device working with speakup?
> >
> > Where can I find more docs on the proper feeding and care of my new os?
> >
> > What about speakup (see last quesion).
> >
> > How hard is it to find documentation on programming un unix/linux?
> > Is it quite differant from programming under dos?
> >
> > Final quesion, what are some do and don'ts when comming to:
> >
> > 1) installing and setting up the os
> > 2) running the os
> > 3) upgrading
> > 4) speakups limitations when comming to the operating this os?
> >
> > Thank you once again for your willingness to help me out.
> >
> >
> >
> > _______________________________________________
> > 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: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
Reinhard Stebner
` Raul A. Gallegos
` Thomas Ward
` Reinhard Stebner
` Keith Creasy
` Thomas Ward [this message]
` Reinhard Stebner
` Thomas Ward
` Gregory Nowak
` Gregory Nowak
` Reinhard Stebner
` Thomas Ward
` Reinhard Stebner
` Gregory Nowak
` Gregory Nowak
` Reinhard Stebner
` Gregory Nowak
` Gregory Nowak
` Reinhard Stebner
` Charles Hallenbeck
` Reinhard Stebner
` Reinhard Stebner
` Charles Hallenbeck
` Thomas Ward
` Jason
` Gregory Nowak
` Thomas Ward
` Gregory Nowak
` Thomas Ward
` Gregory Nowak
` Thomas Ward
` Reinhard Stebner
` Gregory Nowak
` Reinhard Stebner
` Thomas Ward
` Gregory Nowak
` Janina Sajka
` Gregory Nowak
` Reinhard Stebner
` Gregory Nowak
` Gregory Nowak
` Geoff Shang
` Gregory Nowak
` Thomas Ward
` Gregory Nowak
` Shaun Oliver
` Kirk Wood
` Shaun Oliver
` Thomas Ward
` 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='004801c190c5$8dd220c0$0100a8c0@tward' \
--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).