another newbie

another newbie

[Ron Kassen]

Hello all,
Please bear with me as I ask some repeat questions.  First, let me tell you
where I am coming from:
I am a hardware and troubleshooting expert.  I am not trying to be
egotistical here, I have had fourteen years of computer experience, with
DOS, Windows 3.1, Windows95, Windows NT, some with Windows 2000, and diverse
PC based hardware experience.  I am a quick learner, and it is time to learn
again.  It has been a long time, I am rusty, and this is just what I needed
to kick me in the can and get me moving again.  Now for the questions:
I downloaded zipspeak and unzipped it to the \linux directory on my hard
drive (actually it created that folder itself).  After trying to fire it up
once and having it not find the partition, then realizing that I needed the
sda1 partition instead of the hda1 partition (I have scsi hard drives), I
loaded it successfully.  However, when I got to the login screen, typed root
and pressed enter, I did not know what to do next.  So, I did the
ctrl-alt-del to shut down the system (I don't know how to properly exit from
linux), rebooted into windows to go find the docs.  I think the docs are
actually where the zipspeak.txt says they are, but not in a format that
windows can read.  So how do I read the docs?
Second question:
I would like to convert from Windows to Linux because I am looking for a
more stable operating system that I do not have to reload every month (did
you know that Microsoft actually recommends a reformat every year with their
operating systems?)  However, I have some concerns.  I use the computer to
do my finances, serf the net, grab email, play wave and mp3 files, burn cd's
and more.  Are you using linux exclusively?  Am I going to have to keep
windows around to do stuff like burn cd's, do wave and mp3 files, etc?  I
know that I can serf the net and grab email with Linux, but what do I do
with all the emails that I have saved in a Microsoft outlook pst file?  How
do I edit the etc/rc.d/rc.modul file to tell linux what net card and sound
card I am using?  I know that I can read all the docs I want, but until I
actually start playing in Linux, I won't learn a thing.  I know to be
cautious - I can quickly destroy the data on the system.  Any
advice/help/etc would be appreciated.  Also, Linux is like another language
to me - I don't know it yet.  Be patient with me while I learn.  I know
there are some docs that I can get off the net, and I will go get them.
Thanks in advance!

RK

Re: another newbie

[Buddy Brannan]

Hi Ron,

First thing you'll want to do is create a user account. No, scratch
that. The first first thing you should do is change the root password with
passwd

After you've done that, *then* create a user account, from which you
should do most things. Doing everything as root is a bad
idea. (I.E. typing rm -rf * at the root directory is bad if you're
root.) You will create the user account with
adduser

Slackware's pretty nice in that it will step you through the account
creation, asking all the relevant questions.

Yes! You can do your CD burning, listen to MP3's and wavs, record wavs, do
Email, and surf the Web. (Remember...Linux was really *created* over the
Internet.) I'm not sure what Email program Zipspeak comes with--I'm
running the full Slackware distribution--but I use one called elm, and a
lot of folks use pine, while some swear by mutt. pico is a good basic text
editor. vi is the default in a lot of cases, but it's fairly arcane; if
you find yourself in vi, just type
:q!
and you'll get out of that.

Right. I don't know what to tell you about converting from Micro$haft
Lookout!, but you *can* do Email. Some pages don't work in lynx, and
you'll have to compile in SSL support--but you don' have to do that
immediately. Most things, however, work great with lynx, and I actually
prefer it for in-depth reading. About the only thing I use Windows for
these days is the odd OCR job and my online banking program, which runs in
Windows. Absolutely everything else I do in Linux.

I'm certainly not the most experienced person here, there are lots of
those on this list, but I'll certainly be glad to help if I can. Hope this
helps.


-- 
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 889-8147        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

RE: another newbie

[Ron Kassen]

Buddy,
I downloaded the bigslack version from the net.  Can I just unzip this into
the \linux directory, and with the linuz.spk kernel will it still load and
run ok as long as I have the bat file setup correctly?  Do I have to know
some cryptic language to tell this rc.modul file what hardware I have or is
it pretty straight forward?  How do I know how to tell linux, for example,
that I have a 3com 3c905b network card and an ensonic audio pci sound card?
Will it find and install my video card correctly?  Going back: When I get to
the login scree and type in root and press enter, am I in?  Then I can do
the passwd to change the root password and do the adduser to create my user
account?

Another note:
I tried to download the book off the net about linux installation and
getting started, but I have to download each page individually, and where I
found it compressed, it was a .tar.gz file, which I have to work with in
linux.  Any easier way to get these docs?
Thanks!!!

RK

-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Buddy Brannan
Sent: Sunday, April 02, 2000 9:25 AM
To: speakup@braille.uwo.ca
Subject: Re: another newbie


Hi Ron,

First thing you'll want to do is create a user account. No, scratch
that. The first first thing you should do is change the root password with
passwd

After you've done that, *then* create a user account, from which you
should do most things. Doing everything as root is a bad
idea. (I.E. typing rm -rf * at the root directory is bad if you're
root.) You will create the user account with
adduser

Slackware's pretty nice in that it will step you through the account
creation, asking all the relevant questions.

Yes! You can do your CD burning, listen to MP3's and wavs, record wavs, do
Email, and surf the Web. (Remember...Linux was really *created* over the
Internet.) I'm not sure what Email program Zipspeak comes with--I'm
running the full Slackware distribution--but I use one called elm, and a
lot of folks use pine, while some swear by mutt. pico is a good basic text
editor. vi is the default in a lot of cases, but it's fairly arcane; if
you find yourself in vi, just type
:q!
and you'll get out of that.

Right. I don't know what to tell you about converting from Micro$haft
Lookout!, but you *can* do Email. Some pages don't work in lynx, and
you'll have to compile in SSL support--but you don' have to do that
immediately. Most things, however, work great with lynx, and I actually
prefer it for in-depth reading. About the only thing I use Windows for
these days is the odd OCR job and my online banking program, which runs in
Windows. Absolutely everything else I do in Linux.

I'm certainly not the most experienced person here, there are lots of
those on this list, but I'll certainly be glad to help if I can. Hope this
helps.


--
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 889-8147        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

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

Re: another newbie

[Buddy Brannan]

Yeah, bigslack should work with the speakup kernel you got from zipspeak,
unless I am much mistaken.

rc.model: I'm not sure about that file, I haven't seen it. I'm afraid
someone else will have to tackle getting your hardware done. ... Actually,
it may take some doing; you'll probably either have to set up to load the
modules or re-compile your kernel with the network card installed. As for
the sound card, ... Hmm.....yeah, you'll need to put together a new kernel
anyway, as I don't think they have sound support turned on by
default. Matt, do you know for sure? If they do have the sound support,
you can probably use the ALSA drivers, which can be had at
www.alsa-project.org. Kirk or Gene can probably help with those, as I
don't have the latest version of them on my machine.

BTW, no, compiling a kernel is really not that hard. It looks a lot harder
than it is, but I suspect before you try that you might wanna use the
system a bit. :) 

As for the docs; a tar.gz is a fairly standard beastie in Linux. It's a
tar (a bit anachronistic in most cases I suppose, since tar stands for
tape archive, I think), which has been compressed with gzip. Under linux,
you can do
tar zxvf filename.tar.gz (it's case sensitive, and you have to type the
whole thing.) It will unzip into a bunch of files under a directory. I'm
not sure if you downloaded plain text, html, or something else though, but
I think that Winzip will handle tar.gz files...won't it?

-- 
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 889-8147        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

Re: another newbie

[Buddy Brannan]

Sorry, nearly forgot. Yes, you just do the passwd and adduser after you
type root. There is no root password initially, which is why Kirk couldn't
remember it. <Heh>


-- 
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 889-8147        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

RE: another newbie

[cpt.kirk]

Ron,

I will start off with answering some questions here:

When you are at the lodin screen and type in root, after pressing enter
you are prompted for the password. (If memory serves correct the default
password is a cariage return.) After entering the password correctly you
will be in.

For the book, download it in the compressed file. Winzip supports the
compression method. Just say yes to the first prompt about uncompressing
to a temp directory. If you are in linux use the command "tar -zxvf
filesname". (Of course replace filename with the appropriate filename.)

