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: talking lilo prompt?
Date: Sat, 2 Sep 2000 22:30:49 -0700	[thread overview]
Message-ID: <000701c015e2$7a58b540$0100a8c0@wang> (raw)
In-Reply-To: <200008140957.FAA02789@randomc.com>

It is really easy:
put the following line in your /etc/lilo.conf after the first or second line
just to make it look nicer:

serial=0,9600n8

For whatever reason, Doubletalk LT swallows part of the welcome message, but
you can hear some speech anyway.
Regards,
Vic

----- Original Message -----
From: "dana" <dana@randomc.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, August 13, 2000 6:44 PM
Subject: Re: talking lilo prompt?


> You know what? I am using the same setup here also, and would like some
info
> on that also. My computer gives a few beeps, and waits for me to type dos
or
> linux. That would be nice to have.
>
> On 2000-08-14 speakup@braille.uwo.ca said:
>     Hi listers,
>     I have seen several of you mention a talking lilo prompt.  I am
>     interested in this, could someone tell me how to set it up?
>     I am using RedHat linux 6.1, and a doubletalk pc with speakup 0.09.
>     Thanks much,
>     William
>
> Net-Tamer V 1.12.0 - Registered
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 dana
 ` Jim Wantz
   ` William Hubbs
     ` Brent Harding
       ` Joseph Norton
         ` Charles Hallenbeck
       ` Geoff Shang
         ` Brent Harding
           ` Geoff Shang
     ` Jim Wantz
       ` Kirk Reiser
 ` Victor Tsaran [this message]
 William Hubbs
 ` Brent Harding
 dana
 dana
 dana
 ` Brent Harding
   ` dana

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='000701c015e2$7a58b540$0100a8c0@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).