From: Buddy Brannan <davros@ycardz.com>
To: speakup@braille.uwo.ca
Subject: Re: This is the modem. What to do with it?
Date: Sun, 14 Jul 2002 10:29:50 -0400 [thread overview]
Message-ID: <20020714142950.GA15096@kb5elv> (raw)
In-Reply-To: <Pine.LNX.4.33.0207140558060.2030-100000@frontdoor.g0ucu.freeserve.co.uk>
Yep, it's a Lucent (Eiger) modem. You'll want
ltmodem-something--safest bet is likely the 6.0 series, latest I've
seen is 6.00B14. You migh be lucky and have a V.92 capable modem, in
which case V8.00-something will work.
--
Buddy Brannan, KB5ELV/3 | And if the ground yawned,
Phone: (814) 455-7333 | I'd step to the side and say,
Email: davros@ycardz.com | "Hey ground! I'm nobody's lunch!"
| --Eddie From Ohio
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Octavian Rasnita
` Toby Fisher
` Buddy Brannan [this message]
` Janina Sajka
` Janina Sajka
` Octavian Rasnita
[not found] ` <Pine.LNX.4.44.0207151003230.21975-100000@TekRD.grg.afb.net >
` Patrick Turnage
` Janina Sajka
` Janina Sajka
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=20020714142950.GA15096@kb5elv \
--to=davros@ycardz.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).