Kirk Wood
Cpt.Kirk@1tree.net
------------------

Your fly might be open (but don't check it just now).

RE: another newbie

[Geoff Shang]

Hi Ron:

If I were you, I'd recompile the kernel to get your hardware
supported.  Since you are a hardware expert, this shouldn't present any
major difficulties.  Grab a kernel source from the kernel 2.2 tree at
ftp.kernal.org, get the patch from
ftp.braille.uwo.ca/pub/linux/speakup/speakup-0.08.tar.gz and go for it.

Geoff.

RE: another newbie

[Ron Kassen]

Geoff,
Thanks for the encouragement.
This is my plan, but I have to learn a few things first:
1.  How do I tell the kernel that I have a 3com 3c905b 10/100mb ethernet
card?
2.  I know that alsa will give me the sound support I need and I know that
my sound card is supported, but I don't know if I have all the pieces I need
to get it up and running.
3.  There is a minor issue of Video, but for the moment, linux seems not to
care what my video card is.  I suppose it would be different if I was doing
graphics (not likely unless I think about running x-windows).
4.  How do I get the internet configured, and how do I start receiving
email?  It looks like there are many docs I need to read before I get
started, but I am somewhat impatient and want to start experimenting.
5.  I have no kernel compilation experience.  I downloaded what I think is a
kernel source from kerneli.org, but I'm afraid this is a new one for me - I
don't have a clue what I am looking at.  Do you know of a good kernel
compilation document?
6.  Where is a good place to find applications.  I downloaded mp123 (?) from
a site that I can't remember now.  Someone mentioned cdcd, where do I find
this?  Anyway, I won't ramble on like this - any help you could give would
be appreciated.
P.S.  I see your .au email address?  Are you from Australia?  What part?

Thanks a bunch!

RK
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Geoff Shang
Sent: Monday, April 03, 2000 12:55 AM
To: speakup@braille.uwo.ca
Subject: RE: another newbie


Hi Ron:

If I were you, I'd recompile the kernel to get your hardware
supported.  Since you are a hardware expert, this shouldn't present any
major difficulties.  Grab a kernel source from the kernel 2.2 tree at
ftp.kernal.org, get the patch from
ftp.braille.uwo.ca/pub/linux/speakup/speakup-0.08.tar.gz and go for it.

Geoff.



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

RE: another newbie

[Geoff Shang]

Hi Ron:

Questions are good.  Then we know what to tell you.

Lets tackle the kernel first.  You will want a kernel source from
kernel.org or somesuch place that looks something like
linux-2.2.14.tar.gz.  Don't get the 2.3 tree unless you're particularly
adventurous ... oh and if you don't want speakup to work <grin>.  Kernels
prior to 2.2.7 won't work with speakup either so unless 2.2.15 has come out
by the time you go to get it, it's best to get 2.2.14.  If you know how to
use bzip2 and have it installed, then you can get the bz2 file, otherwise
get the tar.gz file.  It will be aproximately 14 meg.  Untar it into your
/usr/src directory, such that it creates a /usr/src/linux directory.  You
will also need to grab speakup-0.08.tar.gz from
ftp.braille.uwo.ca/pub/linux/speakup so that you can patch it into your
kernel.

For reading matter, take a look at the README in the kernel source.  Also
take a poke around in the Documentation subdirectory, and if your
super-caucious like I was, you can even read the entire configure.help file
there too which lists all the help text for the kernel configuration
procedure.  It's a good read if you don't know what you must have.  There
is also a kernel howto on the linux documentation project
(www.linuxdoc.org) which you might also want to read.  Also check out the
hardware howto plus any others that pertain to your hardware.

Untar the speakup patch into /usr/src which will make a speakup-0.08
directory.  Then issue the command (from /usr/src):

patch -p0 <speakup-0.08/speakup-0.08-patch

All hunks except the MIPS one should take.  If you get more errors then, to
paraphrase Linus, either you or I have gotten something wrong.

Go into /usr/src/linux and type "make config".  Set aside some time to do
this, as you will be asked a plethora of questions.  You will be prompted
about network hardware and you should be able to find your card.  If you
plan to use the ALSA sound drivers (recommended in my opinion), say
"yes" to sound support but don't say "yes" to any other sound questions.

After you've answered all this, type the following:

make dep
make clean
make bzImage (note the capital I)
make modules
make modules_install

What you do next depends on the way your distribution does things and which
university you went to.  I personally type "make bzlilo" and am done with
it.  Others move the resultant image by hand.  Still others do other things
that I can't think of at present.  Perhaps other people using your
distribution can comment on this.

OK, you should be ready to reboot.  Hold your breath and type "restart".

I've gotta run so I'll answer the rest of your questions later unless
someone beats me to it.

Geoff.

Re: another newbie

[Scott Howell]

you forgot the most important command/action of them all. First go to your
windows box and type "format c:"
hahahahahahahahahah

3com network driver (was another newbie)

[cpt.kirk]

For the 3905b card that Ron had questioned about, Redhat 6.1 lists the
card as workable but not supported. They also gave a driver. But in
interest of giveing the best information I can, I went and found the
following site to get 3com network drivers for Linux. You can find drivers
for that card and several others at:
http://support.3com.com/infodeli/tools/nic/linuxdownloading.htm


Kirk Wood
Cpt.Kirk@1tree.net
------------------

Your fly might be open (but don't check it just now).

Re: 3com network driver (was another newbie)

[Mike Gorse]

I've got a 3c905 (not sure if it's a b or not), and the 3c59x driver in
the kernel works fine with it.


On Tue, 4 Apr 2000 cpt.kirk@1tree.net wrote:

> For the 3905b card that Ron had questioned about, Redhat 6.1 lists the
> card as workable but not supported. They also gave a driver. But in
> interest of giveing the best information I can, I went and found the
> following site to get 3com network drivers for Linux. You can find drivers
> for that card and several others at:
> http://support.3com.com/infodeli/tools/nic/linuxdownloading.htm
> 
> 
> Kirk Wood
> Cpt.Kirk@1tree.net
> ------------------
> 
> Your fly might be open (but don't check it just now).
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: another newbie

[Christopher Moore]

And, here's another reason to use Linux. If something goes wrong, you can
fix it w/o having to re-install everything.
Over the weekend, I had a bad library file which preventing me from
booting.  Well, I was able to restore it from my slakware distribution by
booting from floppy and mounting the "root" filesystem.  Try that with
winblows. <g>
Chris

w1gm@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

Triple Talk

[Janina Sajka]

Hi:

Does anyone have the contact info for the people building the Triple Talk
PCI and USB speech synths? It was posted here some months ago, and I
thought I kept the message, but now I can't find it.

Thanks.


				Janina Sajka, Director
				Information Systems Research & Development
				American Foundation for the Blind (AFB)

janina@afb.net

Re: another newbie

[cpt.kirk]

I remember seeing what the root password starts as, but can't help you
with that one. But I would not so much worry about destroying data. Linux
is actually less likely to let you wipe out the system or destroy data
then is Winblows. The thing is that if you spend your time in a
non-privledged account, you can't destroy any more then data local to that
account.

As for keeping Winblows, there are two things that I can think of for you
to do so. The first is OCR software (if you have it). I have not found
that in Linux yet. The other is if you have a need to use M$ Office or
similar programs for interchangability reasons. For those using X, that is
less an issue. But since your using speech, then I don't know of any
method of reading the screen inside X. (Though shell scripts can let you
use some X programs.)

As for the formatting every year, you are another victim of M$ outsourcing
program. Having been a contractor at a M$ facility I can assure you that
M$ does not endorse its support personel passing on a regular format
recomendation to its customers. The thing is that most of their support
comes from people who work with no direct M$ contact. Further, the average
tenure at said company is less then 6 months. And the first month is
spent in a class that blows over the top of 80% of the people's heads.
Such leads to people telling customer's that things such as a disk utility
(scandisk) can actually solve program errors (other then those dealing
with disk access).

Kirk Wood
Cpt.Kirk@1tree.net
------------------

Your fly might be open (but don't check it just now).

Re: another newbie

[William F. Acker WB2FLW +1-303-777-8123]

Hi Ron,

     I might be able to help with one of your questions.  Does outlook
Distress support connecting to an IMAP server.  If so, you could copy all
of your mail folders using Outlook to a directory on the IMAP server, and
copy them back to the Linux side using IMAP.  I know that pine supports
IMAP.  I imagine that there are other mail clients for Linux that do.

     I have a machine on the network which was put there for the express
purpose of having Speakup users and other friends play with it.  There's
an IMAP server on that machine.  If you're interested, just tell me what
you'd like your username to be.





          Hope this helps.
          Bill in Denver

Re: another newbie

[cpt.kirk]

Lookout excuse (outlook express) does support IMAP as does Outlook which
he is using. A more straight forward way is to use a converter tool. I am
pretty sure you can find a program on www.freshmeat.net that will import
mail in a pst file to your mailbox on the Linux machine.

Kirk Wood
Cpt.Kirk@1tree.net
------------------

Your fly might be open (but don't check it just now).

Re: another newbie

[Chuck Hallenbeck]

Another solution is to just 'forward' the mail in question from the
Windows software to your own address, then retrieve it with your Linux
software.

Chuck.
 On Sun, 2 Apr 2000 cpt.kirk@1tree.net wrote:

> Lookout excuse (outlook express) does support IMAP as does Outlook which
> he is using. A more straight forward way is to use a converter tool. I am
> pretty sure you can find a program on www.freshmeat.net that will import
> mail in a pst file to your mailbox on the Linux machine.
> 
> Kirk Wood
> Cpt.Kirk@1tree.net
> ------------------
> 
> Your fly might be open (but don't check it just now).
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

My web site is http://www.mhonline.net/~chuckh (I C Q = 67363342)
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759.

Re: another newbie

[William F. Acker WB2FLW +1-303-777-8123]

Hi Chuck,

     The only problem with forwarding the mail from Outlook and then
picking it up from Linux is that you would lose easy access to the date
and sender information.  It would still be contained within the file, but
not where the mailreader could display it without the user's opening it.




          73.
          Bill

RE: another newbie

[Ron Kassen]

I am far from there, but I will let you know if I am interested.  Thanks to
everyone for the notes.  They are useful.

RK

-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of William F. Acker
WB2FLW +1-303-777-8123
Sent: Sunday, April 02, 2000 5:56 PM
To: speakup@braille.uwo.ca
Subject: Re: another newbie


Hi Ron,

     I might be able to help with one of your questions.  Does outlook
Distress support connecting to an IMAP server.  If so, you could copy all
of your mail folders using Outlook to a directory on the IMAP server, and
copy them back to the Linux side using IMAP.  I know that pine supports
IMAP.  I imagine that there are other mail clients for Linux that do.

     I have a machine on the network which was put there for the express
purpose of having Speakup users and other friends play with it.  There's
an IMAP server on that machine.  If you're interested, just tell me what
you'd like your username to be.





          Hope this helps.
          Bill in Denver



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

Re: another newbie

[Geoff Shang]

Hi Ron - great to have you on-board.  If you're in to trouble-shooting
hardware probs then linux is for you.

The w;ay to close linux is by using the shutdown command.  Hopefully
zipspeak is set up so that control-alt-del invokes this.  The command is:

	shutdown -h now

to halt the system.  Use -r instead to reboot.

Geoff.

Re: another newbie

[Jacob Schmude]

What about the "halt" and "reboot" commands, they do the same thing.
On Mon, 3 Apr 2000, Geoff Shang wrote:

> Hi Ron - great to have you on-board.  If you're in to trouble-shooting
> hardware probs then linux is for you.
> 
> The w;ay to close linux is by using the shutdown command.  Hopefully
> zipspeak is set up so that control-alt-del invokes this.  The command is:
> 
> 	shutdown -h now
> 
> to halt the system.  Use -r instead to reboot.
> 
> Geoff.
> 
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Another newbie

[Jack Daniels]

Hi, I am new to Speakup, and I have been following the list for just a
short while now.  I want to learn whether the following is possible, and
how to best accomplish it.

First, some info about my Linux box.  I have a very small PC installed with
Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.  
A friend set it up for me and I am currently using a serial connection from
My Win98 PC.  

What I want to be able to do is to insert a floppy with Speakup and any
necessary boot files and have Linux  come up talking.  Is this possible? 
If so, what do I need to get/do?
I want to use a DEC Express on COM2, keeping the serial connection on COM1.   

If this is possible, and I thought it was from reading the list for just a
short time, what files do I need?
How do I use them?
Any info out there detailing this process?

I am sure there is info I have left out, so please ask any questions, and I
will answer them to the best of my ability.  Rememberr, I am new, never
built a kernal, the more detailed your response, the better.

Thank you in advance for helping another newbie get up and talking with
Speakup!

Jack

Re: Another newbie

[Thomas Ward]

Hi, my comments are below inside your message.I have tried to answer all
your questions as clearly as I can. I hope this helps.
See below.


----- Original Message -----
From: "Jack Daniels" <Labitup@home.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, November 22, 2001 11:30 AM
Subject: Another newbie


> Hi, I am new to Speakup, and I have been following the list for just a
> short while now.  I want to learn whether the following is possible, and
> how to best accomplish it.

That's great. I'll see what we can do for you.
>

> First, some info about my Linux box.  I have a very small PC installed
with
> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
> A friend set it up for me and I am currently using a serial connection
from
> My Win98 PC.
>
> What I want to be able to do is to insert a floppy with Speakup and any
> necessary boot files and have Linux  come up talking.  Is this possible?
> If so, what do I need to get/do?

Yes, it is possible, but someone would have to compile you a talking boot
disk image  of Speakup, for your kernel and send it too you.
Another suggestion is to get Emacspeak rpm, put it on a floppy, and install
it to your box. At least you would  have speech natively on your Linux box
until you were able to build a Speakup kernel for your machine.

> I want to use a DEC Express on COM2, keeping the serial connection on
COM1.
>

This is totally possible. Speakup [probes for your synths ports, and almost
always finds the synth on ttys0 and ttys1. which are com1 and com2 under
dos.



> If this is possible, and I thought it was from reading the list for just a
> short time, what files do I need?
> How do I use them?
> Any info out there detailing this process?
>

Unfortunately, I don't know of any specific documents that exactly gives you
a step by step howto on what to do, but most of us are old hands, or at
least know something about what we are doing.
Read the kernel howto, and the readme documentation in your kernel source
directory.
You basically, will need a clean kernel source tree, and the speakup source.
Also make sure you have kernel headers installed, compilers installed, and
are able to build kernels.

> I am sure there is info I have left out, so please ask any questions, and
I
> will answer them to the best of my ability.  Rememberr, I am new, never
> built a kernal, the more detailed your response, the better.

Ok, is it possible that you can get a cd rom drive for your computer? Bill
has Red Hat 7.2 cd's that come with Speakup built in. All you do is install
the cd's, restart, and wam you have speech.
I've been where you are now. Looking at a stock distribution, and wondering
how to get it to talk. Here is how I learned to do it if it is a stock
distribution and not a Speakup modified distribution.

I downloaded Emacspeak current version, and loaded my Dectalk Express. Then,
I accessed the shell by doing alt+x, and typed shell.
Once I had a talking shell, I then installed the Speakup source from floppy,
and put in the Linux cd, and installed the kernel source. Then, built a
talking kernel.
Since you don't have a cd rom drive you may have to substitute by first
configuring wvdial, and then while in Emacs with Emacspeak do an alt+x and
type term.
This puts Emacs in a terminal  mode, and you can run wvdial & to get your
internet connection.
Then, you can run the Linux ftp program to ftp files from the ftp.kernel.org
site to your box.

So here is the summary. While it is possible to do what you want it does
require some compiling, configuring,  and large learning curves. However,
once you do it a couple of times it won't seam so huge.
However, if you want a quick and simple solution see if you can get Bill's
modified Red Hat 7.2 disks from the Speakup ftp site, and install that. That
way you get speech out of the box, and can consentrate on learning the os
without plunging head-long into advanced compiling, configuring, and all
that.



>
> Thank you in advance for helping another newbie get up and talking with
> Speakup!
>
> Jack
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Another newbie

[Jack Daniels]

Thanks Tom. Unfortunately, no way to add a CDROM to this machine.  It's a
very small computer, (2.5X11.5X8.5) it has built-in everything, and room
for only a hard disk and a floppy.  I picked it up for $25 a while ago, and
thought it would make a neat Linux box.  Perhaps a parallel CD drive will
become a possibility for me down the road.

I already have the Speakup files on the system and will just go ahead and
begin reading the kernal info and start that learning curve now. If I run
into problems, I know where to come for help.  

Jack
At 11:32 PM 11/22/01 -0500, you wrote:
>Hi, my comments are below inside your message.I have tried to answer all
>your questions as clearly as I can. I hope this helps.
>See below.
>
>
>----- Original Message -----
>From: "Jack Daniels" <Labitup@home.com>
>To: <speakup@braille.uwo.ca>
>Sent: Thursday, November 22, 2001 11:30 AM
>Subject: Another newbie
>
>
>> Hi, I am new to Speakup, and I have been following the list for just a
>> short while now.  I want to learn whether the following is possible, and
>> how to best accomplish it.
>
>That's great. I'll see what we can do for you.
>>
>
>> First, some info about my Linux box.  I have a very small PC installed
>with
>> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>> A friend set it up for me and I am currently using a serial connection
>from
>> My Win98 PC.
>>
>> What I want to be able to do is to insert a floppy with Speakup and any
>> necessary boot files and have Linux  come up talking.  Is this possible?
>> If so, what do I need to get/do?
>
>Yes, it is possible, but someone would have to compile you a talking boot
>disk image  of Speakup, for your kernel and send it too you.
>Another suggestion is to get Emacspeak rpm, put it on a floppy, and install
>it to your box. At least you would  have speech natively on your Linux box
>until you were able to build a Speakup kernel for your machine.
>
>> I want to use a DEC Express on COM2, keeping the serial connection on
>COM1.
>>
>
>This is totally possible. Speakup [probes for your synths ports, and almost
>always finds the synth on ttys0 and ttys1. which are com1 and com2 under
>dos.
>
>
>
>> If this is possible, and I thought it was from reading the list for just a
>> short time, what files do I need?
>> How do I use them?
>> Any info out there detailing this process?
>>
>
>Unfortunately, I don't know of any specific documents that exactly gives you
>a step by step howto on what to do, but most of us are old hands, or at
>least know something about what we are doing.
>Read the kernel howto, and the readme documentation in your kernel source
>directory.
>You basically, will need a clean kernel source tree, and the speakup source.
>Also make sure you have kernel headers installed, compilers installed, and
>are able to build kernels.
>
>> I am sure there is info I have left out, so please ask any questions, and
>I
>> will answer them to the best of my ability.  Rememberr, I am new, never
>> built a kernal, the more detailed your response, the better.
>
>Ok, is it possible that you can get a cd rom drive for your computer? Bill
>has Red Hat 7.2 cd's that come with Speakup built in. All you do is install
>the cd's, restart, and wam you have speech.
>I've been where you are now. Looking at a stock distribution, and wondering
>how to get it to talk. Here is how I learned to do it if it is a stock
>distribution and not a Speakup modified distribution.
>
>I downloaded Emacspeak current version, and loaded my Dectalk Express. Then,
>I accessed the shell by doing alt+x, and typed shell.
>Once I had a talking shell, I then installed the Speakup source from floppy,
>and put in the Linux cd, and installed the kernel source. Then, built a
>talking kernel.
>Since you don't have a cd rom drive you may have to substitute by first
>configuring wvdial, and then while in Emacs with Emacspeak do an alt+x and
>type term.
>This puts Emacs in a terminal  mode, and you can run wvdial & to get your
>internet connection.
>Then, you can run the Linux ftp program to ftp files from the ftp.kernel.org
>site to your box.
>
>So here is the summary. While it is possible to do what you want it does
>require some compiling, configuring,  and large learning curves. However,
>once you do it a couple of times it won't seam so huge.
>However, if you want a quick and simple solution see if you can get Bill's
>modified Red Hat 7.2 disks from the Speakup ftp site, and install that. That
>way you get speech out of the box, and can consentrate on learning the os
>without plunging head-long into advanced compiling, configuring, and all
>that.
>
>
>
>>
>> Thank you in advance for helping another newbie get up and talking with
>> Speakup!
>>
>> Jack
>>
>>
>> _______________________________________________
>> 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: Another newbie

[Janina Sajka]

On Sat, 24 Nov 2001, Jack Daniels wrote:

> >> I have a very small PC installed with
> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
> >> What I want to be able to do is to insert a floppy with Speakup and any
> >> necessary boot files and have Linux  come up talking.  Is this possible?

It seems to me you could get this working with the standard installation 
floppy that one would create using boot.img. There are such on the speakup 
website and they already have speakup built into them. You need two files 
from the speakup site to test this: the appropriate boot.img and 
rawrite.exe.

1.)	rawrite.exe is a DOS executable for creating floppy disks from 
image files like boot.img. Shutdown your Windows to MS-DOS before using 
rawrite for best, most reliable results;

2.) Get boot.img via anonymous ftp from:
	www.linux-speakup.org/pub/speakup/disks/redhat/7.2

Regretably, the rawrite.exe isn't there, and perhaps that's an oversight. 
Bill, are you listening? If you decide to try my suggestion, perhaps 
someone can point you to a download location closer to home, but you can 
certainly get it from redhat.com. It'll be in a dos_utils directory. There 
should be no problem using 7.2 disks on your 7.1 system, by the way;

3.)	You need to be careful about your speech synthesizer while using 
rawrite. Generally, it's a good idea to kill speech while rawrite is 
creating your floppy. So, as you hit enter on the last rawrite prompt, 
which is the third prompt it gives you, be ready to kill your speech 
immediately;

54.)	If nothing went wrong in the rawrite floppy you'll have a bootable 
floppy that you can try on your linux system. As you boot, monitor the 
floppy disk for activity. If your system beeps as it begins to load the 
OS, that will help. There will be a brief amount of floppy disk activity 
at this point and then the disk stops. You're at a boot> prompt which 
doesn't talk (though it could, see below); At this point type:

	linux -s speakup_synth=dectlk speakup_ser=1

I believe that even with the mismatch in installation versions this should 
still come up talking. If it does, you can certainly look around natively, 
and you can begin to contemplate getting a native kernel with speakup onto 
your system. But, that's a topic for another day.

Certainly, there will be a good number of things that won't work because 
of the kernel mismatches. But, you should have enough to get started with.

PS: The boot> prompt can be made to speak to any serial device with an 
appropriate lin in the sysconfig file on the floppy:

serial=1,9600N8
	
would be the appropriate lin in this instance, and you could certainly 
insert this line using a DOS text editor. It goes just above the first 
"label" statement.

RE: Another newbie

[Georgina]

Hi

Use rawWrite for Windows, its a lot easier for Windows screen reader users
and I haven't heard of a failure yet.

Isn't it:

text speakup_synth......and not linux?


-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 24 November 2001 16:02
To: speakup@braille.uwo.ca
Subject: Re: Another newbie


On Sat, 24 Nov 2001, Jack Daniels wrote:

> >> I have a very small PC installed with
> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
> >> What I want to be able to do is to insert a floppy with Speakup and any
> >> necessary boot files and have Linux  come up talking.  Is this
possible?

It seems to me you could get this working with the standard installation
floppy that one would create using boot.img. There are such on the speakup
website and they already have speakup built into them. You need two files
from the speakup site to test this: the appropriate boot.img and
rawrite.exe.

1.)	rawrite.exe is a DOS executable for creating floppy disks from
image files like boot.img. Shutdown your Windows to MS-DOS before using
rawrite for best, most reliable results;

2.) Get boot.img via anonymous ftp from:
	www.linux-speakup.org/pub/speakup/disks/redhat/7.2

Regretably, the rawrite.exe isn't there, and perhaps that's an oversight.
Bill, are you listening? If you decide to try my suggestion, perhaps
someone can point you to a download location closer to home, but you can
certainly get it from redhat.com. It'll be in a dos_utils directory. There
should be no problem using 7.2 disks on your 7.1 system, by the way;

3.)	You need to be careful about your speech synthesizer while using
rawrite. Generally, it's a good idea to kill speech while rawrite is
creating your floppy. So, as you hit enter on the last rawrite prompt,
which is the third prompt it gives you, be ready to kill your speech
immediately;

