FAQ gally2

FAQ gally2

[Ann Parsons]

Hi all,

Here is the edited version of the gally proof.  Some significant
corrections were made in the past ten minutes.



			     SPEAKUP FAQ

The document below is designed to answer the most frequently asked
questions about Speakup, the  screen reader/speech access system for
the Linux Operating System, used by people who are blind.  This
software is primarily developed and maintained by Kirk Reiser
(kirk@braille.uwo.ca).  It was developed initially by Kirk along with Andy
Berdan, with additional coding by John Covici and Brian Borowski.
Speakup was first announced on October 29, 1998 at:  08:55:28 -0500
     Most of the current development work is done by Kirk and Jim
Danley, along with contributions from other speakup users.



q.  Why should I use Speakup?

A.  If you are blind and want to use Linux as your operating system,
and if you want to know what is going on with your system from boot-up
to shut-down, then Speakup is for you.  Speakup gives you full access
to all console programs in the Linux OS.  It works particularly well
with telnet and with FTP. 


q.  Where do I get speakup?

A.  Speakup can be obtained by going to:  http://linux-speakup.org


q.  What kind of computer equipment do I need to run Speakup?

A.  The Linux OS can be placed on any PC from a 386 on up.  One will
receive best results from using a 486 or better machine, however.  


q.  What speech synthesizers are supported by Speakup.

A.  At the moment, Speakup supports only hardware synthesizers.  Here
is a list of what is currently supported.

Accent PC: acntpc
Accent SA: acntsa
Apolo: apolo
Audapter: audptr
Braille 'n Speak, and other such Blazie products: bns
DecTalk External (older model): decext
DecTalk PC (newer model): dectlk
DoubleTalk PC (internal): dtlk
LiteTalk/DoubleTalk LT (external): ltlk
Speakout: spkout
Transport: txprt
This list is current as of speakup version 0.10.

Instructions on installation for each synthesizer can be found at the
URL listed above.

  
q.  Will Speakup work on a Windows system?

A.  Although Speakup is a Linux Program and does not work in Windows,
there is a mini version of Linux plus speakup that can be run on a
dos/windows system.  It is called Zipspeak.  It was designed by
Matthew Campbell and can be obtained by going to:  

http://www.linux-speakup.org/zipspeak.html

This is an excellent option if you are interested in Linux but do not
wish to devote much disk space, or resources to it.  It can be
expanded into a full Linux system should you wish to do so.


q.  I have heard about Emacspeak.  How does Speakup differ and which
is better, or do I need both?

A.  Emacspeak, developed by T.V. Raman and currently in version 14, is
a verbal output system for Emacs, the customizable editor for
Unix/Linux.  It is a complete desktop system for the OS, and works
well with any console application that has been linked to it.
However, it has some significant drawbacks.  It does not work well
with Telnet or with FTP, and it does not give access to programs with
which it is not linked.  

However, there is a way to install both Speakup and Emacspeak on one's
system.  This allows full access to all console programs plus the
desktop environment of Emacs.  

Emacspeak can be downloaded from sourceforge via HTTP or FTP:

http://emacspeak.sourceforge.net

ftp://emacspeak.sourceforge.net/pub/emacspeak 

You can visit Emacspeak on the WWW at

http://www.cs.cornell.edu/home/raman/emacspeak (Cornell) --You
can also pick up emacspeak via anonymous ftp from

ftp://ftp.cs.cornell.edu/pub/raman/emacspeak/.


q. What versions of speakup work with what kernels?

A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
and above.  For further information, ask on the speakup list.  


q.  How do I install Speakup?

A.  The easiest way is to download the appropriate precompiled kernel for your
synthesizer if the kernel is lower than 2.2.18 and install from the
downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
likely that there is a generic patched kernel and you have to enter a string
to tell speakup what synthesizer you wish to use.  For example:

speakup_synthesizer=dectlk speakup_serial=0

The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
Linux.

Having obtained the appropriate kernel image that matches your distribution
and synthesizer, you can either create boot up disks with the dd command on
Unix type systems or rawrite under DOS or Windows, or by placing the
necessary files into a directory and using loadlin to start the installation
process.  For example: if the image is called bare.i, under Unix type system
you'd use the command string:

dd . . . .(Sorry don't know the string)

To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
and bare.i are in the same directory as each other, say for example c:\Linux
you'd enter at a command prompt the following command strings:

cd c:\Linux
[Press return]
rawrite bare.i a:
[Press return]

Loadlin.exe enables a Linux installation to be started from a DOS prompt,
before going into Windows.  You'd need to create a batch file to run
loadlin.exe with the appropriate parameters.

Rawrite.exe and loadlin.exe can usually be found in a directory called
dosutils on distribution CD's, or something like that depending upon the
distribution.  They're often accompanied with detailed documentation.


Q.  What is the best way to download the appropriate file from the
site.  

A.  FTP is the quickest way to do this, although you can use the web
site's download facility.  One caveat, MSIE users be sure to type in
the address for the archive with ftp: in stead of http.  Some MSIE
users have trouble downloading the files because MSIE puts line-feeds
where they should not go.  If you do not have an FTP client, then try
using the Windows FTP client from a DOS box.  Be sure to type bin
before starting any transfer.  


Q.  I've just used rawrite to make a boot disk for my system, and it
will not talk, it will not do anything.  Why?

A.  Your speech synthesizer probably got in the way.  Before typing
the command again, turn off your speech program.  


q. why doesn't speakup come up talking when I use bla bla bla distros
boot disk?

A.  There are many reasons for this including:  a bad rawrite image,
the wrong comm port setting in the command line, an improperly
downloaded file.  For more specific information consult the
documentation file or ask on the Speakup list.

q. what is the status of cursering?

A.  The cursoring problem has been solved in part.  It is still in the
process of solution.


Q.  I hate documentation, and find it difficult to use because I do
not understand it.  How can I contact live human beings for help? 

A.  The simplest way to contact us is via our mailing list.  To
subscribe to this list, send an msg to:

speakup-request@braille.uwo.ca

In the body of the message, simply write subscribe.  when you have
done this, you will receive information on how to send directly to the
list.  Please keep this information for future reference.  

We can also be reached via Internet telephony by using the speakfreely
program.  this program can be downloaded at:

http://www.formilab.ch/speakfree/unix

When you have installed the program, access the reflector by entering
:

lwl..braille.uwo.ca port 4074 

To see who is on the reflector, go to:

http://lwl.braille.uwo.ca/speakup.html


			    Ann K. Parsons





-- 
			Ann K. Parsons  
email:  akp@eznet.net 			ICQ Number:  33006854
WEB SITE:  http://home.eznet.net/~akp
"All that is gold does not glitter.  Not all those who wander are lost."  JRRT

Re: FAQ gally2

[Geoff Shang]

On Sun, 17 Jun 2001, Ann Parsons wrote:

> q. What versions of speakup work with what kernels?
>
> A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
> and above.  For further information, ask on the speakup list.

I think we could insert a sentence saying that speakup 0.09 works with most
other versions of kernel 2.2.  Also, the supported kernels are listed in
the README or announcement for that version.

> q.  How do I install Speakup?
>
> A.  The easiest way is to download the appropriate precompiled kernel for your

I think we need to insert a bit before this answer.  Something like:

If you already run linux, you will probably want to recompile your kernel
with speakup included.  To do this, download the speakup source code from
the speakup site and follow the instructions in the README file on how to
patch speakup into your kernel.

If you wish to install linux using speakup, the easiest way is to download
(etc, etc, etc).

> speakup_synthesizer=dectlk speakup_serial=0

hmmm...I've never seen these written longhand before.  Does this actually
work Kirk?  AFAIK, the sommands are speakup_synth and speakup_ser.

> The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> Linux.

You might want to add a sentence here saying "Refer to the list of
supported synthesisers above for the correct string to use here." or
something similar.

> dd . . . .(Sorry don't know the string)

dd if=bare.i of=/dev/fd0

> http://www.formilab.ch/speakfree/unix

This is the unix version.  The windows one can be gotten from
www.speakfreely.org

> When you have installed the program, access the reflector by entering
> :
>
> lwl..braille.uwo.ca port 4074

You need to enter the following:

sfspeaker -j &
sfspeaker -p4074 -j &
sfmike lwl.braille.uwo.ca:4074

Note that your quote above has a double dot in it.

Nice job, Ann.

Geoff.

Re: FAQ gally2: Speakup Versions

[Janina Sajka]

I think the business of speakup versions needs to be a little clearer. We
mention that the current version is 0.10. Then, a few paragraphs below, we
mention version 0.10a. So, the chickens come home to roost on poorly
chosen numbering schemes--but that's not what I want to talk about ...

The poine in the faq needs to be clear guidance. Ann, this is really very
excellent so far, but I think it's important to say something up front
such as:

"There are two current versions of speakup. Which one you should use
depends on what linux kernel version you have. To find out, issue this
command:

	uname -a

If your kernel version is less than ... etc.
If it's greater than, ... etc.

Re: FAQ gally2: Speakup and Emacspeak

[Janina Sajka]

Before I dive into my comments re the treatment of speakup vs emacspeak in
the FAQ draft, let me again say that I'm very impressed, Ann, with the
quality of this writing. It's not easy to make technical documentation
clear. You've done a stellar job of it.

Now to my comments. I post them to the list, by the way, because I suspect
others may want to say something about this.

I really don't think we've done the speakup vs emacspeak issue justice.
The especially good at, and not especially good at business with telent
and ftp leaves me cold. But, it also doesn't address the more central
points, imho. So, let me suggest that:

The greatest strength of speakup is that it's very easy to learn to use it
once it's installed. In fact, for the most part, you'll just forget about
speakup and concentrate on the things you're doing in linux instead. For
example, you can surf the world wide web, and even play Real Audio and mp3
right from the command line.

The strength of emacspeak is the clever and powerful way that the audio
desktop works for blind users. The weakness of emacspeak is that there's a
lot of commands to learn before you can get good at it. If you already
know how to use emacs, you'll love emacspeak. If you don't know what that
is, you'll have a lot of learning to do before you'll feel comfortable
with emacspeak--though it's probably worth the effort.

Re: FAQ gally2: What is linux?

[Janina Sajka]

I think we need to add this question. Here are some unpolished sentences
that I think inform the eventual answer:

Linux is a computer operating system. Other operating systems you probably
already know about include Windows and DOS. Linux is different from these
in many ways, but the most important difference is that it's very powerful
and it's absolutely free. If you ever had a dialup shell account in the
past where you used programs like pine and lynx, that's what you'll get
with linux right on your very own computer. How hard it is to use will
depend on what kinds of things you're comfortable with, and how much you
want to do. If you don't mind typing commands to get a program that works
fast and doesn't crash, you'll love linux. And, the sky's the limit for
what you can do with it.

Re: FAQ gally2

[Chris Nestrud]

The question:
q.  What speech synthesizers are supported by Speakup.
refers to a URL which isn't given. you might also want to put an
explanation of the need for the synthesizer codes. Also, it might be a
good idea to
put the document explaining boot parameters somewhere and link to that.
I'm referring to the "why doesn't speakup talk" question. It lists
possible problems, but doesn't offer a link to a document with a
solution.

Chris

On Sun, Jun 17, 2001 at 10:09:58AM -0400, Ann Parsons wrote:
> Hi all,
> 
> Here is the edited version of the gally proof.  Some significant
> corrections were made in the past ten minutes.
> 
> 
> 
> 			     SPEAKUP FAQ
> 
> The document below is designed to answer the most frequently asked
> questions about Speakup, the  screen reader/speech access system for
> the Linux Operating System, used by people who are blind.  This
> software is primarily developed and maintained by Kirk Reiser
> (kirk@braille.uwo.ca).  It was developed initially by Kirk along with Andy
> Berdan, with additional coding by John Covici and Brian Borowski.
> Speakup was first announced on October 29, 1998 at:  08:55:28 -0500
>      Most of the current development work is done by Kirk and Jim
> Danley, along with contributions from other speakup users.
> 
> 
> 
> q.  Why should I use Speakup?
> 
> A.  If you are blind and want to use Linux as your operating system,
> and if you want to know what is going on with your system from boot-up
> to shut-down, then Speakup is for you.  Speakup gives you full access
> to all console programs in the Linux OS.  It works particularly well
> with telnet and with FTP. 
> 
> 
> q.  Where do I get speakup?
> 
> A.  Speakup can be obtained by going to:  http://linux-speakup.org
> 
> 
> q.  What kind of computer equipment do I need to run Speakup?
> 
> A.  The Linux OS can be placed on any PC from a 386 on up.  One will
> receive best results from using a 486 or better machine, however.  
> 
> 
> q.  What speech synthesizers are supported by Speakup.
> 
> A.  At the moment, Speakup supports only hardware synthesizers.  Here
> is a list of what is currently supported.
> 
> Accent PC: acntpc
> Accent SA: acntsa
> Apolo: apolo
> Audapter: audptr
> Braille 'n Speak, and other such Blazie products: bns
> DecTalk External (older model): decext
> DecTalk PC (newer model): dectlk
> DoubleTalk PC (internal): dtlk
> LiteTalk/DoubleTalk LT (external): ltlk
> Speakout: spkout
> Transport: txprt
> This list is current as of speakup version 0.10.
> 
> Instructions on installation for each synthesizer can be found at the
> URL listed above.
> 
>   
> q.  Will Speakup work on a Windows system?
> 
> A.  Although Speakup is a Linux Program and does not work in Windows,
> there is a mini version of Linux plus speakup that can be run on a
> dos/windows system.  It is called Zipspeak.  It was designed by
> Matthew Campbell and can be obtained by going to:  
> 
> http://www.linux-speakup.org/zipspeak.html
> 
> This is an excellent option if you are interested in Linux but do not
> wish to devote much disk space, or resources to it.  It can be
> expanded into a full Linux system should you wish to do so.
> 
> 
> q.  I have heard about Emacspeak.  How does Speakup differ and which
> is better, or do I need both?
> 
> A.  Emacspeak, developed by T.V. Raman and currently in version 14, is
> a verbal output system for Emacs, the customizable editor for
> Unix/Linux.  It is a complete desktop system for the OS, and works
> well with any console application that has been linked to it.
> However, it has some significant drawbacks.  It does not work well
> with Telnet or with FTP, and it does not give access to programs with
> which it is not linked.  
> 
> However, there is a way to install both Speakup and Emacspeak on one's
> system.  This allows full access to all console programs plus the
> desktop environment of Emacs.  
> 
> Emacspeak can be downloaded from sourceforge via HTTP or FTP:
> 
> http://emacspeak.sourceforge.net
> 
> ftp://emacspeak.sourceforge.net/pub/emacspeak 
> 
> You can visit Emacspeak on the WWW at
> 
> http://www.cs.cornell.edu/home/raman/emacspeak (Cornell) --You
> can also pick up emacspeak via anonymous ftp from
> 
> ftp://ftp.cs.cornell.edu/pub/raman/emacspeak/.
> 
> 
> q. What versions of speakup work with what kernels?
> 
> A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
> and above.  For further information, ask on the speakup list.  
> 
> 
> q.  How do I install Speakup?
> 
> A.  The easiest way is to download the appropriate precompiled kernel for your
> synthesizer if the kernel is lower than 2.2.18 and install from the
> downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> likely that there is a generic patched kernel and you have to enter a string
> to tell speakup what synthesizer you wish to use.  For example:
> 
> speakup_synthesizer=dectlk speakup_serial=0
> 
> The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> Linux.
> 
> Having obtained the appropriate kernel image that matches your distribution
> and synthesizer, you can either create boot up disks with the dd command on
> Unix type systems or rawrite under DOS or Windows, or by placing the
> necessary files into a directory and using loadlin to start the installation
> process.  For example: if the image is called bare.i, under Unix type system
> you'd use the command string:
> 
> dd . . . .(Sorry don't know the string)
> 
> To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> and bare.i are in the same directory as each other, say for example c:\Linux
> you'd enter at a command prompt the following command strings:
> 
> cd c:\Linux
> [Press return]
> rawrite bare.i a:
> [Press return]
> 
> Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> before going into Windows.  You'd need to create a batch file to run
> loadlin.exe with the appropriate parameters.
> 
> Rawrite.exe and loadlin.exe can usually be found in a directory called
> dosutils on distribution CD's, or something like that depending upon the
> distribution.  They're often accompanied with detailed documentation.
> 
> 
> Q.  What is the best way to download the appropriate file from the
> site.  
> 
> A.  FTP is the quickest way to do this, although you can use the web
> site's download facility.  One caveat, MSIE users be sure to type in
> the address for the archive with ftp: in stead of http.  Some MSIE
> users have trouble downloading the files because MSIE puts line-feeds
> where they should not go.  If you do not have an FTP client, then try
> using the Windows FTP client from a DOS box.  Be sure to type bin
> before starting any transfer.  
> 
> 
> Q.  I've just used rawrite to make a boot disk for my system, and it
> will not talk, it will not do anything.  Why?
> 
> A.  Your speech synthesizer probably got in the way.  Before typing
> the command again, turn off your speech program.  
> 
> 
> q. why doesn't speakup come up talking when I use bla bla bla distros
> boot disk?
> 
> A.  There are many reasons for this including:  a bad rawrite image,
> the wrong comm port setting in the command line, an improperly
> downloaded file.  For more specific information consult the
> documentation file or ask on the Speakup list.
> 
> q. what is the status of cursering?
> 
> A.  The cursoring problem has been solved in part.  It is still in the
> process of solution.
> 
> 
> Q.  I hate documentation, and find it difficult to use because I do
> not understand it.  How can I contact live human beings for help? 
> 
> A.  The simplest way to contact us is via our mailing list.  To
> subscribe to this list, send an msg to:
> 
> speakup-request@braille.uwo.ca
> 
> In the body of the message, simply write subscribe.  when you have
> done this, you will receive information on how to send directly to the
> list.  Please keep this information for future reference.  
> 
> We can also be reached via Internet telephony by using the speakfreely
> program.  this program can be downloaded at:
> 
> http://www.formilab.ch/speakfree/unix
> 
> When you have installed the program, access the reflector by entering
> :
> 
> lwl..braille.uwo.ca port 4074 
> 
> To see who is on the reflector, go to:
> 
> http://lwl.braille.uwo.ca/speakup.html
> 
> 
> 			    Ann K. Parsons
> 
> 
> 
> 
> 
> -- 
> 			Ann K. Parsons  
> email:  akp@eznet.net 			ICQ Number:  33006854
> WEB SITE:  http://home.eznet.net/~akp
> "All that is gold does not glitter.  Not all those who wander are lost."  JRRT
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: The Cursoring Problem

[Janina Sajka]

This answer is inadequate because the problem is not explained. My sense
is that either the problem itself should be explained--what is cursoring
and how does speakup support it?--or the whole thing should just be left
out of the FAQ.

Re: FAQ gally2: Distro Prejudice

[Janina Sajka]

I expect we don't want to betray a bias toward one linux distribution over
any other. In fact, I think the current faq does exactly that without
meaning to. All the examples are slackware based.

The solution, imho, is to carefully insure that examples are given in such
a way that the main distros are represented somewhere in the faq. I don't
mean many examples, one for each distro, where examples are. I just mean
that on the whole, there should be parity. Else, there's a subtle
implication of favor.

Re: FAQ gally2: System Requirements

[Janina Sajka]

I don't think it's useful to leave the minimum system requirement as it
is. While it is academically true that one can run linux with speakup on a
386 or 486 system, doing so is a little bit more dificult than our blithe
comments suggest. It seems to me that most people here on out will use
some of the canned installation distributions, Debian, Slack, Redhat,
where speakup is already compiled in. How well do these support
installations on older chips with only a few hundred megabytes of hard
disk space? If they do that well--never mind this post. But, if not, let's
not steer people wrong.


Suggestion:

Installation on older computers is not advised for people who've never
installed linux before. It's just harder, much harder, to get it
working. For
best results, especially if you want to listen to Real Audio and mp3s,
you should use a Pentium system with a hard disk that has several
gigabytes of space.

Re: FAQ gally2: System Requirements

[Chris Nestrud]

You could mention that anything which runs Windows haf-way decently
should work well with linux. This is just meant to assure new users
that, if they're using their computer for Windows tasks, it's likely to
work well with linux.

Chris

On Sun, Jun 17, 2001 at 12:04:03PM -0400, Janina Sajka wrote:
> I don't think it's useful to leave the minimum system requirement as it
> is. While it is academically true that one can run linux with speakup on a
> 386 or 486 system, doing so is a little bit more dificult than our blithe
> comments suggest. It seems to me that most people here on out will use
> some of the canned installation distributions, Debian, Slack, Redhat,
> where speakup is already compiled in. How well do these support
> installations on older chips with only a few hundred megabytes of hard
> disk space? If they do that well--never mind this post. But, if not, let's
> not steer people wrong.
> 
> 
> Suggestion:
> 
> Installation on older computers is not advised for people who've never
> installed linux before. It's just harder, much harder, to get it
> working. For
> best results, especially if you want to listen to Real Audio and mp3s,
> you should use a Pentium system with a hard disk that has several
> gigabytes of space.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: The easiest way to install

[Janina Sajka]

The part of the FAQ that describes the "easiest way" to get speakup is on
the wrong track, but is quite incorrect.

Problem: People ;do not "download a kernel for their synthesizer." This is
not how it is, but it is what's written currently.

Correction Suggestion:

Select the linux distribution you want to install and download the
installation files for that distribution from the speakup web site. Do not
download them from any source that doesn't explicitly say speakup, because
you want to be sure and get the version that already has speakup included
with it.

The second part is really about how to launch the installation once the
distro is obtained and the floppies correctly created with rawrite or dd.
The guidance given currently is essentially correct. But, it could be
clearer. In particular, it should be made clear that the first prompt will
not speak, and that people will need to type without speech to indicate
what synth they have and where it is connected so that the program will
know what synth to talk to and where to find it. This is what
speakup_synth and speakup_ser mean, respectively.
 On Sun, 17 Jun 2001, Ann
Parsons wrote:

> A.  The easiest way is to download the appropriate precompiled kernel for your
> synthesizer if the kernel is lower than 2.2.18 and install from the
> downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> likely that there is a generic patched kernel and you have to enter a string
> to tell speakup what synthesizer you wish to use.  For example:
>
> speakup_synthesizer=dectlk speakup_serial=0
>
> The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> Linux.
>
> Having obtained the appropriate kernel image that matches your distribution
> and synthesizer, you can either create boot up disks with the dd command on
> Unix type systems or rawrite under DOS or Windows, or by placing the
> necessary files into a directory and using loadlin to start the installation
> process.  For example: if the image is called bare.i, under Unix type system
> you'd use the command string:
>
> dd . . . .(Sorry don't know the string)
>
> To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> and bare.i are in the same directory as each other, say for example c:\Linux
> you'd enter at a command prompt the following command strings:
>
> cd c:\Linux
> [Press return]
> rawrite bare.i a:
> [Press return]
>
> Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> before going into Windows.  You'd need to create a batch file to run
> loadlin.exe with the appropriate parameters.
>
> Rawrite.exe and loadlin.exe can usually be found in a directory called
> dosutils on distribution CD's, or something like that depending upon the
> distribution.  They're often accompanied with detailed documentation.
>
>
> Q.  What is the best way to download the appropriate file from the
> site.
>
> A.  FTP is the quickest way to do this, although you can use the web
> site's download facility.  One caveat, MSIE users be sure to type in
> the address for the archive with ftp: in stead of http.  Some MSIE
> users have trouble downloading the files because MSIE puts line-feeds
> where they should not go.  If you do not have an FTP client, then try
> using the Windows FTP client from a DOS box.  Be sure to type bin
> before starting any transfer.
>
>
> Q.  I've just used rawrite to make a boot disk for my system, and it
> will not talk, it will not do anything.  Why?
>
> A.  Your speech synthesizer probably got in the way.  Before typing
> the command again, turn off your speech program.
>
>
> q. why doesn't speakup come up talking when I use bla bla bla distros
> boot disk?
>
> A.  There are many reasons for this including:  a bad rawrite image,
> the wrong comm port setting in the command line, an improperly
> downloaded file.  For more specific information consult the
> documentation file or ask on the Speakup list.
>
> q. what is the status of cursering?
>
> A.  The cursoring problem has been solved in part.  It is still in the
> process of solution.
>
>
> Q.  I hate documentation, and find it difficult to use because I do
> not understand it.  How can I contact live human beings for help?
>
> A.  The simplest way to contact us is via our mailing list.  To
> subscribe to this list, send an msg to:
>
> speakup-request@braille.uwo.ca
>
> In the body of the message, simply write subscribe.  when you have
> done this, you will receive information on how to send directly to the
> list.  Please keep this information for future reference.
>
> We can also be reached via Internet telephony by using the speakfreely
> program.  this program can be downloaded at:
>
> http://www.formilab.ch/speakfree/unix
>
> When you have installed the program, access the reflector by entering
> :
>
> lwl..braille.uwo.ca port 4074
>
> To see who is on the reflector, go to:
>
> http://lwl.braille.uwo.ca/speakup.html
>
>
> 			    Ann K. Parsons
>
>
>
>
>
>

Re: FAQ gally2

[Darcy Burnard]

Hi Ann, great job with the faq.  The only comment I would make is that in
the list of supported synths, you've got the DecTalk PC listed rather than
the DecTalk Express.  I've been off the list for a few months now, so
I could be wrong here, but I don't believe that the DecTalk PC is
supported under speakup as yet.
Darcy Burnard


On Sun, 17 Jun 2001, Ann Parsons wrote:

> Hi all,
> 
> Here is the edited version of the gally proof.  Some significant
> corrections were made in the past ten minutes.
> 
> 
> 
> 			     SPEAKUP FAQ
> 
> The document below is designed to answer the most frequently asked
> questions about Speakup, the  screen reader/speech access system for
> the Linux Operating System, used by people who are blind.  This
> software is primarily developed and maintained by Kirk Reiser
> (kirk@braille.uwo.ca).  It was developed initially by Kirk along with Andy
> Berdan, with additional coding by John Covici and Brian Borowski.
> Speakup was first announced on October 29, 1998 at:  08:55:28 -0500
>      Most of the current development work is done by Kirk and Jim
> Danley, along with contributions from other speakup users.
> 
> 
> 
> q.  Why should I use Speakup?
> 
> A.  If you are blind and want to use Linux as your operating system,
> and if you want to know what is going on with your system from boot-up
> to shut-down, then Speakup is for you.  Speakup gives you full access
> to all console programs in the Linux OS.  It works particularly well
> with telnet and with FTP. 
> 
> 
> q.  Where do I get speakup?
> 
> A.  Speakup can be obtained by going to:  http://linux-speakup.org
> 
> 
> q.  What kind of computer equipment do I need to run Speakup?
> 
> A.  The Linux OS can be placed on any PC from a 386 on up.  One will
> receive best results from using a 486 or better machine, however.  
> 
> 
> q.  What speech synthesizers are supported by Speakup.
> 
> A.  At the moment, Speakup supports only hardware synthesizers.  Here
> is a list of what is currently supported.
> 
> Accent PC: acntpc
> Accent SA: acntsa
> Apolo: apolo
> Audapter: audptr
> Braille 'n Speak, and other such Blazie products: bns
> DecTalk External (older model): decext
> DecTalk PC (newer model): dectlk
> DoubleTalk PC (internal): dtlk
> LiteTalk/DoubleTalk LT (external): ltlk
> Speakout: spkout
> Transport: txprt
> This list is current as of speakup version 0.10.
> 
> Instructions on installation for each synthesizer can be found at the
> URL listed above.
> 
>   
> q.  Will Speakup work on a Windows system?
> 
> A.  Although Speakup is a Linux Program and does not work in Windows,
> there is a mini version of Linux plus speakup that can be run on a
> dos/windows system.  It is called Zipspeak.  It was designed by
> Matthew Campbell and can be obtained by going to:  
> 
> http://www.linux-speakup.org/zipspeak.html
> 
> This is an excellent option if you are interested in Linux but do not
> wish to devote much disk space, or resources to it.  It can be
> expanded into a full Linux system should you wish to do so.
> 
> 
> q.  I have heard about Emacspeak.  How does Speakup differ and which
> is better, or do I need both?
> 
> A.  Emacspeak, developed by T.V. Raman and currently in version 14, is
> a verbal output system for Emacs, the customizable editor for
> Unix/Linux.  It is a complete desktop system for the OS, and works
> well with any console application that has been linked to it.
> However, it has some significant drawbacks.  It does not work well
> with Telnet or with FTP, and it does not give access to programs with
> which it is not linked.  
> 
> However, there is a way to install both Speakup and Emacspeak on one's
> system.  This allows full access to all console programs plus the
> desktop environment of Emacs.  
> 
> Emacspeak can be downloaded from sourceforge via HTTP or FTP:
> 
> http://emacspeak.sourceforge.net
> 
> ftp://emacspeak.sourceforge.net/pub/emacspeak 
> 
> You can visit Emacspeak on the WWW at
> 
> http://www.cs.cornell.edu/home/raman/emacspeak (Cornell) --You
> can also pick up emacspeak via anonymous ftp from
> 
> ftp://ftp.cs.cornell.edu/pub/raman/emacspeak/.
> 
> 
> q. What versions of speakup work with what kernels?
> 
> A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
> and above.  For further information, ask on the speakup list.  
> 
> 
> q.  How do I install Speakup?
> 
> A.  The easiest way is to download the appropriate precompiled kernel for your
> synthesizer if the kernel is lower than 2.2.18 and install from the
> downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> likely that there is a generic patched kernel and you have to enter a string
> to tell speakup what synthesizer you wish to use.  For example:
> 
> speakup_synthesizer=dectlk speakup_serial=0
> 
> The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> Linux.
> 
> Having obtained the appropriate kernel image that matches your distribution
> and synthesizer, you can either create boot up disks with the dd command on
> Unix type systems or rawrite under DOS or Windows, or by placing the
> necessary files into a directory and using loadlin to start the installation
> process.  For example: if the image is called bare.i, under Unix type system
> you'd use the command string:
> 
> dd . . . .(Sorry don't know the string)
> 
> To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> and bare.i are in the same directory as each other, say for example c:\Linux
> you'd enter at a command prompt the following command strings:
> 
> cd c:\Linux
> [Press return]
> rawrite bare.i a:
> [Press return]
> 
> Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> before going into Windows.  You'd need to create a batch file to run
> loadlin.exe with the appropriate parameters.
> 
> Rawrite.exe and loadlin.exe can usually be found in a directory called
> dosutils on distribution CD's, or something like that depending upon the
> distribution.  They're often accompanied with detailed documentation.
> 
> 
> Q.  What is the best way to download the appropriate file from the
> site.  
> 
> A.  FTP is the quickest way to do this, although you can use the web
> site's download facility.  One caveat, MSIE users be sure to type in
> the address for the archive with ftp: in stead of http.  Some MSIE
> users have trouble downloading the files because MSIE puts line-feeds
> where they should not go.  If you do not have an FTP client, then try
> using the Windows FTP client from a DOS box.  Be sure to type bin
> before starting any transfer.  
> 
> 
> Q.  I've just used rawrite to make a boot disk for my system, and it
> will not talk, it will not do anything.  Why?
> 
> A.  Your speech synthesizer probably got in the way.  Before typing
> the command again, turn off your speech program.  
> 
> 
> q. why doesn't speakup come up talking when I use bla bla bla distros
> boot disk?
> 
> A.  There are many reasons for this including:  a bad rawrite image,
> the wrong comm port setting in the command line, an improperly
> downloaded file.  For more specific information consult the
> documentation file or ask on the Speakup list.
> 
> q. what is the status of cursering?
> 
> A.  The cursoring problem has been solved in part.  It is still in the
> process of solution.
> 
> 
> Q.  I hate documentation, and find it difficult to use because I do
> not understand it.  How can I contact live human beings for help? 
> 
> A.  The simplest way to contact us is via our mailing list.  To
> subscribe to this list, send an msg to:
> 
> speakup-request@braille.uwo.ca
> 
> In the body of the message, simply write subscribe.  when you have
> done this, you will receive information on how to send directly to the
> list.  Please keep this information for future reference.  
> 
> We can also be reached via Internet telephony by using the speakfreely
> program.  this program can be downloaded at:
> 
> http://www.formilab.ch/speakfree/unix
> 
> When you have installed the program, access the reflector by entering
> :
> 
> lwl..braille.uwo.ca port 4074 
> 
> To see who is on the reflector, go to:
> 
> http://lwl.braille.uwo.ca/speakup.html
> 
> 
> 			    Ann K. Parsons
> 
> 
> 
> 
> 
> -- 
> 			Ann K. Parsons  
> email:  akp@eznet.net 			ICQ Number:  33006854
> WEB SITE:  http://home.eznet.net/~akp
> "All that is gold does not glitter.  Not all those who wander are lost."  JRRT
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: FAQ gally2: Miscellaneous

[Janina Sajka]

A few minor points:

On Sun, 17 Jun 2001, Ann Parsons wrote:

> The document below is designed to answer the most frequently asked
> questions about Speakup, the  screen reader/speech access system for
> the Linux Operating System, used by people who are blind.
I think we mean that speakup is used by people who are blind, not linux
the operating system. In other words, linux isn't for blind people,
speakup is.

> This
> software is primarily developed and maintained by Kirk Reiser

What software? Linux? One could think that because it's the last software
mentioned, so correct grammar suggests that "this" means linux, whereas we
know it really means speakup. Better to just say "speakup."
> Speakup gives you full access
> to all console programs in the Linux OS.
True, but many people, even people very good at using Windows, will not
understand this because they've not encountered the concept of "consoles."
Better to say "character based," or better still "text-based." Examples
like pine and lynx would help illustrate the point.

> A.  At the moment, Speakup supports only hardware synthesizers.  Here
> is a list of what is currently supported.
>
> Accent PC: acntpc
> Accent SA: acntsa
> Apolo: apolo
> Audapter: audptr
> Braille 'n Speak, and other such Blazie products: bns
> DecTalk External (older model): decext
> DecTalk PC (newer model): dectlk
> DoubleTalk PC (internal): dtlk
> LiteTalk/DoubleTalk LT (external): ltlk
> Speakout: spkout
> Transport: txprt
> This list is current as of speakup version 0.10.

I suggest explaining why the keywords are here, something like:

"Notice the keyword abrieviation given above for your speech synthesizer.
You will need to use it, so be sure to note its spelling and learn it
now."

> Instructions on installation for each synthesizer can be found at the
> URL listed above.
>
True, but why not give it again? If the reader is here, then a link here
would be helpful.

> Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> before going into Windows.  You'd need to create a batch file to run
> loadlin.exe with the appropriate parameters.

Why a batch file? Why not just type the command on the command line? Isn't
it just a matter of passing the appropriate speakup_ser and speakup_synth
plus appropriate image arguments?  I think it would make m0ore sense to
prototype this then to get into talking about creating batch files.

> A.  There are many reasons for this including:  a bad rawrite image,
> the wrong comm port setting in the command line, an improperly

Ooopps. "com port" is a Windows designation. Better to be neutral by
saying "serial port."

Re: FAQ gally2: System Requirements

[Janina Sajka]

Good suggestion, Chris. Should it be "newer Windows system?" I'm thinking
there are still folks out  there with Win 3.11 and Win 95 on boxes with
only megabytes of hd.
 On Sun, 17 Jun 2001, Chris Nestrud wrote:

> You could mention that anything which runs Windows haf-way decently
> should work well with linux. This is just meant to assure new users
> that, if they're using their computer for Windows tasks, it's likely to
> work well with linux.
>
> Chris
>
> On Sun, Jun 17, 2001 at 12:04:03PM -0400, Janina Sajka wrote:
> > I don't think it's useful to leave the minimum system requirement as it
> > is. While it is academically true that one can run linux with speakup on a
> > 386 or 486 system, doing so is a little bit more dificult than our blithe
> > comments suggest. It seems to me that most people here on out will use
> > some of the canned installation distributions, Debian, Slack, Redhat,
> > where speakup is already compiled in. How well do these support
> > installations on older chips with only a few hundred megabytes of hard
> > disk space? If they do that well--never mind this post. But, if not, let's
> > not steer people wrong.
> >
> >
> > Suggestion:
> >
> > Installation on older computers is not advised for people who've never
> > installed linux before. It's just harder, much harder, to get it
> > working. For
> > best results, especially if you want to listen to Real Audio and mp3s,
> > you should use a Pentium system with a hard disk that has several
> > gigabytes of space.
> >
> >
> >
> > _______________________________________________
> > 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
>

Re: FAQ gally2

[Janina Sajka]

Yes, dectlk is the Express. Good catch.

On Sun, 17 Jun 2001, Darcy Burnard wrote:

> Hi Ann, great job with the faq.  The only comment I would make is that in
> the list of supported synths, you've got the DecTalk PC listed rather than
> the DecTalk Express.  I've been off the list for a few months now, so
> I could be wrong here, but I don't believe that the DecTalk PC is
> supported under speakup as yet.
> Darcy Burnard
>
>
> On Sun, 17 Jun 2001, Ann Parsons wrote:
>
> > Hi all,
> >
> > Here is the edited version of the gally proof.  Some significant
> > corrections were made in the past ten minutes.
> >
> >
> >
> > 			     SPEAKUP FAQ
> >
> > The document below is designed to answer the most frequently asked
> > questions about Speakup, the  screen reader/speech access system for
> > the Linux Operating System, used by people who are blind.  This
> > software is primarily developed and maintained by Kirk Reiser
> > (kirk@braille.uwo.ca).  It was developed initially by Kirk along with Andy
> > Berdan, with additional coding by John Covici and Brian Borowski.
> > Speakup was first announced on October 29, 1998 at:  08:55:28 -0500
> >      Most of the current development work is done by Kirk and Jim
> > Danley, along with contributions from other speakup users.
> >
> >
> >
> > q.  Why should I use Speakup?
> >
> > A.  If you are blind and want to use Linux as your operating system,
> > and if you want to know what is going on with your system from boot-up
> > to shut-down, then Speakup is for you.  Speakup gives you full access
> > to all console programs in the Linux OS.  It works particularly well
> > with telnet and with FTP.
> >
> >
> > q.  Where do I get speakup?
> >
> > A.  Speakup can be obtained by going to:  http://linux-speakup.org
> >
> >
> > q.  What kind of computer equipment do I need to run Speakup?
> >
> > A.  The Linux OS can be placed on any PC from a 386 on up.  One will
> > receive best results from using a 486 or better machine, however.
> >
> >
> > q.  What speech synthesizers are supported by Speakup.
> >
> > A.  At the moment, Speakup supports only hardware synthesizers.  Here
> > is a list of what is currently supported.
> >
> > Accent PC: acntpc
> > Accent SA: acntsa
> > Apolo: apolo
> > Audapter: audptr
> > Braille 'n Speak, and other such Blazie products: bns
> > DecTalk External (older model): decext
> > DecTalk PC (newer model): dectlk
> > DoubleTalk PC (internal): dtlk
> > LiteTalk/DoubleTalk LT (external): ltlk
> > Speakout: spkout
> > Transport: txprt
> > This list is current as of speakup version 0.10.
> >
> > Instructions on installation for each synthesizer can be found at the
> > URL listed above.
> >
> >
> > q.  Will Speakup work on a Windows system?
> >
> > A.  Although Speakup is a Linux Program and does not work in Windows,
> > there is a mini version of Linux plus speakup that can be run on a
> > dos/windows system.  It is called Zipspeak.  It was designed by
> > Matthew Campbell and can be obtained by going to:
> >
> > http://www.linux-speakup.org/zipspeak.html
> >
> > This is an excellent option if you are interested in Linux but do not
> > wish to devote much disk space, or resources to it.  It can be
> > expanded into a full Linux system should you wish to do so.
> >
> >
> > q.  I have heard about Emacspeak.  How does Speakup differ and which
> > is better, or do I need both?
> >
> > A.  Emacspeak, developed by T.V. Raman and currently in version 14, is
> > a verbal output system for Emacs, the customizable editor for
> > Unix/Linux.  It is a complete desktop system for the OS, and works
> > well with any console application that has been linked to it.
> > However, it has some significant drawbacks.  It does not work well
> > with Telnet or with FTP, and it does not give access to programs with
> > which it is not linked.
> >
> > However, there is a way to install both Speakup and Emacspeak on one's
> > system.  This allows full access to all console programs plus the
> > desktop environment of Emacs.
> >
> > Emacspeak can be downloaded from sourceforge via HTTP or FTP:
> >
> > http://emacspeak.sourceforge.net
> >
> > ftp://emacspeak.sourceforge.net/pub/emacspeak
> >
> > You can visit Emacspeak on the WWW at
> >
> > http://www.cs.cornell.edu/home/raman/emacspeak (Cornell) --You
> > can also pick up emacspeak via anonymous ftp from
> >
> > ftp://ftp.cs.cornell.edu/pub/raman/emacspeak/.
> >
> >
> > q. What versions of speakup work with what kernels?
> >
> > A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
> > and above.  For further information, ask on the speakup list.
> >
> >
> > q.  How do I install Speakup?
> >
> > A.  The easiest way is to download the appropriate precompiled kernel for your
> > synthesizer if the kernel is lower than 2.2.18 and install from the
> > downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> > likely that there is a generic patched kernel and you have to enter a string
> > to tell speakup what synthesizer you wish to use.  For example:
> >
> > speakup_synthesizer=dectlk speakup_serial=0
> >
> > The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> > Linux.
> >
> > Having obtained the appropriate kernel image that matches your distribution
> > and synthesizer, you can either create boot up disks with the dd command on
> > Unix type systems or rawrite under DOS or Windows, or by placing the
> > necessary files into a directory and using loadlin to start the installation
> > process.  For example: if the image is called bare.i, under Unix type system
> > you'd use the command string:
> >
> > dd . . . .(Sorry don't know the string)
> >
> > To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> > and bare.i are in the same directory as each other, say for example c:\Linux
> > you'd enter at a command prompt the following command strings:
> >
> > cd c:\Linux
> > [Press return]
> > rawrite bare.i a:
> > [Press return]
> >
> > Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> > before going into Windows.  You'd need to create a batch file to run
> > loadlin.exe with the appropriate parameters.
> >
> > Rawrite.exe and loadlin.exe can usually be found in a directory called
> > dosutils on distribution CD's, or something like that depending upon the
> > distribution.  They're often accompanied with detailed documentation.
> >
> >
> > Q.  What is the best way to download the appropriate file from the
> > site.
> >
> > A.  FTP is the quickest way to do this, although you can use the web
> > site's download facility.  One caveat, MSIE users be sure to type in
> > the address for the archive with ftp: in stead of http.  Some MSIE
> > users have trouble downloading the files because MSIE puts line-feeds
> > where they should not go.  If you do not have an FTP client, then try
> > using the Windows FTP client from a DOS box.  Be sure to type bin
> > before starting any transfer.
> >
> >
> > Q.  I've just used rawrite to make a boot disk for my system, and it
> > will not talk, it will not do anything.  Why?
> >
> > A.  Your speech synthesizer probably got in the way.  Before typing
> > the command again, turn off your speech program.
> >
> >
> > q. why doesn't speakup come up talking when I use bla bla bla distros
> > boot disk?
> >
> > A.  There are many reasons for this including:  a bad rawrite image,
> > the wrong comm port setting in the command line, an improperly
> > downloaded file.  For more specific information consult the
> > documentation file or ask on the Speakup list.
> >
> > q. what is the status of cursering?
> >
> > A.  The cursoring problem has been solved in part.  It is still in the
> > process of solution.
> >
> >
> > Q.  I hate documentation, and find it difficult to use because I do
> > not understand it.  How can I contact live human beings for help?
> >
> > A.  The simplest way to contact us is via our mailing list.  To
> > subscribe to this list, send an msg to:
> >
> > speakup-request@braille.uwo.ca
> >
> > In the body of the message, simply write subscribe.  when you have
> > done this, you will receive information on how to send directly to the
> > list.  Please keep this information for future reference.
> >
> > We can also be reached via Internet telephony by using the speakfreely
> > program.  this program can be downloaded at:
> >
> > http://www.formilab.ch/speakfree/unix
> >
> > When you have installed the program, access the reflector by entering
> > :
> >
> > lwl..braille.uwo.ca port 4074
> >
> > To see who is on the reflector, go to:
> >
> > http://lwl.braille.uwo.ca/speakup.html
> >
> >
> > 			    Ann K. Parsons
> >
> >
> >
> >
> >
> > --
> > 			Ann K. Parsons
> > email:  akp@eznet.net 			ICQ Number:  33006854
> > WEB SITE:  http://home.eznet.net/~akp
> > "All that is gold does not glitter.  Not all those who wander are lost."  JRRT
> >
> >
> > _______________________________________________
> > 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
>

Re: FAQ gally2: System Requirements

[Chris Nestrud]

That's a good point. I wonder what the lowest usable system is. Can't
you play mp3's with a P90? Anything that can run win95 and a
resource-intensive assistive technology package and still be usable
should be fine. <grin>

Chris


On Sun, Jun 17, 2001 at 12:56:44PM -0400, Janina Sajka wrote:
> Good suggestion, Chris. Should it be "newer Windows system?" I'm thinking
> there are still folks out  there with Win 3.11 and Win 95 on boxes with
> only megabytes of hd.
>  On Sun, 17 Jun 2001, Chris Nestrud wrote:
> 
> > You could mention that anything which runs Windows haf-way decently
> > should work well with linux. This is just meant to assure new users
> > that, if they're using their computer for Windows tasks, it's likely to
> > work well with linux.
> >
> > Chris
> >
> > On Sun, Jun 17, 2001 at 12:04:03PM -0400, Janina Sajka wrote:
> > > I don't think it's useful to leave the minimum system requirement as it
> > > is. While it is academically true that one can run linux with speakup on a
> > > 386 or 486 system, doing so is a little bit more dificult than our blithe
> > > comments suggest. It seems to me that most people here on out will use
> > > some of the canned installation distributions, Debian, Slack, Redhat,
> > > where speakup is already compiled in. How well do these support
> > > installations on older chips with only a few hundred megabytes of hard
> > > disk space? If they do that well--never mind this post. But, if not, let's
> > > not steer people wrong.
> > >
> > >
> > > Suggestion:
> > >
> > > Installation on older computers is not advised for people who've never
> > > installed linux before. It's just harder, much harder, to get it
> > > working. For
> > > best results, especially if you want to listen to Real Audio and mp3s,
> > > you should use a Pentium system with a hard disk that has several
> > > gigabytes of space.
> > >
> > >
> > >
> > > _______________________________________________
> > > 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

Re: FAQ gally2: The easiest way to install

[Kenny Hitt]

Hi, the installation part will probably need to list the command for
each Distribution.  Also, one thing not mention which is true for all
distributions is to make sure you install the Kernel from your boot
floppy.

          Kenny

On Sun, Jun 17, 2001 at 12:25:35PM -0400, Janina Sajka wrote:
> The part of the FAQ that describes the "easiest way" to get speakup is on
> the wrong track, but is quite incorrect.
> 
> Problem: People ;do not "download a kernel for their synthesizer." This is
> not how it is, but it is what's written currently.
> 
> Correction Suggestion:
> 
> Select the linux distribution you want to install and download the
> installation files for that distribution from the speakup web site. Do not
> download them from any source that doesn't explicitly say speakup, because
> you want to be sure and get the version that already has speakup included
> with it.
> 
> The second part is really about how to launch the installation once the
> distro is obtained and the floppies correctly created with rawrite or dd.
> The guidance given currently is essentially correct. But, it could be
> clearer. In particular, it should be made clear that the first prompt will
> not speak, and that people will need to type without speech to indicate
> what synth they have and where it is connected so that the program will
> know what synth to talk to and where to find it. This is what
> speakup_synth and speakup_ser mean, respectively.
>  On Sun, 17 Jun 2001, Ann
> Parsons wrote:
> 
> > A.  The easiest way is to download the appropriate precompiled kernel for your
> > synthesizer if the kernel is lower than 2.2.18 and install from the
> > downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> > likely that there is a generic patched kernel and you have to enter a string
> > to tell speakup what synthesizer you wish to use.  For example:
> >
> > speakup_synthesizer=dectlk speakup_serial=0
> >
> > The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> > Linux.
> >
> > Having obtained the appropriate kernel image that matches your distribution
> > and synthesizer, you can either create boot up disks with the dd command on
> > Unix type systems or rawrite under DOS or Windows, or by placing the
> > necessary files into a directory and using loadlin to start the installation
> > process.  For example: if the image is called bare.i, under Unix type system
> > you'd use the command string:
> >
> > dd . . . .(Sorry don't know the string)
> >
> > To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> > and bare.i are in the same directory as each other, say for example c:\Linux
> > you'd enter at a command prompt the following command strings:
> >
> > cd c:\Linux
> > [Press return]
> > rawrite bare.i a:
> > [Press return]
> >
> > Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> > before going into Windows.  You'd need to create a batch file to run
> > loadlin.exe with the appropriate parameters.
> >
> > Rawrite.exe and loadlin.exe can usually be found in a directory called
> > dosutils on distribution CD's, or something like that depending upon the
> > distribution.  They're often accompanied with detailed documentation.
> >
> >
> > Q.  What is the best way to download the appropriate file from the
> > site.
> >
> > A.  FTP is the quickest way to do this, although you can use the web
> > site's download facility.  One caveat, MSIE users be sure to type in
> > the address for the archive with ftp: in stead of http.  Some MSIE
> > users have trouble downloading the files because MSIE puts line-feeds
> > where they should not go.  If you do not have an FTP client, then try
> > using the Windows FTP client from a DOS box.  Be sure to type bin
> > before starting any transfer.
> >
> >
> > Q.  I've just used rawrite to make a boot disk for my system, and it
> > will not talk, it will not do anything.  Why?
> >
> > A.  Your speech synthesizer probably got in the way.  Before typing
> > the command again, turn off your speech program.
> >
> >
> > q. why doesn't speakup come up talking when I use bla bla bla distros
> > boot disk?
> >
> > A.  There are many reasons for this including:  a bad rawrite image,
> > the wrong comm port setting in the command line, an improperly
> > downloaded file.  For more specific information consult the
> > documentation file or ask on the Speakup list.
> >
> > q. what is the status of cursering?
> >
> > A.  The cursoring problem has been solved in part.  It is still in the
> > process of solution.
> >
> >
> > Q.  I hate documentation, and find it difficult to use because I do
> > not understand it.  How can I contact live human beings for help?
> >
> > A.  The simplest way to contact us is via our mailing list.  To
> > subscribe to this list, send an msg to:
> >
> > speakup-request@braille.uwo.ca
> >
> > In the body of the message, simply write subscribe.  when you have
> > done this, you will receive information on how to send directly to the
> > list.  Please keep this information for future reference.
> >
> > We can also be reached via Internet telephony by using the speakfreely
> > program.  this program can be downloaded at:
> >
> > http://www.formilab.ch/speakfree/unix
> >
> > When you have installed the program, access the reflector by entering
> > :
> >
> > lwl..braille.uwo.ca port 4074
> >
> > To see who is on the reflector, go to:
> >
> > http://lwl.braille.uwo.ca/speakup.html
> >
> >
> > 			    Ann K. Parsons
> >
> >
> >
> >
> >
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: The easiest way to install

[Buddy Brannan]

Hi,

Janina, you're mostly right, except that now Slackware (with upcoming
7.2) will apparently have a Speakup-enabled boot disk available right
from the CD. So that should be safe to use.

Also, I *think* speakup_ser boot parameter is being phased out, but I
had best not say for sure.
-- 
Buddy Brannan, KB5ELV    | History is made by stupid people.
Email: davros@ycardz.com | Clever people wouldn't even try.
Phone: (972) 276-6360    | If you want a place in the history books
ICQ: 36621210            | Then do something dumb before you die.

Re: FAQ gally2: The easiest way to install

[Janina Sajka]

Kenny:

Good first point.

The second point is wrong, though, I think. At least it's wrong for the
RedHat distros. If they're already cooked with speakup, and the RH iso
images that Bill Acker puts up are already cooked, then you don't need to
do this because speakup is already in the kernels that the install will
copy to the hd.
 On Sun, 17 Jun 2001, Kenny Hitt wrote:

> Hi, the installation part will probably need to list the command for
> each Distribution.  Also, one thing not mention which is true for all
> distributions is to make sure you install the Kernel from your boot
> floppy.
>
>           Kenny
>
> On Sun, Jun 17, 2001 at 12:25:35PM -0400, Janina Sajka wrote:
> > The part of the FAQ that describes the "easiest way" to get speakup is on
> > the wrong track, but is quite incorrect.
> >
> > Problem: People ;do not "download a kernel for their synthesizer." This is
> > not how it is, but it is what's written currently.
> >
> > Correction Suggestion:
> >
> > Select the linux distribution you want to install and download the
> > installation files for that distribution from the speakup web site. Do not
> > download them from any source that doesn't explicitly say speakup, because
> > you want to be sure and get the version that already has speakup included
> > with it.
> >
> > The second part is really about how to launch the installation once the
> > distro is obtained and the floppies correctly created with rawrite or dd.
> > The guidance given currently is essentially correct. But, it could be
> > clearer. In particular, it should be made clear that the first prompt will
> > not speak, and that people will need to type without speech to indicate
> > what synth they have and where it is connected so that the program will
> > know what synth to talk to and where to find it. This is what
> > speakup_synth and speakup_ser mean, respectively.
> >  On Sun, 17 Jun 2001, Ann
> > Parsons wrote:
> >
> > > A.  The easiest way is to download the appropriate precompiled kernel for your
> > > synthesizer if the kernel is lower than 2.2.18 and install from the
> > > downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> > > likely that there is a generic patched kernel and you have to enter a string
> > > to tell speakup what synthesizer you wish to use.  For example:
> > >
> > > speakup_synthesizer=dectlk speakup_serial=0
> > >
> > > The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> > > Linux.
> > >
> > > Having obtained the appropriate kernel image that matches your distribution
> > > and synthesizer, you can either create boot up disks with the dd command on
> > > Unix type systems or rawrite under DOS or Windows, or by placing the
> > > necessary files into a directory and using loadlin to start the installation
> > > process.  For example: if the image is called bare.i, under Unix type system
> > > you'd use the command string:
> > >
> > > dd . . . .(Sorry don't know the string)
> > >
> > > To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> > > and bare.i are in the same directory as each other, say for example c:\Linux
> > > you'd enter at a command prompt the following command strings:
> > >
> > > cd c:\Linux
> > > [Press return]
> > > rawrite bare.i a:
> > > [Press return]
> > >
> > > Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> > > before going into Windows.  You'd need to create a batch file to run
> > > loadlin.exe with the appropriate parameters.
> > >
> > > Rawrite.exe and loadlin.exe can usually be found in a directory called
> > > dosutils on distribution CD's, or something like that depending upon the
> > > distribution.  They're often accompanied with detailed documentation.
> > >
> > >
> > > Q.  What is the best way to download the appropriate file from the
> > > site.
> > >
> > > A.  FTP is the quickest way to do this, although you can use the web
> > > site's download facility.  One caveat, MSIE users be sure to type in
> > > the address for the archive with ftp: in stead of http.  Some MSIE
> > > users have trouble downloading the files because MSIE puts line-feeds
> > > where they should not go.  If you do not have an FTP client, then try
> > > using the Windows FTP client from a DOS box.  Be sure to type bin
> > > before starting any transfer.
> > >
> > >
> > > Q.  I've just used rawrite to make a boot disk for my system, and it
> > > will not talk, it will not do anything.  Why?
> > >
> > > A.  Your speech synthesizer probably got in the way.  Before typing
> > > the command again, turn off your speech program.
> > >
> > >
> > > q. why doesn't speakup come up talking when I use bla bla bla distros
> > > boot disk?
> > >
> > > A.  There are many reasons for this including:  a bad rawrite image,
> > > the wrong comm port setting in the command line, an improperly
> > > downloaded file.  For more specific information consult the
> > > documentation file or ask on the Speakup list.
> > >
> > > q. what is the status of cursering?
> > >
> > > A.  The cursoring problem has been solved in part.  It is still in the
> > > process of solution.
> > >
> > >
> > > Q.  I hate documentation, and find it difficult to use because I do
> > > not understand it.  How can I contact live human beings for help?
> > >
> > > A.  The simplest way to contact us is via our mailing list.  To
> > > subscribe to this list, send an msg to:
> > >
> > > speakup-request@braille.uwo.ca
> > >
> > > In the body of the message, simply write subscribe.  when you have
> > > done this, you will receive information on how to send directly to the
> > > list.  Please keep this information for future reference.
> > >
> > > We can also be reached via Internet telephony by using the speakfreely
> > > program.  this program can be downloaded at:
> > >
> > > http://www.formilab.ch/speakfree/unix
> > >
> > > When you have installed the program, access the reflector by entering
> > > :
> > >
> > > lwl..braille.uwo.ca port 4074
> > >
> > > To see who is on the reflector, go to:
> > >
> > > http://lwl.braille.uwo.ca/speakup.html
> > >
> > >
> > > 			    Ann K. Parsons
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > 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
>

Re: FAQ gally2

[Gregory Nowak]

Hi all,

Below are my suggestions for some corrections.
Greg


On Sun, Jun 17, 2001 at 10:09:58AM -0400, Ann Parsons wrote:
> Hi all,
> 
> Here is the edited version of the gally proof.  Some significant
> corrections were made in the past ten minutes.
> 
> 
> 
> 			     SPEAKUP FAQ
> 
> The document below is designed to answer the most frequently asked
> questions about Speakup, the  screen reader/speech access system for
> the Linux Operating System, used by people who are blind.  This
> software is primarily developed and maintained by Kirk Reiser
> (kirk@braille.uwo.ca).  It was developed initially by Kirk along with Andy
> Berdan, with additional coding by John Covici and Brian Borowski.
> Speakup was first announced on October 29, 1998 at:  08:55:28 -0500
>      Most of the current development work is done by Kirk and Jim
> Danley, along with contributions from other speakup users.
> 
> 
> 
> q.  Why should I use Speakup?
> 
> A.  If you are blind and want to use Linux as your operating system,
> and if you want to know what is going on with your system from boot-up
> to shut-down, then Speakup is for you.  Speakup gives you full access
> to all console programs in the Linux OS.  It works particularly well
> with telnet and with FTP. 
> 
> 
> q.  Where do I get speakup?
> 
> A.  Speakup can be obtained by going to:  http://linux-speakup.org
> 
> 
> q.  What kind of computer equipment do I need to run Speakup?
> 
> A.  The Linux OS can be placed on any PC from a 386 on up.  One will
> receive best results from using a 486 or better machine, however.  
> 
> 
> q.  What speech synthesizers are supported by Speakup.
> 
> A.  At the moment, Speakup supports only hardware synthesizers.  Here
> is a list of what is currently supported.
> 
> Accent PC: acntpc
> Accent SA: acntsa
> Apolo: apolo
> Audapter: audptr
> Braille 'n Speak, and other such Blazie products: bns
> DecTalk External (older model): decext
> DecTalk PC (newer model): dectlk
> DoubleTalk PC (internal): dtlk
> LiteTalk/DoubleTalk LT (external): ltlk
> Speakout: spkout
> Transport: txprt
> This list is current as of speakup version 0.10.
> 
> Instructions on installation for each synthesizer can be found at the
> URL listed above.
> 
>   
> q.  Will Speakup work on a Windows system?
> 
> A.  Although Speakup is a Linux Program and does not work in Windows,
> there is a mini version of Linux plus speakup that can be run on a
> dos/windows system.  It is called Zipspeak.  It was designed by
> Matthew Campbell and can be obtained by going to:  
> 
> http://www.linux-speakup.org/zipspeak.html
> 
> This is an excellent option if you are interested in Linux but do not
> wish to devote much disk space, or resources to it.  It can be
> expanded into a full Linux system should you wish to do so.
> 
> 
> q.  I have heard about Emacspeak.  How does Speakup differ and which
> is better, or do I need both?
> 
> A.  Emacspeak, developed by T.V. Raman and currently in version 14, is
> a verbal output system for Emacs, the customizable editor for
> Unix/Linux.  It is a complete desktop system for the OS, and works
> well with any console application that has been linked to it.
> However, it has some significant drawbacks.  It does not work well
> with Telnet or with FTP, and it does not give access to programs with
> which it is not linked.  
> 
> However, there is a way to install both Speakup and Emacspeak on one's
> system.  This allows full access to all console programs plus the
> desktop environment of Emacs.  
> 
> Emacspeak can be downloaded from sourceforge via HTTP or FTP:
> 
> http://emacspeak.sourceforge.net
> 
> ftp://emacspeak.sourceforge.net/pub/emacspeak 
> 
> You can visit Emacspeak on the WWW at
> 
> http://www.cs.cornell.edu/home/raman/emacspeak (Cornell) --You
> can also pick up emacspeak via anonymous ftp from
> 
> ftp://ftp.cs.cornell.edu/pub/raman/emacspeak/.
> 
> 
> q. What versions of speakup work with what kernels?
> 
> A.  The latest version of Speakup, 0.10A will work with kernels 2.2.18
> and above.  For further information, ask on the speakup list.  
> 
> 
> q.  How do I install Speakup?
> 
> A.  The easiest way is to download the appropriate precompiled kernel for your
> synthesizer if the kernel is lower than 2.2.18 and install from the
> downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> likely that there is a generic patched kernel and you have to enter a string
> to tell speakup what synthesizer you wish to use.  For example:
> 
> speakup_synthesizer=dectlk speakup_serial=0
> 
> The above string is for the Dectalk Express on Com 1 under DOS or ttyS0 under
> Linux.
> 
> Having obtained the appropriate kernel image that matches your distribution
> and synthesizer, you can either create boot up disks with the dd command on
> Unix type systems or rawrite under DOS or Windows, or by placing the
> necessary files into a directory and using loadlin to start the installation
> process.  For example: if the image is called bare.i, under a Unix type system
> you'd use the command string:
> 
> dd <bare.i> /dev/fd0 (for a disk in /dev/fd0 or a: under DOS).
> 
> To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> and bare.i are in the same directory as each other, say for example c:\Linux
> you'd enter at a command prompt the following command strings:
> 
> c:
> cd \Linux
> [Press return]
> rawrite bare.i a:
> [Press return]
> 
> Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> before going into Windows.  You'd need to create a batch file to run
> loadlin.exe with the appropriate parameters.
> 
> Rawrite.exe and loadlin.exe can usually be found in a directory called
> dosutils on distribution CD's, or something like that depending upon the
> distribution.  They're often accompanied with detailed documentation.
> 
> 
> Q.  What is the best way to download the appropriate file from the
> site.  
> 
> A.  FTP is the quickest way to do this, although you can use the web
> site's download facility.  One caveat, MSIE users be sure to type in
> the address for the archive with ftp: in stead of http.  Some MSIE
> users have trouble downloading the files because MSIE puts line-feeds
> where they should not go.  If you do not have an FTP client, then try
> using the Windows FTP client from a DOS box.  Be sure to type bin
> before starting any transfer.  
> 
> 
> Q.  I've just used rawrite to make a boot disk for my system, and it
> will not talk, it will not do anything.  Why?
> 
> A.  Your speech synthesizer probably got in the way.  Before typing
> the command again, turn off your speech program.  
> 
> 
> q. why doesn't speakup come up talking when I use bla bla bla distros
> boot disk?
> 
> A.  There are many reasons for this including:  a bad rawrite image,
> the wrong comm port setting in the command line, an improperly
> downloaded file.  For more specific information consult the
> documentation file or ask on the Speakup list.
> 
> q. what is the status of cursering?
> 
> A.  The cursoring problem has been solved in part.  It is still in the
> process of solution.
> 
> 
> Q.  I hate documentation, and find it difficult to use because I do
> not understand it.  How can I contact live human beings for help? 
> 
> A.  The simplest way to contact us is via our mailing list.  To
> subscribe to this list, send an msg to:
> 
> speakup-request@braille.uwo.ca
> 
> In the body of the message, simply write subscribe.  when you have
> done this, you will receive information on how to send directly to the
> list.  Please keep this information for future reference.  
> 
> We can also be reached via Internet telephony by using the speakfreely
> program.  this program can be downloaded at:
> 
> http://www.formilab.ch/speakfree/unix
> 
> When you have installed the program, access the reflector by entering
> :
> 
> lwl..braille.uwo.ca port 4074 
> 
> To see who is on the reflector, go to:
> 
> http://lwl.braille.uwo.ca/speakup.html
> 
> 
> 			    Ann K. Parsons
> 
> 
> 
> 
> 
> -- 
> 			Ann K. Parsons  
> email:  akp@eznet.net 			ICQ Number:  33006854
> WEB SITE:  http://home.eznet.net/~akp
> "All that is gold does not glitter.  Not all those who wander are lost."  JRRT
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: The easiest way to install

[Kenny Hitt]

Hi, for Debian 2.2, you are given a choice of sources for your Kernel.
Currently, if you don't install the Kernel from your boot floppy, you won't
have speech.  I saw the CD immage for Debian on the speakup web sight,
 but I didn't have a CD burner or enough disk space to use it.

          Kenny

On Sun, Jun 17, 2001 at 03:28:44PM -0400, Janina Sajka wrote:
> Kenny:
> 
> Good first point.
> 
> The second point is wrong, though, I think. At least it's wrong for the
> RedHat distros. If they're already cooked with speakup, and the RH iso
> images that Bill Acker puts up are already cooked, then you don't need to
> do this because speakup is already in the kernels that the install will
> copy to the hd.
>  On Sun, 17 Jun 2001, Kenny Hitt wrote:
> 
> > Hi, the installation part will probably need to list the command for
> > each Distribution.  Also, one thing not mention which is true for all
> > distributions is to make sure you install the Kernel from your boot
> > floppy.
> >
> >           Kenny
> >
> > On Sun, Jun 17, 2001 at 12:25:35PM -0400, Janina Sajka wrote:
> > > The part of the FAQ that describes the "easiest way" to get speakup is on
> > > the wrong track, but is quite incorrect.
> > >
> > > Problem: People ;do not "download a kernel for their synthesizer." This is
> > > not how it is, but it is what's written currently.
> > >
> > > Correction Suggestion:
> > >
> > > Select the linux distribution you want to install and download the
> > > installation files for that distribution from the speakup web site. Do not
> > > download them from any source that doesn't explicitly say speakup, because
> > > you want to be sure and get the version that already has speakup included
> > > with it.
> > >
> > > The second part is really about how to launch the installation once the
> > > distro is obtained and the floppies correctly created with rawrite or dd.
> > > The guidance given currently is essentially correct. But, it could be
> > > clearer. In particular, it should be made clear that the first prompt will
> > > not speak, and that people will need to type without speech to indicate
> > > what synth they have and where it is connected so that the program will
> > > know what synth to talk to and where to find it. This is what
> > > speakup_synth and speakup_ser mean, respectively.
> > >  On Sun, 17 Jun 2001, Ann
> > > Parsons wrote:
> > >
> > > > A.  The easiest way is to download the appropriate precompiled kernel for your
> > > > synthesizer if the kernel is lower than 2.2.18 and install from the
> > > > downloaded image.  If the distribution's kernel is higher than 2.2.18, it is
> > > > likely that there is a generic patched kernel and you have to enter a string
> > > > to tell speakup what synthesizer you wish to use.  For example:
> > > >
> > > > speakup_synthesizer=dectlk speakup_serial=0
> > > >
> > > > The above string is for the Dectalk Express on Com 1 under DOS or tty0 under
> > > > Linux.
> > > >
> > > > Having obtained the appropriate kernel image that matches your distribution
> > > > and synthesizer, you can either create boot up disks with the dd command on
> > > > Unix type systems or rawrite under DOS or Windows, or by placing the
> > > > necessary files into a directory and using loadlin to start the installation
> > > > process.  For example: if the image is called bare.i, under Unix type system
> > > > you'd use the command string:
> > > >
> > > > dd . . . .(Sorry don't know the string)
> > > >
> > > > To use rawrite.exe under DOS or Windows you'd write, providing rawrite.exe
> > > > and bare.i are in the same directory as each other, say for example c:\Linux
> > > > you'd enter at a command prompt the following command strings:
> > > >
> > > > cd c:\Linux
> > > > [Press return]
> > > > rawrite bare.i a:
> > > > [Press return]
> > > >
> > > > Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> > > > before going into Windows.  You'd need to create a batch file to run
> > > > loadlin.exe with the appropriate parameters.
> > > >
> > > > Rawrite.exe and loadlin.exe can usually be found in a directory called
> > > > dosutils on distribution CD's, or something like that depending upon the
> > > > distribution.  They're often accompanied with detailed documentation.
> > > >
> > > >
> > > > Q.  What is the best way to download the appropriate file from the
> > > > site.
> > > >
> > > > A.  FTP is the quickest way to do this, although you can use the web
> > > > site's download facility.  One caveat, MSIE users be sure to type in
> > > > the address for the archive with ftp: in stead of http.  Some MSIE
> > > > users have trouble downloading the files because MSIE puts line-feeds
> > > > where they should not go.  If you do not have an FTP client, then try
> > > > using the Windows FTP client from a DOS box.  Be sure to type bin
> > > > before starting any transfer.
> > > >
> > > >
> > > > Q.  I've just used rawrite to make a boot disk for my system, and it
> > > > will not talk, it will not do anything.  Why?
> > > >
> > > > A.  Your speech synthesizer probably got in the way.  Before typing
> > > > the command again, turn off your speech program.
> > > >
> > > >
> > > > q. why doesn't speakup come up talking when I use bla bla bla distros
> > > > boot disk?
> > > >
> > > > A.  There are many reasons for this including:  a bad rawrite image,
> > > > the wrong comm port setting in the command line, an improperly
> > > > downloaded file.  For more specific information consult the
> > > > documentation file or ask on the Speakup list.
> > > >
> > > > q. what is the status of cursering?
> > > >
> > > > A.  The cursoring problem has been solved in part.  It is still in the
> > > > process of solution.
> > > >
> > > >
> > > > Q.  I hate documentation, and find it difficult to use because I do
> > > > not understand it.  How can I contact live human beings for help?
> > > >
> > > > A.  The simplest way to contact us is via our mailing list.  To
> > > > subscribe to this list, send an msg to:
> > > >
> > > > speakup-request@braille.uwo.ca
> > > >
> > > > In the body of the message, simply write subscribe.  when you have
> > > > done this, you will receive information on how to send directly to the
> > > > list.  Please keep this information for future reference.
> > > >
> > > > We can also be reached via Internet telephony by using the speakfreely
> > > > program.  this program can be downloaded at:
> > > >
> > > > http://www.formilab.ch/speakfree/unix
> > > >
> > > > When you have installed the program, access the reflector by entering
> > > > :
> > > >
> > > > lwl..braille.uwo.ca port 4074
> > > >
> > > > To see who is on the reflector, go to:
> > > >
> > > > http://lwl.braille.uwo.ca/speakup.html
> > > >
> > > >
> > > > 			    Ann K. Parsons
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > 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

Re: FAQ gally2: What is linux?

[Kirk Reiser]

I think at this point I syhould point out that this should be listed
or refered to as gnus/linux to indicate the whole operating system
instead of just the kernel.  The kernel is Linux the entire system is
gnus/linux.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: FAQ gally2: Distro Prejudice

[Gregory Nowak]

If that's going to be changed,
then we should have examples
such as
if you use slackware, type this.
if you use redhat, do this etc.
If we're just going to give
incompatible command after command,
then people will get very confused.
Greg


On Sun, Jun 17, 2001 at 11:57:14AM -0400, Janina Sajka wrote:
> I expect we don't want to betray a bias toward one linux distribution over
> any other. In fact, I think the current faq does exactly that without
> meaning to. All the examples are slackware based.
> 
> The solution, imho, is to carefully insure that examples are given in such
> a way that the main distros are represented somewhere in the faq. I don't
> mean many examples, one for each distro, where examples are. I just mean
> that on the whole, there should be parity. Else, there's a subtle
> implication of favor.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: System Requirements

[Gregory Nowak]

Which windows?
A 486 runs win 3.x very decently.
Greg


On Sun, Jun 17, 2001 at 11:10:21AM -0500, Chris Nestrud wrote:
> You could mention that anything which runs Windows haf-way decently
> should work well with linux. This is just meant to assure new users
> that, if they're using their computer for Windows tasks, it's likely to
> work well with linux.
> 
> Chris
> 
> On Sun, Jun 17, 2001 at 12:04:03PM -0400, Janina Sajka wrote:
> > I don't think it's useful to leave the minimum system requirement as it
> > is. While it is academically true that one can run linux with speakup on a
> > 386 or 486 system, doing so is a little bit more dificult than our blithe
> > comments suggest. It seems to me that most people here on out will use
> > some of the canned installation distributions, Debian, Slack, Redhat,
> > where speakup is already compiled in. How well do these support
> > installations on older chips with only a few hundred megabytes of hard
> > disk space? If they do that well--never mind this post. But, if not, let's
> > not steer people wrong.
> > 
> > 
> > Suggestion:
> > 
> > Installation on older computers is not advised for people who've never
> > installed linux before. It's just harder, much harder, to get it
> > working. For
> > best results, especially if you want to listen to Real Audio and mp3s,
> > you should use a Pentium system with a hard disk that has several
> > gigabytes of space.
> > 
> > 
> > 
> > _______________________________________________
> > 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

Re: FAQ gally2: Miscellaneous

[Gregory Nowak]

I think that for a newby a once written 
batch file would be the ticket.
Greg


On Sun, Jun 17, 2001 at 12:52:48PM -0400, Janina Sajka wrote:
> A few minor points:
> 
> On Sun, 17 Jun 2001, Ann Parsons wrote:
> 
> > The document below is designed to answer the most frequently asked
> > questions about Speakup, the  screen reader/speech access system for
> > the Linux Operating System, used by people who are blind.
> I think we mean that speakup is used by people who are blind, not linux
> the operating system. In other words, linux isn't for blind people,
> speakup is.
> 
> > This
> > software is primarily developed and maintained by Kirk Reiser
> 
> What software? Linux? One could think that because it's the last software
> mentioned, so correct grammar suggests that "this" means linux, whereas we
> know it really means speakup. Better to just say "speakup."
> > Speakup gives you full access
> > to all console programs in the Linux OS.
> True, but many people, even people very good at using Windows, will not
> understand this because they've not encountered the concept of "consoles."
> Better to say "character based," or better still "text-based." Examples
> like pine and lynx would help illustrate the point.
> 
> > A.  At the moment, Speakup supports only hardware synthesizers.  Here
> > is a list of what is currently supported.
> >
> > Accent PC: acntpc
> > Accent SA: acntsa
> > Apolo: apolo
> > Audapter: audptr
> > Braille 'n Speak, and other such Blazie products: bns
> > DecTalk External (older model): decext
> > DecTalk PC (newer model): dectlk
> > DoubleTalk PC (internal): dtlk
> > LiteTalk/DoubleTalk LT (external): ltlk
> > Speakout: spkout
> > Transport: txprt
> > This list is current as of speakup version 0.10.
> 
> I suggest explaining why the keywords are here, something like:
> 
> "Notice the keyword abrieviation given above for your speech synthesizer.
> You will need to use it, so be sure to note its spelling and learn it
> now."
> 
> > Instructions on installation for each synthesizer can be found at the
> > URL listed above.
> >
> True, but why not give it again? If the reader is here, then a link here
> would be helpful.
> 
> > Loadlin.exe enables a Linux installation to be started from a DOS prompt,
> > before going into Windows.  You'd need to create a batch file to run
> > loadlin.exe with the appropriate parameters.
> 
> Why a batch file? Why not just type the command on the command line? Isn't
> it just a matter of passing the appropriate speakup_ser and speakup_synth
> plus appropriate image arguments?  I think it would make m0ore sense to
> prototype this then to get into talking about creating batch files.
> 
> > A.  There are many reasons for this including:  a bad rawrite image,
> > the wrong comm port setting in the command line, an improperly
> 
> Ooopps. "com port" is a Windows designation. Better to be neutral by
> saying "serial port."
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: What is linux?

[Gregory Nowak]

Isn't itgnu/linux?
Greg


On Sun, Jun 17, 2001 at 04:20:56PM -0400, Kirk Reiser wrote:
> I think at this point I syhould point out that this should be listed
> or refered to as gnus/linux to indicate the whole operating system
> instead of just the kernel.  The kernel is Linux the entire system is
> gnus/linux.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: FAQ gally2: What is linux?

[Janina Sajka]

The problem with getting clinically precise is that you introduce more
terms that must then be defined. Pretty soon, it ceases to be a friendly,
readable FAQ, and becomes a technical disertation. Isn't the intent on
this FAQ readability for newbies? Give 'em time to do first grade before
you send 'em to grad school!
 On Sun, 17 Jun 2001, Gregory Nowak wrote:

> Isn't itgnu/linux?
> Greg
>
>
> On Sun, Jun 17, 2001 at 04:20:56PM -0400, Kirk Reiser wrote:
> > I think at this point I syhould point out that this should be listed
> > or refered to as gnus/linux to indicate the whole operating system
> > instead of just the kernel.  The kernel is Linux the entire system is
> > gnus/linux.
> >
> >   Kirk
> >
> > --
> >
> > Kirk Reiser				The Computer Braille Facility
> > e-mail: kirk@braille.uwo.ca		University of Western Ontario
> > phone: (519) 661-3061
> >
> > _______________________________________________
> > 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
>

Re: FAQ gally2

[The Electronicman Scott Berry]

Ann,

I think instead of just having the unix speak freely listed maybe list 
the Windows one too in case people are having problems.

Re: FAQ gally2: System Requirements

[Geoff Shang]

On Sun, 17 Jun 2001, Chris Nestrud wrote:

> That's a good point. I wonder what the lowest usable system is. Can't
> you play mp3's with a P90? Anything that can run win95 and a
> resource-intensive assistive technology package and still be usable
> should be fine. <grin>

I think MPG123 can play 128kbps MP3 files on high-end 486's IIRC.

Geoff.

Re: FAQ gally2: The easiest way to install

[Geoff Shang]

On Sun, 17 Jun 2001, Buddy Brannan wrote:

> Also, I *think* speakup_ser boot parameter is being phased out, but I
> had best not say for sure.

Why would this be the case?  There is nothing that has obsoleted this
option.  It has always been and continues to be a backstop to deal with
synths that fail to auto-detect.

Geoff.

Re: FAQ gally2: Speakup Versions

[Geoff Shang]

On Sun, 17 Jun 2001, Janina Sajka wrote:

> I think the business of speakup versions needs to be a little clearer. We
> mention that the current version is 0.10. Then, a few paragraphs below, we
> mention version 0.10a. So, the chickens come home to roost on poorly
> chosen numbering schemes--but that's not what I want to talk about ...
>
> The poine in the faq needs to be clear guidance. Ann, this is really very
> excellent so far, but I think it's important to say something up front
> such as:
>
> "There are two current versions of speakup. Which one you should use
> depends on what linux kernel version you have. To find out, issue this
> command:

This is not correct.  I will address the FAQ as it now stands in a seperate
message, but I want to clarify this point.  Speakup 0.10A is a bug-fix
release of 0.10.  That is to say, Kirk fucked up and put it out before it
worked 100% so he had to rerelease it.  This also happened to speakup 0.09
(in fact, we got to speakup 0.09B IIRC).  suggestion for the future: Put
out speakup-0.11beta1 and if it works, rename it to speakup-0.11 or if not,
keep putting out betas until its fixed.  Or RC1, RC2, etc.

What this means is that speakup 0.10A works on 2.2.18 and above, and
2.4.0test10 (IIRC) and above.  for kernel 2.2.17 and below (well as far
down as 2.2.7 I think), use speakup 0.09.

Geoff.