From: mahmha@crl.com (Mark A. Horton) Subject: Re: Internal modem on COM3 problems Date: 25 Sep 1993 08:30:34 -0700
CAM PROCTOR (bcp1@cc.msstate.edu) wrote:
: I have an Infotel 14.4K baud modem (internal) set at com3 (irq4). When trying
: to access the modem with anything (kermit, minicom, pcomm) I get the reply
: "can't open /dev/modem. Device busy." I've also tried setting the programs
: to look directly at /dev/cua2 and /dev/ttyS2, but still the same results. A
: local person suggested re-linking the /dev/modem to each /dev/cuaX (where X is
: 0 - 3) and seeing what happened. I still got the same results on cua2, but on
: cua1 i would get nothing (no negative response) since this is my mouse, cua0
: would say it was busy also.
: Does anyone have another suggestion to try?
You might have a getty active to it - check inittab. If this is
the case, your comm programs will not be allowed to snatch it. Use
uugetty instead (but check doc for right parameters!)
If this is the case, you can call it whatever you wish and getty will
still own it and not let go!
- Mark
: Please email me at one of the following addresses.
: bcp1@ra.msstate.edu
: bcp1@cc.msstate.edu
: bcp1@pcmail.cc.msstate.edu