54.)	If nothing went wrong in the rawrite floppy you'll have a bootable
floppy that you can try on your linux system. As you boot, monitor the
floppy disk for activity. If your system beeps as it begins to load the
OS, that will help. There will be a brief amount of floppy disk activity
at this point and then the disk stops. You're at a boot> prompt which
doesn't talk (though it could, see below); At this point type:

	linux -s speakup_synth=dectlk speakup_ser=1

I believe that even with the mismatch in installation versions this should
still come up talking. If it does, you can certainly look around natively,
and you can begin to contemplate getting a native kernel with speakup onto
your system. But, that's a topic for another day.

Certainly, there will be a good number of things that won't work because
of the kernel mismatches. But, you should have enough to get started with.

PS: The boot> prompt can be made to speak to any serial device with an
appropriate lin in the sysconfig file on the floppy:

serial=1,9600N8

would be the appropriate lin in this instance, and you could certainly
insert this line using a DOS text editor. It goes just above the first
"label" statement.



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

Re: Another newbie

[Jack Daniels]

Thanks Janina, I have saved the info, but think I will read up more on
Linux patching and kernal compiling, and hope learn enough to feel
confident to compile my first kernal, and  add Speakup so it can be
selected and booted from the hard disk.  I was looking for a quick and easy
way to get Speakup talking, and then read more later.

