From: "Ann" <tate886_thequeen@bigfoot.com>
To: <speakup@braille.uwo.ca>
Subject: Re: US Robotics 56K Voice PCI
Date: Thu, 23 May 2002 16:58:26 -0400 [thread overview]
Message-ID: <001201c2029c$96875340$d6780cd8@oemcomputer> (raw)
In-Reply-To: <20020523154953.A2377@romualt.dhs.org>
I don't mind reading a couple of docs. What docs do I need, and where can
they be found?
~Ann
----- Original Message -----
From: "Gregory Nowak" <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 23, 2002 4:49 PM
Subject: Re: US Robotics 56K Voice PCI
| I'm sorry about that. I forgot that you might not have gotten around to
building your own kernel yet. I haven't used zipspeak for 2 years or so.
Does anyone out there remember if the standard zipspeak kernel comes with
extended serial options configured into it. If not, then you will need to
build your own kernel. If you're up to reading a couple of docs, it is not
as hard as it sounds, as long as you know what hardware you have in your
system.
| Greg
|
|
| On Thu, May 23, 2002 at 04:42:16PM -0400, Ann wrote:
| > LOL! As far as I know, I haven't actually configured anything. With
| > Zipspeak, all you need to do is extract the files to the root of
whatever
| > drive you want, edit the LInux.bat file to point in the right direction,
and
| > start in Dos, type linux, and away you go. Wouldn't have a clue as to
how to
| > enable extended serial options in the kernel yet - I'm new to this
stuff.
| > ~Ann
| >
| >
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
|
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Ann
` Gregory Nowak
` Janina Sajka
` Saqib Shaikh
` Janina Sajka
` Ann
` Gregory Nowak
` Ann
` Gregory Nowak
` Ann [this message]
` Gregory Nowak
` Gregory Nowak
` Adam Myrow
` Gregory Nowak
` Ann
` Toby Fisher
` Gregory Nowak
` Igor Gueths
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='001201c2029c$96875340$d6780cd8@oemcomputer' \
--to=tate886_thequeen@bigfoot.com \
--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).