From: lee@dlpco.dlpco.COM (Lee Penn)
Newsgroups: biz.sco.general
Subject: SCO UNIX and Telebit Worldblazer
Date: 26 Sep 92 14:08:37 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

>Is anyone running a Telebit Worldblazer with SCO UNIX (3.2.2 as well as
>3.2.4)?  Are you using Dialers entries or a dialer program?  Can you
>send me your dialers entry and/or dialer program source code?
>Also, any info or wisdom about the various register settings on the
>Worldblazer for UUCP dial-in/out would be greatly appreciated.

>BTW, I am trying to configure the Worldblazer to run on a Specialix
>SI + TA/8.  The manual mentions that the stty(C) setting of 50 baud
>will really be mapped to 57600 bps.  Has anyone successfully configured
>a Worldblazer (or for that matter, any modem) to run with such a port
>speed?  What did you have to do with the Devices, Systems and gettydefs
>files?  What about the dialer program and/or dialer scripts?

We have a telebit 2500 on our specialix port set to 19200.  It 
works great and connects to everything at just about every speed 
imaginable.  This is how I use it:
(BE SURE AND USE THE CABLE EXACTLY AS DOCUMENTED IN THE SPECIALIX
MANUAL)

02/29/91  TBIT 2500 Notes for DLP Technologies, Inc.

GOAL:  Lock the modem <-> server connection at 19,200 baud while
        allowing remote users to dial in at baud rates from
        300 -> 9600 baud using various protocols; PEP, V.42, 
        MNP etc.

TBIT 2500 register settings:

        These are the ones I've changed from the factory default
        settings:

        S01=1   Answer 1 ring

        S07=120 Allow enough time to connect to remote modems
                which do not answer on the first ring.

        S45=255 Remote access enable so I can fix the modem from
                a remote location (my home)

        S50=0   Allow all baud rates to connect

        S51=5   CPU <-> Modem interface speed locked at 19,200

        S52=1   DTR causes modem to hang up if it drops and 
                modem will not answer if DTR is not active.

        S54=3   BREAK transferred out to remote system

        S58=2   CTS/RTS flow control between CPU <-> Modem

        S66=1   Lock the interface speed, use flow control

        S69=1   XON/XOFF characters are passed to remote modem

        S92=1   Issue PEP tones last to allow for slower modems
                to connect without agravation.  NOTE: Another
                TBIT dialing into my system must have S50=255
                to force a high speed connection, otherwise
                that modem may well connect at 2400 baud.
                When I dial out on this modem I change S50 to
                255 to insure a high speed connection.

        S95=2   MNP AutoReliable mode.  This sometimes even works
                but I've had problems with this.

        S97=1   V.42 enabled.  This is better than MNP

        S106=1  V.42 will be detected, S97 must also be a 1

        S111=30 UUCP G protocol selected.  I like to force this
                since most of my connections are to uunet and 
                sosco.  I find their modems are not always set
                to force UUCP G.  Leaving S111 at 255 would
                allow for automatic protocol detection.

        S131=1  DCD is ON only when carrier is really present!
                This is critical for proper hanging up when a 
                remote user disconnects without logging off.

==============  That is what I change!  ( Lee )

The SCO dialer supplement includes a number of default dialer
scripts that are stored in /etc/default.  This is really a pretty
nice trick as it makes it very easy to setup unique dialer scripts
for different purposes.  The original atdialT25 made the mistake
of reprogramming the Telebit 2500 from scratch which destroyed
all my carefully programmed settings.  That was not nice.  I've
left the original SCO setup line commented out.

Notice that since I am dialing out and expect a T2500 at the other
end, I am forcing S50 to 255.  I have another script that is for
connecting to slower modems called atdialT25S which is for slower
modems and sets S50=0.

===== cut here for my atdialT25 script =========
*  Original SCO setup was below
* MDM_SETUP=AT&Fs7=120s45=255s51=5s52=2s58=2s66=1s67=0s68=2s92=0s95=2ate0&w
*
*MDM_SETUP=ATZS50=0  <=== for slow modems
*
MDM_SETUP=ATZS50=255
MDM_OPTION=
MDM_ANSWER=
MDM_DIALCMD=ATDT
MDM_ESCAPE=+++
MDM_HANGUP=ATQ0H0
MDM_RESET=ATZ
MDM_DIALIN=ATS0=1Q1
MDM_ATTN=AT
MDM_DSBLESC=ATS2=128
RTC_OK=OK
RTC_NOCARR=NO CARRIER
RTC_ERROR=ERROR
RTC_NOTONE=NO DIALTONE
RTC_BUSY=BUSY
RTC_NOANS=NO ANSWER
RTC_300=not used
RTC_1200=not used
RTC_2400=CONNECT 2400
RTC_4800=not used
RTC_9600=not used
RTC_19200=CONNECT FAST
RTC_38400=not used
==================  end of script ============

I do not warrantee this in any way.  But it does work well for
us.  Hope it helps others.
================================================================================
Lee Penn,  DLP Technologies, Inc.                     Voice: 513 232-7791
SCO Advanced Product Center                           FAX: (513) 232-7801
7444 Jager Ct.
Cincinnati, OH  45230-4344                           email: lee@dlpco.COM
Newsgroups: biz.sco.general