I guess I will need to put in the effort up front, and learn about this
topic and work it out. It was suggested that I first try compiling a kernal
to make sure everything works correctly, then try it with Speakup after
that.   

BTW, what happens if Speakup doesn't find a synthesizer connected when it
tries to load?  I may not have the DEC Express connected each and every time.

Thanks for your reply.

Jack
At 11:01 AM 11/24/01 -0500, you wrote:
>On Sat, 24 Nov 2001, Jack Daniels wrote:
>
>> >> I have a very small PC installed with
>> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>> >> What I want to be able to do is to insert a floppy with Speakup and any
>> >> necessary boot files and have Linux  come up talking.  Is this possible?
>
>It seems to me you could get this working with the standard installation 
>floppy that one would create using boot.img. There are such on the speakup 
>website and they already have speakup built into them. You need two files 
>from the speakup site to test this: the appropriate boot.img and 
>rawrite.exe.
>
>1.)	rawrite.exe is a DOS executable for creating floppy disks from 
>image files like boot.img. Shutdown your Windows to MS-DOS before using 
>rawrite for best, most reliable results;
>
>2.) Get boot.img via anonymous ftp from:
>	www.linux-speakup.org/pub/speakup/disks/redhat/7.2
>
>Regretably, the rawrite.exe isn't there, and perhaps that's an oversight. 
>Bill, are you listening? If you decide to try my suggestion, perhaps 
>someone can point you to a download location closer to home, but you can 
>certainly get it from redhat.com. It'll be in a dos_utils directory. There 
>should be no problem using 7.2 disks on your 7.1 system, by the way;
>
>3.)	You need to be careful about your speech synthesizer while using 
>rawrite. Generally, it's a good idea to kill speech while rawrite is 
>creating your floppy. So, as you hit enter on the last rawrite prompt, 
>which is the third prompt it gives you, be ready to kill your speech 
>immediately;
>
>54.)	If nothing went wrong in the rawrite floppy you'll have a bootable 
>floppy that you can try on your linux system. As you boot, monitor the 
>floppy disk for activity. If your system beeps as it begins to load the 
>OS, that will help. There will be a brief amount of floppy disk activity 
>at this point and then the disk stops. You're at a boot> prompt which 
>doesn't talk (though it could, see below); At this point type:
>
>	linux -s speakup_synth=dectlk speakup_ser=1
>
>I believe that even with the mismatch in installation versions this should 
>still come up talking. If it does, you can certainly look around natively, 
>and you can begin to contemplate getting a native kernel with speakup onto 
>your system. But, that's a topic for another day.
>
>Certainly, there will be a good number of things that won't work because 
>of the kernel mismatches. But, you should have enough to get started with.
>
>PS: The boot> prompt can be made to speak to any serial device with an 
>appropriate lin in the sysconfig file on the floppy:
>
>serial=1,9600N8
>	
>would be the appropriate lin in this instance, and you could certainly 
>insert this line using a DOS text editor. It goes just above the first 
>"label" statement.
>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: Another newbie

