Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!mcnc!unccvax!cs00jec
From: cs00jec@unccvax.uncc.edu (Jim Cain)
Newsgroups: comp.sys.next
Subject: Modem dial-up problems
Keywords: modem getty etc
Message-ID: <3265@unccvax.uncc.edu>
Date: 15 Mar 91 01:05:12 GMT
Organization: University of NC at Charlotte
Lines: 39


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.

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.

Do I have to change any other configuration files? How
about changing the modem configuration from the default?
This is a modem I borrowed from work, and neither I nor they
have a manual for it, so I don't know how to change its
settings.

I would greatly appreciate any help anyone might offer.

Thanks,
Jim

-- 
=================== Jim Cain * cs00jec@unccvax.uncc.edu ===================
               The University of North Carolina at Charlotte
             College of Engineering * Dept of Computer Science
========== "'ave you been shopping?" * "No, I've been shopping." ==========