Path: utzoo!utgpu!water!watmath!uunet!labrea!rutgers!tut.cis.ohio-state.edu!osu-cis!att!ihlpl!ihchk!ihtlt!kosman!kevin
From: kevin@kosman.UUCP (Kevin O'Gorman)
Newsgroups: unix-pc.general
Subject: Re: (Long) Why can't I get PCOMM to work with my Trailblazer?
Message-ID: <456@kosman.UUCP>
Date: 15 Sep 88 23:23:12 GMT
References: <454@kosman.UUCP> <559@rbdc.UUCP>
Reply-To: kevin@kosman.UUCP (Root)
Organization: K.O.'s Manor - Vital Computer Systems, Oxnard, CA 93035
Lines: 21

In article <559@rbdc.UUCP> andy@rbdc.UUCP (Andy Pitts) writes:
>In article <454@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
>
>>MODEM_1a=DIRECT;;;;
>>MODEM_1b=Y;;;;;;
>>MODEM_1c=;;;
>>MODEM_2a=TELEBIT-SLOW;%AAAAAATS66=0S51=255S52=2S50=0S95=0!;%AAAAAATS64=1S92=0S7
>                                                                         ^^^^^
>Note: S92 has no meaning when dialing out.  It only affects how the Telebit
>answers.
>

All the rest of what Andy wrote made good sense, and some of it made me blush.
Here, however, he falls prey to the RTFM trap: he believed what he read.
In a long debugging session with Telebit, we found that in certain config-
urations, S92 causes the firmware to go south on outgoing calls.  The safe
thing to do is to set S92=0 on all outgoing calls.  The symptoms vary
somewhat, but I remember getting NO CARRIER if the responding modem did not
pick up immediately.  I forget now what other settings caused this bug
to surface.  Anyway, I now ALWAYS set S92=0 on outgoing calls, and have
S52=2 to reset things when the call is done.