[Gregory Nowak]

All that will happen will be that you'll have no speech.
Greg


On Sat, Nov 24, 2001 at 06:10:29PM -0500, Jack Daniels wrote:
> Thanks Janina, I have saved the info, but think I will read up more on
> Linux patching and kernal compiling, and hope learn enough to feel
> confident to compile my first kernal, and  add Speakup so it can be
> selected and booted from the hard disk.  I was looking for a quick and easy
> way to get Speakup talking, and then read more later.
> 
> I guess I will need to put in the effort up front, and learn about this
> topic and work it out. It was suggested that I first try compiling a kernal
> to make sure everything works correctly, then try it with Speakup after
> that.   
> 
> BTW, what happens if Speakup doesn't find a synthesizer connected when it
> tries to load?  I may not have the DEC Express connected each and every time.
> 
> Thanks for your reply.
> 
> Jack
> At 11:01 AM 11/24/01 -0500, you wrote:
> >On Sat, 24 Nov 2001, Jack Daniels wrote:
> >
> >> >> I have a very small PC installed with
> >> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
> >> >> What I want to be able to do is to insert a floppy with Speakup and any
> >> >> necessary boot files and have Linux  come up talking.  Is this possible?
> >
> >It seems to me you could get this working with the standard installation 
> >floppy that one would create using boot.img. There are such on the speakup 
> >website and they already have speakup built into them. You need two files 
> >from the speakup site to test this: the appropriate boot.img and 
> >rawrite.exe.
> >
> >1.)	rawrite.exe is a DOS executable for creating floppy disks from 
> >image files like boot.img. Shutdown your Windows to MS-DOS before using 
> >rawrite for best, most reliable results;
> >
> >2.) Get boot.img via anonymous ftp from:
> >	www.linux-speakup.org/pub/speakup/disks/redhat/7.2
> >
> >Regretably, the rawrite.exe isn't there, and perhaps that's an oversight. 
> >Bill, are you listening? If you decide to try my suggestion, perhaps 
> >someone can point you to a download location closer to home, but you can 
> >certainly get it from redhat.com. It'll be in a dos_utils directory. There 
> >should be no problem using 7.2 disks on your 7.1 system, by the way;
> >
> >3.)	You need to be careful about your speech synthesizer while using 
> >rawrite. Generally, it's a good idea to kill speech while rawrite is 
> >creating your floppy. So, as you hit enter on the last rawrite prompt, 
> >which is the third prompt it gives you, be ready to kill your speech 
> >immediately;
> >
> >54.)	If nothing went wrong in the rawrite floppy you'll have a bootable 
> >floppy that you can try on your linux system. As you boot, monitor the 
> >floppy disk for activity. If your system beeps as it begins to load the 
> >OS, that will help. There will be a brief amount of floppy disk activity 
> >at this point and then the disk stops. You're at a boot> prompt which 
> >doesn't talk (though it could, see below); At this point type:
> >
> >	linux -s speakup_synth=dectlk speakup_ser=1
> >
> >I believe that even with the mismatch in installation versions this should 
> >still come up talking. If it does, you can certainly look around natively, 
> >and you can begin to contemplate getting a native kernel with speakup onto 
> >your system. But, that's a topic for another day.
> >
> >Certainly, there will be a good number of things that won't work because 
> >of the kernel mismatches. But, you should have enough to get started with.
> >
> >PS: The boot> prompt can be made to speak to any serial device with an 
> >appropriate lin in the sysconfig file on the floppy:
> >
> >serial=1,9600N8
> >	
> >would be the appropriate lin in this instance, and you could certainly 
> >insert this line using a DOS text editor. It goes just above the first 
> >"label" statement.
> >
> >
> >
> >_______________________________________________
> >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: Another newbie

