public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: Problem booting into talking installation
Date: Mon, 7 Aug 2000 22:29:36 -0700	[thread overview]
Message-ID: <000401c0010f$1e48d240$0200a8c0@wang> (raw)
In-Reply-To: <Pine.LNX.4.21.0008071837460.897-100000@wb2flw.octothorp.org>

Also, I think Bill earlier mentioned that boot disks for RedHat6.1 were
broken.
Vic

----- Original Message -----
From: "William F. Acker WB2FLW +1-303-777-8123" <wacker@octothorp.org>
To: <speakup@braille.uwo.ca>
Sent: Monday, August 07, 2000 5:48 PM
Subject: Re: Problem booting into talking installation


> Hi again,
>
>      Linux counts commports from zero instead of one.  So if your
> litetalk is on com1 you would type: text speakup_ser=0.  If it's on com2
> you would type text speakup_ser=1.  Any questions, call or write.
>
>
>
>
>
>           Bill in Denver
> On Mon, 7 Aug
> 2000, Bruce Pfeiffer wrote:
>
> > Hello again listers.  I have a question as to parameters which should be
> > passed to the kernel when booting into redhat.  When my boot prompt
comes
> > up, i type "text" and press enter.  After the system finishes loading,
it
> > refuses to talk.  Do I need to tell the kernel whare my Double Talk is
> > located at?
> >
> > Bruce
> >
> >
> > _______________________________________________
> > 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



  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Bruce Pfeiffer
 ` William F. Acker WB2FLW +1-303-777-8123
   ` Victor Tsaran [this message]
     ` blinux on evoice Raul A. Gallegos
       ` Kirk Reiser
 Problem booting into talking installation Klarich, Terry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000401c0010f$1e48d240$0200a8c0@wang' \
    --to=vtsaran@nimbus.ocis.temple.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).