From: Cheryl Homiak <chomiak@chartermi.net>
To: blinux-list@redhat.com
Subject: Re: The Minicom Saga (cont.)
Date: Wed, 30 Jan 2002 22:07:04 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0201302153450.2829-100000@maranatha.chartermi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0201301544240.4566-100000@localhost.localdomain>
John,
To quit minicom, just do control-a x and then, even though on the braille
display it may look like no is selected it isn't; just hit enter; it will
tell you it is resetting the modem and then exit.
As for the dialing out, look in your dialing directory and make sure you
have the number and all the info set up correctly; another way to test
this would be just to do control-a d and then m for manual; then you can
type in the phone number and listen to what happens. By the way, have you
used this modem under linux other than what you are now doing with
minicom; are you sure the modem is working under linux?
My problem is that I set minicom to /dev/ttyS1 to interface with my
braillelite, so now my braille display quits every time I go into minicom;
that's ok if I also have speakup loaded but otherwise I then have to kill
minicom and restart brltty. Looks like I may have to set minicom back to
/dev/ttys# (seems to be what it's choosing for the default) and only put
in /dev/ttyS1 when I want to download or upload to brltty.
As for the baud rate, I was wondering about this too, as I allways have to
go back to parameters and reset it to 9600 when I want to use the
braillelite. Is there a way to reset this permanently?
Also, I finally got minicom to upload and download using my braillelite,
but it only downloads or uploads a small portion of the file before the
transfer stops. I do consider this progress, but any suggestions as to why
I can't transfer the entire file would be appreciated.
Thanks.
--
Cheryl
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Nicolas Pitre
` Cheryl Homiak [this message]
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=Pine.LNX.4.44.0201302153450.2829-100000@maranatha.chartermi.net \
--to=chomiak@chartermi.net \
--cc=blinux-list@redhat.com \
/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).