[Jack Daniels]

Thanks Greg.

Jack

At 05:44 PM 11/24/01 -0600, you wrote:
>All that will happen will be that you'll have no speech.
>Greg
>
>
>On Sat, Nov 24, 2001 at 06:10:29PM -0500, Jack Daniels wrote:
>> Thanks Janina, I have saved the info, but think I will read up more on
>> Linux patching and kernal compiling, and hope learn enough to feel
>> confident to compile my first kernal, and  add Speakup so it can be
>> selected and booted from the hard disk.  I was looking for a quick and easy
>> way to get Speakup talking, and then read more later.
>> 
>> I guess I will need to put in the effort up front, and learn about this
>> topic and work it out. It was suggested that I first try compiling a kernal
>> to make sure everything works correctly, then try it with Speakup after
>> that.   
>> 
>> BTW, what happens if Speakup doesn't find a synthesizer connected when it
>> tries to load?  I may not have the DEC Express connected each and every
time.
>> 
>> Thanks for your reply.
>> 
>> Jack
>> At 11:01 AM 11/24/01 -0500, you wrote:
>> >On Sat, 24 Nov 2001, Jack Daniels wrote:
>> >
>> >> >> I have a very small PC installed with
>> >> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>> >> >> What I want to be able to do is to insert a floppy with Speakup
and any
>> >> >> necessary boot files and have Linux  come up talking.  Is this
possible?
>> >
>> >It seems to me you could get this working with the standard installation 
>> >floppy that one would create using boot.img. There are such on the
speakup 
>> >website and they already have speakup built into them. You need two files 
>> >from the speakup site to test this: the appropriate boot.img and 
>> >rawrite.exe.
>> >
>> >1.)	rawrite.exe is a DOS executable for creating floppy disks from 
>> >image files like boot.img. Shutdown your Windows to MS-DOS before using 
>> >rawrite for best, most reliable results;
>> >
>> >2.) Get boot.img via anonymous ftp from:
>> >	www.linux-speakup.org/pub/speakup/disks/redhat/7.2
>> >
>> >Regretably, the rawrite.exe isn't there, and perhaps that's an oversight. 
>> >Bill, are you listening? If you decide to try my suggestion, perhaps 
>> >someone can point you to a download location closer to home, but you can 
>> >certainly get it from redhat.com. It'll be in a dos_utils directory.
There 
>> >should be no problem using 7.2 disks on your 7.1 system, by the way;
>> >
>> >3.)	You need to be careful about your speech synthesizer while using 
>> >rawrite. Generally, it's a good idea to kill speech while rawrite is 
>> >creating your floppy. So, as you hit enter on the last rawrite prompt, 
>> >which is the third prompt it gives you, be ready to kill your speech 
>> >immediately;
>> >
>> >54.)	If nothing went wrong in the rawrite floppy you'll have a bootable 
>> >floppy that you can try on your linux system. As you boot, monitor the 
>> >floppy disk for activity. If your system beeps as it begins to load the 
>> >OS, that will help. There will be a brief amount of floppy disk activity 
>> >at this point and then the disk stops. You're at a boot> prompt which 
>> >doesn't talk (though it could, see below); At this point type:
>> >
>> >	linux -s speakup_synth=dectlk speakup_ser=1
>> >
>> >I believe that even with the mismatch in installation versions this
should 
>> >still come up talking. If it does, you can certainly look around
natively, 
>> >and you can begin to contemplate getting a native kernel with speakup
onto 
>> >your system. But, that's a topic for another day.
>> >
>> >Certainly, there will be a good number of things that won't work because 
>> >of the kernel mismatches. But, you should have enough to get started with.
>> >
>> >PS: The boot> prompt can be made to speak to any serial device with an 
>> >appropriate lin in the sysconfig file on the floppy:
>> >
>> >serial=1,9600N8
>> >	
>> >would be the appropriate lin in this instance, and you could certainly 
>> >insert this line using a DOS text editor. It goes just above the first 
>> >"label" statement.
>> >
>> >
>> >
>> >_______________________________________________
>> >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: Another newbie

[Georgina]

Hi

No I think your original approach is right.  Get a custom installation up
and going then play about with compiling a kernel.  There's no significant
difference in compiling a kernel with or without Speakup.  Its just applying
a patch and then as a result the config process asks you about 14 extra
questions such as do you want speakup and if so, one by one which synths do
you want?  Its the compiling process that is time consuming and demanding.

But if any Linux user is honest, they'll admit that its a steep learning
curve. I'd suggest that you should make your learning in as small pieces as
possible, that way you'll enjoy it and learn a lot quicker.

-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Jack Daniels
Sent: 24 November 2001 23:10
To: speakup@braille.uwo.ca
Subject: Re: Another newbie


Thanks Janina, I have saved the info, but think I will read up more on
Linux patching and kernal compiling, and hope learn enough to feel
confident to compile my first kernal, and  add Speakup so it can be
selected and booted from the hard disk.  I was looking for a quick and easy
way to get Speakup talking, and then read more later.

I guess I will need to put in the effort up front, and learn about this
topic and work it out. It was suggested that I first try compiling a kernal
to make sure everything works correctly, then try it with Speakup after
that.

BTW, what happens if Speakup doesn't find a synthesizer connected when it
tries to load?  I may not have the DEC Express connected each and every
time.

Thanks for your reply.

Jack
At 11:01 AM 11/24/01 -0500, you wrote:
>On Sat, 24 Nov 2001, Jack Daniels wrote:
>
>> >> I have a very small PC installed with
>> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>> >> What I want to be able to do is to insert a floppy with Speakup and
any
>> >> necessary boot files and have Linux  come up talking.  Is this
possible?
>
>It seems to me you could get this working with the standard installation
>floppy that one would create using boot.img. There are such on the speakup
>website and they already have speakup built into them. You need two files
>from the speakup site to test this: the appropriate boot.img and
>rawrite.exe.
>
>1.)	rawrite.exe is a DOS executable for creating floppy disks from
>image files like boot.img. Shutdown your Windows to MS-DOS before using
>rawrite for best, most reliable results;
>
>2.) Get boot.img via anonymous ftp from:
>	www.linux-speakup.org/pub/speakup/disks/redhat/7.2
>
>Regretably, the rawrite.exe isn't there, and perhaps that's an oversight.
>Bill, are you listening? If you decide to try my suggestion, perhaps
>someone can point you to a download location closer to home, but you can
>certainly get it from redhat.com. It'll be in a dos_utils directory. There
>should be no problem using 7.2 disks on your 7.1 system, by the way;
>
>3.)	You need to be careful about your speech synthesizer while using
>rawrite. Generally, it's a good idea to kill speech while rawrite is
>creating your floppy. So, as you hit enter on the last rawrite prompt,
>which is the third prompt it gives you, be ready to kill your speech
>immediately;
>
>54.)	If nothing went wrong in the rawrite floppy you'll have a bootable
>floppy that you can try on your linux system. As you boot, monitor the
>floppy disk for activity. If your system beeps as it begins to load the
>OS, that will help. There will be a brief amount of floppy disk activity
>at this point and then the disk stops. You're at a boot> prompt which
>doesn't talk (though it could, see below); At this point type:
>
>	linux -s speakup_synth=dectlk speakup_ser=1
>
>I believe that even with the mismatch in installation versions this should
>still come up talking. If it does, you can certainly look around natively,
>and you can begin to contemplate getting a native kernel with speakup onto
>your system. But, that's a topic for another day.
>
>Certainly, there will be a good number of things that won't work because
>of the kernel mismatches. But, you should have enough to get started with.
>
>PS: The boot> prompt can be made to speak to any serial device with an
>appropriate lin in the sysconfig file on the floppy:
>
>serial=1,9600N8
>
>would be the appropriate lin in this instance, and you could certainly
>insert this line using a DOS text editor. It goes just above the first
>"label" statement.
>
>
>
>_______________________________________________
>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: Another newbie

[Jack Daniels]

