Xref: utzoo comp.dcom.modems:2782 comp.sys.att:4599
Path: utzoo!attcan!uunet!dalsqnt!rpp386!jfh
From: jfh@rpp386.Dallas.TX.US (The Beach Bum)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: Verbose modems (Re: MORE 6386 UUCP WOES)
Message-ID: <8188@rpp386.Dallas.TX.US>
Date: 22 Oct 88 01:18:04 GMT
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <5042@cbmvax.UUCP> <889@vsi.COM>
Reply-To: jfh@rpp386.Dallas.TX.US (The Beach Bum)
Organization: River Parishes Programming, Dallas TX
Lines: 23

In article <889@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes:
>In article <5042@cbmvax.UUCP>, ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
>> I disagree.  Having "result codes" on a dialin modem on a Unix
>> system is a pretty stupid idea, ...
>
>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;

I run both lines bi-directional on this system.  The approach I use is to
turn off echo and result codes when I prepare the modem for dialin.  Then,
when the modem is being initialized for dialing out, result codes and echo
are both enabled.  I use verbose result codes since getty is no longer in
the picture.

The string I send just after hangup is ATE0V1Q1S0=1, then when I am
ready to start dialing I send ATE1V1Q0S0=0 [ and curse the RING codes I
still wind up getting ].
-- 
John F. Haugh II                        +----Make believe quote of the week----
VoiceNet: (214) 250-3311   Data: -6272  | Nancy Reagan on Richard Stallman:
InterNet: jfh@rpp386.Dallas.TX.US       |          "Just say `Gno'"
UucpNet : <backbone>!killer!rpp386!jfh  +--------------------------------------