Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ptsfa!ihnp4!homxb!houxm!mtuxo!pegasus!phoenix!poseidon!popeye!naples!avalon!merlyn
From: merlyn@avalon.UUCP
Newsgroups: comp.dcom.modems
Subject: Re: Penril modems for dialups
Message-ID: <519@avalon.UUCP>
Date: Mon, 30-Mar-87 15:32:43 EST
Article-I.D.: avalon.519
Posted: Mon Mar 30 15:32:43 1987
Date-Received: Wed, 1-Apr-87 05:37:43 EST
References: <531@pyrnj.uucp>
Organization: AT&T, Summit NJ
Lines: 29
Keywords: Penril, configuration, getty

In article <531@pyrnj.uucp>, romain@pyrnj.uucp (Romain Kang) writes:
> I have a friend who wound up with a bunch of Penril smart modems...
> ...these modems don't seem to have a configuration suitable for dialup
> use.  When init opens the line, the Penril will assert DCD, allowing
> getty to run, which in turn starts a cycle of login: vs. Penril battles,
> since the Penril echoes everything back and tries to interpret each
> character as something from its command set.

Most auto-dial modems present this problem. We've used two solutions:

	- Use the ``Honey-DAN-BER'' UUCP. It adds an option
	  to the getty (really /usr/lib/uucp/uugetty) that keeps
	  the login: message from being printed until at least
	  one character comes in. Since most auto-dial modems
	  are also mute until they see incoming data, this generally
	  prevents the problem. (It does work with Penrils).

	- Set the initial getty speed to 9600 baud. The login: message,
	  if short enough, will not produce a recognizable byte,
	  keeping the modem from responding.

Either solution requires incoming calls to begin with an extra
carriage return or two, to either get the uugetty program to
prompt for login, or to get the regular getty program to cycle
to the correct baud rate.

			Steve Humphrey
			AT&T
			ihnp4!avalon!merlyn