Thanks Gena. The reason for suggesting I compile a kernal without Speakup
was to go through the process, to see whether everything went smoothly.
That way, it would be easier to do it again a second time.  I will  start
reading more, then see where I am. I have saved the earlier info, thanks.

Jack

At 02:29 AM 11/25/01 +0000, you wrote:
>Hi
>
>No I think your original approach is right.  Get a custom installation up
>and going then play about with compiling a kernel.  There's no significant
>difference in compiling a kernel with or without Speakup.  Its just applying
>a patch and then as a result the config process asks you about 14 extra
>questions such as do you want speakup and if so, one by one which synths do
>you want?  Its the compiling process that is time consuming and demanding.
>
>But if any Linux user is honest, they'll admit that its a steep learning
>curve. I'd suggest that you should make your learning in as small pieces as
>possible, that way you'll enjoy it and learn a lot quicker.
>
>-----Original Message-----
>From: speakup-admin@braille.uwo.ca
>[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Jack Daniels
>Sent: 24 November 2001 23:10
>To: speakup@braille.uwo.ca
>Subject: Re: Another newbie
>
>
>Thanks Janina, I have saved the info, but think I will read up more on
>Linux patching and kernal compiling, and hope learn enough to feel
>confident to compile my first kernal, and  add Speakup so it can be
>selected and booted from the hard disk.  I was looking for a quick and easy
>way to get Speakup talking, and then read more later.
>
>I guess I will need to put in the effort up front, and learn about this
>topic and work it out. It was suggested that I first try compiling a kernal
>to make sure everything works correctly, then try it with Speakup after
>that.
>
>BTW, what happens if Speakup doesn't find a synthesizer connected when it
>tries to load?  I may not have the DEC Express connected each and every
>time.
>
>Thanks for your reply.
>
>Jack
>At 11:01 AM 11/24/01 -0500, you wrote:
>>On Sat, 24 Nov 2001, Jack Daniels wrote:
>>
>>> >> I have a very small PC installed with
>>> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>>> >> What I want to be able to do is to insert a floppy with Speakup and
>any
>>> >> necessary boot files and have Linux  come up talking.  Is this
>possible?
>>
>>It seems to me you could get this working with the standard installation
>>floppy that one would create using boot.img. There are such on the speakup
>>website and they already have speakup built into them. You need two files
>>from the speakup site to test this: the appropriate boot.img and
>>rawrite.exe.
>>
>>1.)	rawrite.exe is a DOS executable for creating floppy disks from
>>image files like boot.img. Shutdown your Windows to MS-DOS before using
>>rawrite for best, most reliable results;
>>
>>2.) Get boot.img via anonymous ftp from:
>>	www.linux-speakup.org/pub/speakup/disks/redhat/7.2
>>
>>Regretably, the rawrite.exe isn't there, and perhaps that's an oversight.
>>Bill, are you listening? If you decide to try my suggestion, perhaps
>>someone can point you to a download location closer to home, but you can
>>certainly get it from redhat.com. It'll be in a dos_utils directory. There
>>should be no problem using 7.2 disks on your 7.1 system, by the way;
>>
>>3.)	You need to be careful about your speech synthesizer while using
>>rawrite. Generally, it's a good idea to kill speech while rawrite is
>>creating your floppy. So, as you hit enter on the last rawrite prompt,
>>which is the third prompt it gives you, be ready to kill your speech
>>immediately;
>>
>>54.)	If nothing went wrong in the rawrite floppy you'll have a bootable
>>floppy that you can try on your linux system. As you boot, monitor the
>>floppy disk for activity. If your system beeps as it begins to load the
>>OS, that will help. There will be a brief amount of floppy disk activity
>>at this point and then the disk stops. You're at a boot> prompt which
>>doesn't talk (though it could, see below); At this point type:
>>
>>	linux -s speakup_synth=dectlk speakup_ser=1
>>
>>I believe that even with the mismatch in installation versions this should
>>still come up talking. If it does, you can certainly look around natively,
>>and you can begin to contemplate getting a native kernel with speakup onto
>>your system. But, that's a topic for another day.
>>
>>Certainly, there will be a good number of things that won't work because
>>of the kernel mismatches. But, you should have enough to get started with.
>>
>>PS: The boot> prompt can be made to speak to any serial device with an
>>appropriate lin in the sysconfig file on the floppy:
>>
>>serial=1,9600N8
>>
>>would be the appropriate lin in this instance, and you could certainly
>>insert this line using a DOS text editor. It goes just above the first
>>"label" statement.
>>
>>
>>
>>_______________________________________________
>>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: Another newbie

[Thomas Ward]

i'm sorry to hear that you won't be able to add a cdrom, but fortunately
there are many other options here.
Option 1: you may considder some external drive system. I don't know if you
have a usb port or not, but external hard drives are a great way to backup
and install files to your Linux box.
If built into the kernel a external USB or Parallel Zip drive is another
great tool.
Lastly, you could buy a small network kit from someone like Linksys, and set
up your computer to share files and drives.
I baught such a kit myself, and am happy with it. For $60 I got a Linksys
hub, two cables, and two Linksys PCI nics.
However, this may or may not be an option for you depending on how skilled
you are with networking computers. Although, I found this to be a great
option, and great way to share files.



----- Original Message -----
From: "Jack Daniels" <Labitup@home.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, November 24, 2001 10:39 AM
Subject: Re: Another newbie


