Xref: utzoo comp.dcom.modems:2771 comp.sys.att:4582
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!bloom-beacon!tut.cis.ohio-state.edu!osu-cis!att!westmark!dave
From: dave@westmark.UUCP (Dave Levenson)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: Verbose modems (Re: MORE 6386 UUCP WOES)
Keywords: cu, Hayes Modem
Message-ID: <469@westmark.UUCP>
Date: 22 Oct 88 02:25:47 GMT
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <889@vsi.COM>
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 27

In article <889@vsi.COM>, friedl@vsi.COM (Stephen J. Friedl) writes:
> In article <5042@cbmvax.UUCP>, ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
...
> > (Modem sends "CONNECT" message to the computer ... computer thinks
> > "CONNECT" is a login name, etc.).
...
> It is certainly a drag to be stuck in upper case because
> RING was seen as a login.  To combat this, we set our modems
> to give digit result codes instead of verbose ones; we've
> been quite pleased except that it's harder to debug the
> outgoing dialing...

There is a simpler solution, for UNIX Sys V Rel 2.5 on the 6300PLUS.
Perhaps it also applies to the 6386.  In your inittab, when you
spawn uugetty on the modem, set option -d<n> with a value in seconds.
This causes uugetty to ignore characters for <n> seconds before
prompting for login.  I generally use uugetty -d8 to pause 8 seconds
after answering before prompting.  This means that the modem can
generate the RING message, and then the CONNECT	message that results
from the modem handshake, before I expect a login name.  Verbose
mode works fine with this option.   I find verbose mode makes the
dialer script a bit more robust.

-- 
Dave Levenson
Westmark, Inc.		The Man in the Mooney
Warren, NJ USA
{rutgers | att}!westmark!dave