public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Michael" <michael.ryan@nf.sympatico.ca>
To: <speakup@braille.uwo.ca>
Subject: serial port output
Date: Thu, 4 Oct 2001 17:05:29 -0230	[thread overview]
Message-ID: <000001c14d0d$97022ba0$0409a38e@nomad> (raw)

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]



Hello all: 

I'm going to change sides for a moment and use what may be identified as bad language. <grin> 

I herd that it was possible, to output the install screens of a 9-x, NT-x platform to a serial port, to have it spoken by an external synthesizer.  One of the major stumbling blocks I'm faced with is total control of building a 9-X or NT-X machine from the ground up.  I have to rely on a sited individual to read the installation screens up until the point where my screen reader can be installed.  
My current screen reader requires that IE 5.0, sound driver of course, and video driver be installed before it can become operational.  
Can anybody shed some light on this matter? 
I think one of the clear benefits of a Speakup adapted Linux machine is the ability for the blind user to hear the installation processes, along with the added security and the total independent control over 
his or her computing environment.  

Chow:  
Michael 

P S 
Anyone dabble in amateur radio? 
 
  
  
  
  
 
  


[-- Attachment #2: Type: text/html, Size: 2370 bytes --]

             reply	other threads:[~ UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael [this message]
 ` Buddy Brannan
   ` Tommy Moore
     ` Buddy Brannan
       ` governor
         ` Buddy Brannan
           ` Thomas Stivers
     ` jwantz
       ` Angelo Sonnesso
   ` Amanda Lee
     ` Charles Hallenbeck
       ` Robert Arnzen
     ` Brian Borowski
 ` Tommy Moore
 ` Janina Sajka
   ` Georgina
     ` Kirk Wood
 Dawes, Stephen

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='000001c14d0d$97022ba0$0409a38e@nomad' \
    --to=michael.ryan@nf.sympatico.ca \
    --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).