> Thanks Tom. Unfortunately, no way to add a CDROM to this machine.  It's a
> very small computer, (2.5X11.5X8.5) it has built-in everything, and room
> for only a hard disk and a floppy.  I picked it up for $25 a while ago,
and
> thought it would make a neat Linux box.  Perhaps a parallel CD drive will
> become a possibility for me down the road.
>
> I already have the Speakup files on the system and will just go ahead and
> begin reading the kernal info and start that learning curve now. If I run
> into problems, I know where to come for help.
>
> Jack
> At 11:32 PM 11/22/01 -0500, you wrote:
> >Hi, my comments are below inside your message.I have tried to answer all
> >your questions as clearly as I can. I hope this helps.
> >See below.
> >
> >
> >----- Original Message -----
> >From: "Jack Daniels" <Labitup@home.com>
> >To: <speakup@braille.uwo.ca>
> >Sent: Thursday, November 22, 2001 11:30 AM
> >Subject: Another newbie
> >
> >
> >> Hi, I am new to Speakup, and I have been following the list for just a
> >> short while now.  I want to learn whether the following is possible,
and
> >> how to best accomplish it.
> >
> >That's great. I'll see what we can do for you.
> >>
> >
> >> First, some info about my Linux box.  I have a very small PC installed
> >with
> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
> >> A friend set it up for me and I am currently using a serial connection
> >from
> >> My Win98 PC.
> >>
> >> What I want to be able to do is to insert a floppy with Speakup and any
> >> necessary boot files and have Linux  come up talking.  Is this
possible?
> >> If so, what do I need to get/do?
> >
> >Yes, it is possible, but someone would have to compile you a talking boot
> >disk image  of Speakup, for your kernel and send it too you.
> >Another suggestion is to get Emacspeak rpm, put it on a floppy, and
install
> >it to your box. At least you would  have speech natively on your Linux
box
> >until you were able to build a Speakup kernel for your machine.
> >
> >> I want to use a DEC Express on COM2, keeping the serial connection on
> >COM1.
> >>
> >
> >This is totally possible. Speakup [probes for your synths ports, and
almost
> >always finds the synth on ttys0 and ttys1. which are com1 and com2 under
> >dos.
> >
> >
> >
> >> If this is possible, and I thought it was from reading the list for
just a
> >> short time, what files do I need?
> >> How do I use them?
> >> Any info out there detailing this process?
> >>
> >
> >Unfortunately, I don't know of any specific documents that exactly gives
you
> >a step by step howto on what to do, but most of us are old hands, or at
> >least know something about what we are doing.
> >Read the kernel howto, and the readme documentation in your kernel source
> >directory.
> >You basically, will need a clean kernel source tree, and the speakup
source.
> >Also make sure you have kernel headers installed, compilers installed,
and
> >are able to build kernels.
> >
> >> I am sure there is info I have left out, so please ask any questions,
and
> >I
> >> will answer them to the best of my ability.  Rememberr, I am new, never
> >> built a kernal, the more detailed your response, the better.
> >
> >Ok, is it possible that you can get a cd rom drive for your computer?
Bill
> >has Red Hat 7.2 cd's that come with Speakup built in. All you do is
install
> >the cd's, restart, and wam you have speech.
> >I've been where you are now. Looking at a stock distribution, and
wondering
> >how to get it to talk. Here is how I learned to do it if it is a stock
> >distribution and not a Speakup modified distribution.
> >
> >I downloaded Emacspeak current version, and loaded my Dectalk Express.
Then,
> >I accessed the shell by doing alt+x, and typed shell.
> >Once I had a talking shell, I then installed the Speakup source from
floppy,
> >and put in the Linux cd, and installed the kernel source. Then, built a
> >talking kernel.
> >Since you don't have a cd rom drive you may have to substitute by first
> >configuring wvdial, and then while in Emacs with Emacspeak do an alt+x
and
> >type term.
> >This puts Emacs in a terminal  mode, and you can run wvdial & to get your
> >internet connection.
> >Then, you can run the Linux ftp program to ftp files from the
ftp.kernel.org
> >site to your box.
> >
> >So here is the summary. While it is possible to do what you want it does
> >require some compiling, configuring,  and large learning curves. However,
> >once you do it a couple of times it won't seam so huge.
> >However, if you want a quick and simple solution see if you can get
Bill's
> >modified Red Hat 7.2 disks from the Speakup ftp site, and install that.
That
> >way you get speech out of the box, and can consentrate on learning the os
> >without plunging head-long into advanced compiling, configuring, and all
> >that.
> >
> >
> >
> >>
> >> Thank you in advance for helping another newbie get up and talking with
> >> Speakup!
> >>
> >> Jack
> >>
> >>
> >> _______________________________________________
> >> 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: Another newbie

[Jack Daniels]

Tom, no USB, but I use a similar network setup, the serial connection is so
I can hear all the messages when it boots. 

Jack
Jack
At 08:43 PM 11/24/01 -0500, you wrote:
>i'm sorry to hear that you won't be able to add a cdrom, but fortunately
>there are many other options here.
>Option 1: you may considder some external drive system. I don't know if you
>have a usb port or not, but external hard drives are a great way to backup
>and install files to your Linux box.
>If built into the kernel a external USB or Parallel Zip drive is another
>great tool.
>Lastly, you could buy a small network kit from someone like Linksys, and set
>up your computer to share files and drives.
>I baught such a kit myself, and am happy with it. For $60 I got a Linksys
>hub, two cables, and two Linksys PCI nics.
>However, this may or may not be an option for you depending on how skilled
>you are with networking computers. Although, I found this to be a great
>option, and great way to share files.
>
>
>
>----- Original Message -----
>From: "Jack Daniels" <Labitup@home.com>
>To: <speakup@braille.uwo.ca>
>Sent: Saturday, November 24, 2001 10:39 AM
>Subject: Re: Another newbie
>
>
>> Thanks Tom. Unfortunately, no way to add a CDROM to this machine.  It's a
>> very small computer, (2.5X11.5X8.5) it has built-in everything, and room
>> for only a hard disk and a floppy.  I picked it up for $25 a while ago,
>and
>> thought it would make a neat Linux box.  Perhaps a parallel CD drive will
>> become a possibility for me down the road.
>>
>> I already have the Speakup files on the system and will just go ahead and
>> begin reading the kernal info and start that learning curve now. If I run
>> into problems, I know where to come for help.
>>
>> Jack
>> At 11:32 PM 11/22/01 -0500, you wrote:
>> >Hi, my comments are below inside your message.I have tried to answer all
>> >your questions as clearly as I can. I hope this helps.
>> >See below.
>> >
>> >
>> >----- Original Message -----
>> >From: "Jack Daniels" <Labitup@home.com>
>> >To: <speakup@braille.uwo.ca>
>> >Sent: Thursday, November 22, 2001 11:30 AM
>> >Subject: Another newbie
>> >
>> >
>> >> Hi, I am new to Speakup, and I have been following the list for just a
>> >> short while now.  I want to learn whether the following is possible,
>and
>> >> how to best accomplish it.
>> >
>> >That's great. I'll see what we can do for you.
>> >>
>> >
>> >> First, some info about my Linux box.  I have a very small PC installed
>> >with
>> >> Redhat 7.1, kernal 2.4.2-12 running on a P133 with no CDROM.
>> >> A friend set it up for me and I am currently using a serial connection
>> >from
>> >> My Win98 PC.
>> >>
>> >> What I want to be able to do is to insert a floppy with Speakup and any
>> >> necessary boot files and have Linux  come up talking.  Is this
>possible?
>> >> If so, what do I need to get/do?
>> >
>> >Yes, it is possible, but someone would have to compile you a talking boot
>> >disk image  of Speakup, for your kernel and send it too you.
>> >Another suggestion is to get Emacspeak rpm, put it on a floppy, and
>install
>> >it to your box. At least you would  have speech natively on your Linux
>box
>> >until you were able to build a Speakup kernel for your machine.
>> >
>> >> I want to use a DEC Express on COM2, keeping the serial connection on
>> >COM1.
>> >>
>> >
>> >This is totally possible. Speakup [probes for your synths ports, and
>almost
>> >always finds the synth on ttys0 and ttys1. which are com1 and com2 under
>> >dos.
>> >
>> >
>> >
>> >> If this is possible, and I thought it was from reading the list for
>just a
>> >> short time, what files do I need?
>> >> How do I use them?
>> >> Any info out there detailing this process?
>> >>
>> >
>> >Unfortunately, I don't know of any specific documents that exactly gives
>you
>> >a step by step howto on what to do, but most of us are old hands, or at
>> >least know something about what we are doing.
>> >Read the kernel howto, and the readme documentation in your kernel source
>> >directory.
>> >You basically, will need a clean kernel source tree, and the speakup
>source.
>> >Also make sure you have kernel headers installed, compilers installed,
>and
>> >are able to build kernels.
>> >
>> >> I am sure there is info I have left out, so please ask any questions,
>and
>> >I
>> >> will answer them to the best of my ability.  Rememberr, I am new, never
>> >> built a kernal, the more detailed your response, the better.
>> >
>> >Ok, is it possible that you can get a cd rom drive for your computer?
>Bill
>> >has Red Hat 7.2 cd's that come with Speakup built in. All you do is
>install
>> >the cd's, restart, and wam you have speech.
>> >I've been where you are now. Looking at a stock distribution, and
>wondering
>> >how to get it to talk. Here is how I learned to do it if it is a stock
>> >distribution and not a Speakup modified distribution.
>> >
>> >I downloaded Emacspeak current version, and loaded my Dectalk Express.
>Then,
>> >I accessed the shell by doing alt+x, and typed shell.
>> >Once I had a talking shell, I then installed the Speakup source from
>floppy,
>> >and put in the Linux cd, and installed the kernel source. Then, built a
>> >talking kernel.
>> >Since you don't have a cd rom drive you may have to substitute by first
>> >configuring wvdial, and then while in Emacs with Emacspeak do an alt+x
>and
>> >type term.
>> >This puts Emacs in a terminal  mode, and you can run wvdial & to get your
>> >internet connection.
>> >Then, you can run the Linux ftp program to ftp files from the
>ftp.kernel.org
>> >site to your box.
>> >
>> >So here is the summary. While it is possible to do what you want it does
>> >require some compiling, configuring,  and large learning curves. However,
>> >once you do it a couple of times it won't seam so huge.
>> >However, if you want a quick and simple solution see if you can get
>Bill's
>> >modified Red Hat 7.2 disks from the Speakup ftp site, and install that.
>That
>> >way you get speech out of the box, and can consentrate on learning the os
>> >without plunging head-long into advanced compiling, configuring, and all
>> >that.
>> >
>> >
>> >
>> >>
>> >> Thank you in advance for helping another newbie get up and talking with
>> >> Speakup!
>> >>
>> >> Jack
>> >>
>> >>
>> >> _______________________________________________
>> >> 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
>>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
>