Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!mcnc!uvaarpa!haven!wam.umd.edu!mikec
From: mikec@wam.umd.edu (Michael D. Callaghan)
Newsgroups: comp.sys.next
Subject: Re: Modem dial-up problems
Keywords: modem getty etc
Message-ID: <1991Mar14.204058.14941@wam.umd.edu>
Date: 14 Mar 91 20:40:58 GMT
References: <3265@unccvax.uncc.edu>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 40
Nntp-Posting-Host: wor

In article <3265@unccvax.uncc.edu> cs00jec@unccvax.uncc.edu (Jim Cain) writes:
>
>Well, I just got my custom modem cable. It was $17.50 at
>a custom cable builder. This is what I've got happening
>so far:
>
>I have changed /etc/ttys to have a line that reads:
>
>   ttyda "/usr/etc/getty std.1200" dialup on
>
>On port A is connected a Hayes 1200 using the cable
>I had built according to the "NeXT to Modem Cable"
>configuration given on p.187 of the Net & Sys Admin
>Manual (release 2.0).
>
>Now when init starts up the getty process, the receive
>and send lights on the modem come on and stay on. When I
>call the modem, it answers and immediately hangs up.

Your modem is echoing back everything the computer sends it.
So, when you're computer says go, the modem says "OK". The 
computer thinks someone is trying to log in. So it says,
"Log In" and your modem says, "ERROR" and your computer says
"Password:" and your modem says, "ERROR" and so on and so on...

>One more problem: when I use cu or tip with /dev/cua,
>it says the line is busy, but according to the manual
>you should be able to use /dev/cua to dial out if
>/dev/ttyda is waiting.

This happens on my machine ever since I upgraded to 2.0.
So far, the fix has been just not to use that port, but 
that's the coward's way out.


-- 
MikeC
_________________________________________________________
Michael D. Callaghan, MDC Designs, University of Maryland
mikec@wam.umd.edu