Here is my original posting...
>
>I need some help with setting up the new version on UUCP on our SUN 4/330
>running 4.1. Basically, I have a similar problem to a previous net msg but
>I don't know how to implement the suggested solution. My problem is in
>the chat script of 'uucico'. When the chat script gets to the point
>of expecting the passwd, nothing happens ie: it times out. The comment was
>something along the lines of adding the option 'P_ZERO' (and that's a guess at
>the options syntax ) to the chat script, but where do you add this option, in
>the Dialers file, or the Systems file or where??
>
>Another problem comes up when I simply want to execute 'tip machine_name' on a
>dial-in, dial-out port. I get the msg "can't synchronize with modem".
>What's funny though is 'uucico' doesn't have a problem at this point
>although I believe both tip and uucico use the same file, Dialers which
>handles the initialization. In order to make the command 'tip machine_name' work
>I have to set the modem ( Hayes 2400 ) to assume data carrier always
>present ie: &C0. But this is not a solution for the obvious reasons and
>also because once I enable the port ( for dial-in dial-out use ) then
>'tip machine' or 'uucico' give me the following error msg, "all ports
>busy".
>What's wrong with me. Help!
>
I want to thank everyone who responed. I was able to resolve my most pressing
problem, that of UUCP not 'chat'ing correctly with the use of the 'P_ZERO'
option. However, I still can't get 'tip machine_name' to work ( msg: cant sync
with hayes),and yet 'tip cua0' works fine. I have kept the syntax in /etc/remote
as the users msgs below suggest ( ie: it matches the book as well ). Here is my
Hayes profile:
AT &V
ACTIVE PROFILE:
B1 E0 L1 M1 Q1 V1 X4 Y0 &C1 &D3 &G0 &J0 &L0 &P0 &Q0 &R0 &S1 &X0 &Y0
S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:030
S08:002 S09:006 S10:014 S12:050 S14:ACH S16:00H S18:000 S21:78H
S22:75H S23:17H S25:005 S26:001 S27:40H
STORED PROFILE 0:
B1 E0 L1 M1 Q1 V1 X4 Y0 &C1 &D3 &G0 &J0 &L0 &P0 &Q0 &R0 &S1 &X0
S00:001 S14:ACH S18:000 S21:78H S22:75H S23:17H S25:005 S26:001
S27:40H
STORED PROFILE 1:
B1 E1 L2 M1 Q0 V1 X4 Y0 &C0 &D0 &G0 &J0 &L0 &P0 &Q0 &R0 &S0 &X0
S00:000 S14:AAH S18:000 S21:00H S22:76H S23:17H S25:005 S26:001
S27:40H
TELEPHONE NUMBERS:
&Z0=
&Z1=
&Z2=
&Z3=
The active profile supports dialin-dialout, which is what I want, but 'tip
machinename' doesn't work. With stored profile 1, 'tip machinename' works
fine.
As stated in my original msg, changing &C1 does the trick but of course
not something that is acceptable.
I hope this isn't something obvious that I have missed!
**********************************************************************
Kevin Kimsa vmail: 416-366-6363
The Braegen Group Inc. fax : 416-366-4428
email: uunet!moore!bragrt!kck
**********************************************************************
***********************************************************************
Here are the responses I have received so far....
***********************************************************************
>From uucp Thu Nov 8 18:59 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA13020; Thu, 8 Nov 90 18:59:53 EST
Received: by moore.UUCP (smail2.5)
id AA09082; Thu, 8 Nov 90 18:46:29 EST
Received: from ucsd.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA14431; Thu, 8 Nov 90 15:38:55 -0500
From: uunet!ucsd!snoopy!tots.Logicon.COM!louis
Received: from snoopy.UUCP by ucsd.edu; id AA17308
sendmail 5.64/UCSD-2.1-sun via UUCP
Thu, 8 Nov 90 11:26:51 -0800
Received: from tots.UUCP by Snoopy.Logicon.COM (5.61/7.17) with UUCP
id AA05535; Thu, 8 Nov 90 11:15:14 -0800
Received: from leaf1.sun.com by tots.Logicon.COM (3.2/4.02)
id AA06975; Thu, 8 Nov 90 10:55:22 PST
Received: by leaf1.sun.com (3.2/SMI-3.2)
id AB12123; Thu, 8 Nov 90 10:56:10 PST
Date: Thu, 8 Nov 90 10:56:10 PST
Message-Id: <9011081856.AB12123@leaf1.sun.com>
To: moore!bragrt!kck
In-Reply-To: Kevin Kimsa's message of Wed, 7 Nov 90 19:01:43 EST <9011080001.AA01453@bragrt>
Subject: SUN 4.1 UUCP question
Status: RO
Refer to a copy of your post to sun-managers. I don't have the latest
and greatest SunOS running, but your first paragraph rang a small
bell. One of my (I think of them as mine) remote sites starting
behaving much more responsibly when I changed its line in my L.sys
file from something like:
toad Any,1 ACUHAYES 4800 16195551212 "" \r in:--in: Ume word: passwd
to something more like:
toad Any,1 ACUHAYES 4800 16195551212 "" \r in:-\r-in: Ume word: passwd
The difference in those two lines is the "-\r-" in the first, replacing
the "--" in the one that didn't work nearly as well.
For your second paragraph, take a look at the file /etc/remote (or its
corresponding file on your newer operating system) and make the entry
for machine_name match, at least for baud rate, the stuff that uucp
uses from L.sys, L-devices, and so forth.
Good luck!
pending dramatic signature file Louis Brune
...sun!suntan!tots!louis
San Diego, CA louis@tots.Logicon.COM
(619) 455-1330 x403
>From uucp Fri Nov 9 00:00 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA15168; Fri, 9 Nov 90 00:00:16 EST
Received: by moore.UUCP (smail2.5)
id AA10531; Thu, 8 Nov 90 22:02:26 EST
Received: from poseur.jpl.nasa.gov by uunet.uu.net (5.61/1.14) with SMTP
id AA09106; Thu, 8 Nov 90 17:00:27 -0500
Received: by poseur.JPL.NASA.GOV (4.1/SMI-4.1)
id AA06524; Thu, 8 Nov 90 01:03:07 PST
Date: Thu, 8 Nov 90 01:03:07 PST
From: uunet!poseur.JPL.NASA.GOV!earle (Greg Earle - Sun JPL on-site Software Support)
Message-Id: <9011080903.AA06524@poseur.JPL.NASA.GOV>
Errors-To: uunet!poseur.JPL.NASA.GOV!nobody
Precedence: junk
To: moore!bragrt!kck
Subject: Re: Sun 4.1 UUCP questions
Status: RO
>My problem is in the chat script of 'uucico'. When the chat script gets to
>the point of expecting the passwd, nothing happens ie: it times out. The
>comment was something along the lines of adding the option 'P_ZERO' ( and
>that's a guess at the options syntax ) to the chat script, but where do you
>add this option, in the Dialers file, or the Systems file or where??
It can go in either the Dialers file (if, for example, you wanted to apply it
to all `hayes' dialer dialed calls) or the Systems file (if you only need it
for certain systems). And you would use ` "" P_ZERO ' because it is part of
an expect-send couplet.
Do you not have a 4.1 Documentation set? This is described pretty clearly on
pages 660-668 of the 4.1 "System and Network Administration" manual.
>Another problem comes up when I simply want to execute 'tip machine_name' on a
>dial-in, dial-out port. I get the msg "can't synchronize with modem".
It *should* be saying "Can't synchronize with hayes" or possibly "Can't
synchronize with ventel". I.e., you have to define the correct dialer type in
/etc/remote. Send me the /etc/remote entry for `machine_name' and any other
/etc/remote entries that are included (i.e., via the `tc=' specifier).
Make sure your entry in /etc/remote looks something like this:
machine_name:\
:pn=14165551212:tc=UNIX-2400:
..
UNIX-2400:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#2400:tc=dialers:
..
dialers:\
:dv=/dev/cua0:\
Make sure you properly created the /dev/cua0 device according to the
instructions in the 4.1 "System and Network Administration" manual. i.e.,
cd /dev
mknod cua0 c 12 128 (If using serial port A, a.k.a. /dev/ttya)
chown uucp.daemon cua0
chmod 600 cua0
>What's funny though is 'uucico' doesn't have a problem at this point
>although I believe both tip and uucico use the same file, Dialers which
>handles the initialization.
This is not true. cu(1) and UUCP use `Dialers'. tip(1) uses /etc/remote.
>In order to make the command 'tip machine_name' work I have to set the modem
>( Hayes 2400 ) to assume data carrier always present ie: &C0.
Then your modem hardware configuration is not correct. It should only put up
CD when it actually connects to a remote modem, or it receives an incoming
connection.
- Greg Earle
Sun Microsystems, Inc. - JPL on-site Software Support
earle@poseur.JPL.NASA.GOV (Direct)
...!uunet!poseur.jpl.nasa.gov!earle
>From uucp Fri Nov 9 00:00 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA15174; Fri, 9 Nov 90 00:00:18 EST
Received: by moore.UUCP (smail2.5)
id AA10542; Thu, 8 Nov 90 22:02:31 EST
Received: from idgeast.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA26804; Thu, 8 Nov 90 17:34:01 -0500
Received: from dent.dent.idgeast.com by idgeast (4.1/SMI-4.1)
id AA07443; Thu, 8 Nov 90 09:13:57 EST
Date: Thu, 8 Nov 90 09:13:57 EST
From: uunet!idgeast!mark (Mark Cappel)
Message-Id: <9011081413.AA07443@idgeast>
To: moore!bragrt!kck
Subject: uucp & tip
Status: RO
Greetings Kevin,
uucp and tip *do not* use the same Dialers file for outbound calls. tip
uses the file /etc/remote to tell it how and who to call. Given that you
are using a Hayes modem, you need to change all of the "ventel" references
to "hayes" for the speeds you plan to use. In your case, I would imagine
you would need to change the "UNIX-2400" and maybe "UNIX-1200" too if you
plan to call at the slower speed.
tip and cu are different beasts.
Once you nose around in the remote file I think more of how remote works
will become clear.
As for the chat script timing out, there are several things to look at.
First, get tip talking to the modem. If memory serves, you can enter the
command 'tip h2400' to get into the modem. There is some S register setting
to set the timeout. THe default, I think, is 60 seconds. Make it longer.
(Check you Hayes manual to find how to do this.) Also, check to make
sure gettydefs isnt set to kill the line after too short of a wait.
You do not want the modem to always assume DTR. Bad things happen, as
you have found. Check the manual System & Network Administration, page
326, for details.
Hope this helps.
Mark Cappel
Senior Editor
SunTech Journal
dartvax!idgeast!mark
>From uucp Fri Nov 9 13:54 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA19703; Fri, 9 Nov 90 13:54:30 EST
Received: by moore.UUCP (smail2.5)
id AA25652; Fri, 9 Nov 90 13:30:09 EST
Received: by becker.UUCP (smail2.5/bdb-15Aug90)
id AA00401; Fri, 9 Nov 90 12:58:04 EST (-0500)
Received: by mnetor.UUCP (smail2.3)
id AA05409; 8 Nov 90 14:10:33 EST (Thu)
Received: from SUN.COM by uunet.uu.net (5.61/1.14) with SMTP
id AA12225; Thu, 8 Nov 90 10:32:34 -0500
Received: from snail.Sun.COM (snail.Corp.Sun.COM) by Sun.COM (4.1/SMI-4.1)
id AA15032; Thu, 8 Nov 90 07:32:33 PST
Received: from East.Sun.COM by snail.Sun.COM (4.1/SMI-4.1)
id AA13824; Thu, 8 Nov 90 07:32:30 PST
Received: from sunne.East.Sun.COM (sunne-fddi) by East.Sun.COM (4.1/SMI-4.1)
id AA03325; Thu, 8 Nov 90 10:32:28 EST
Received: from kfir.East.Sun.COM by sunne.East.Sun.COM (4.1/SMI-4.1)
id AA26681; Thu, 8 Nov 90 10:29:41 EST
Date: Thu, 8 Nov 90 10:29:41 EST
From: uunet!Sun.COM!halstern (Hal Stern - Consultant)
Message-Id: <9011081529.AA26681@sunne.East.Sun.COM>
To: bragrt!kck
Subject: Re: SUN 4.1 UUCP question
Status: RO
as for the "all ports busy" problem, it sounds like you don't
have hardware carrier set up properly. this changed radically
from 4.0.3 to 4.1; in 4.0.3 you have to tweak a kernel config
file flag, and in 4.1 it's controlled by a token in the /etc/ttytab
file (the "local/remote" flag). see ttysoftcar for more details.
the "can't synchronize" error is probably due to a bad /etc/remote
file. tip and uucico do not use the same Dialers file -- uucico
uses DIalers, but tip is still the BSD-style utility that reads
/etc/remote to find modem configuration info. you probably have
a "dialer=vental" in there instead of "dialer=hayes".
--hal stern
sun microsystems
northeast area consulting group
>From uucp Fri Nov 9 13:54 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA19709; Fri, 9 Nov 90 13:54:33 EST
Received: by moore.UUCP (smail2.5)
id AA25657; Fri, 9 Nov 90 13:30:11 EST
Received: by becker.UUCP (smail2.5/bdb-15Aug90)
id AA00666; Fri, 9 Nov 90 13:07:49 EST (-0500)
Received: by mnetor.UUCP (smail2.3)
id AA00112; 9 Nov 90 03:32:58 EST (Fri)
Received: from camco1.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA08553; Thu, 8 Nov 90 15:06:36 -0500
Received: from camco by camco1.Celestial.COM (smail2.5c) with UUCP
id AA02795; 8 Nov 90 10:25:17 PST (Thu)
Received: from hood by camco.Celestial.COM (smail2.5c) with UUCP
id AA05592; 8 Nov 90 10:12:25 PST (Thu)
Received: by c4west.eds.com (4.1/smail2.5/10-22-87)
id AA21609; Thu, 8 Nov 90 09:25:40 PST
Date: Thu, 8 Nov 90 09:25:40 PST
From: uunet!c4west.eds.com!runyan (David Runyan)
Message-Id: <9011081725.AA21609@c4west.eds.com>
To: bragrt!kck
Subject: Re: SUN 4.1 UUCP question
Status: RO
>I don't know how to implement the suggested solution. My problem is in
>the chat script of 'uucico'. When the chat script gets to the point
>of expecting the passwd, nothing happens ie: it times out. The comment was
>something along the lines of adding the option 'P_ZERO' ( and that's a guess at the options syntax ) to the chat script, but where do you add this option, in
>the Dialers file, or the Systems file or where??
Kevin,
That was me who posted the chat script question a few weeks back.
The chat script goes in the Systems file.
We don't even use the Dialers file at our site. I have placed the
complete phone number in the Systems file chat script.
Here's the line in our Systems file about which I had questioned.
What you see includes the P_ZERO option. It fixed our passwd hanging
problem.
camco Any ACU 19200 9=<phone#> "" P_ZERO "" \r ogin:-: uuhood ssword: <password>
I got several replys to my chat script question which led to this
solution. I suppose you will get the same sort of response, but If
this isn't enough to solve your chat script woes, let me know. I will
send you a copy of the stuf I received.
Sorry, I can't help with the modem question. We experienced the same
sort of problem with our Sparcstation and Trailblazer modem, but I don't
know what we did to solve it...or even if the problem is fixed. Modems
are still misterious to me.
regards
dave
runyan@c4west.eds.com
>From uucp Fri Nov 9 13:54 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA19715; Fri, 9 Nov 90 13:54:37 EST
Received: by moore.UUCP (smail2.5)
id AA25662; Fri, 9 Nov 90 13:30:12 EST
Received: by becker.UUCP (smail2.5/bdb-15Aug90)
id AA00762; Fri, 9 Nov 90 13:10:17 EST (-0500)
Received: by mnetor.UUCP (smail2.3)
id AA00731; 9 Nov 90 03:35:26 EST (Fri)
Received: from auspex.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA19706; Thu, 8 Nov 90 17:21:10 -0500
Date: Thu, 8 Nov 90 14:15:43 PST
From: uunet!auspex!guy (Guy Harris)
Message-Id: <9011082215.AA24196@auspex.com>
To: bragrt!kck
Subject: Re: SUN 4.1 UUCP question
Status: RO
>The comment was something along the lines of adding the option 'P_ZERO'
>( and that's a guess at the options syntax )
It's a precise guess. It's actually sort of a "send" string, so you'd
give a null string as the "expect" string (the syntax, and the option
itself, came from the 4.3BSD UUCP; I put it in on the theory that it
might be useful, and it turned out to be useful)....
>to the chat script, but where do you add this option, in
>the Dialers file, or the Systems file or where??
Either one - I'd tend to put it in the Systems file on the grounds that
the requirement for a zero parity bit is imposed by the system you're
connecting to.
See p. 668 of the "System & Network Administration" manual.
>Another problem comes up when I simply want to execute 'tip machine_name' on a
>dial-in, dial-out port. I get the msg "can't synchronize with modem".
>What's funny though is 'uucico' doesn't have a problem at this point
>although I believe both tip and uucico use the same file, Dialers which
>handles the initialization.
I don't think so; "strings /usr/bin/tip" shows no signs of any
"/etc/uucp" files. The SunOS "tip" is basically a 4.3BSD "tip", and
that didn't even use the 4.3BSD UUCP configuration files, much less any
Honey DanBer files - its dialer code is compiled in, in the form of
specific routines for specific autodialers.
>In order to make the command 'tip machine_name' work I have to set the
>modem ( Hayes 2400 ) to assume data carrier always present ie: &C0. But
>this is not a solution for the obvious reasons and also because once I
>enable the port ( for dial-in dial-out use ) then 'tip machine' or
>'uucico' give me the following error msg, "all ports busy".
Yup. If it assumes carrier is present, I assume it pulls DCD high,
which causes the dial-in side's "open" to complete; if the dial-in side
is open, the dial-out side is busy.
Is "tip" dialing out on "/dev/cua0" (or whatever you've called the
dial-out port), or "/dev/ttyd0" (or whatever you've called the dial-in
port)?
>From uucp Fri Nov 9 13:54 EST 1990
Received: by bragrt (AIX 2.1 2/4.03)
id AA19722; Fri, 9 Nov 90 13:54:41 EST
Received: by moore.UUCP (smail2.5)
id AA25667; Fri, 9 Nov 90 13:30:14 EST
Received: by becker.UUCP (smail2.5/bdb-15Aug90)
id AA00969; Fri, 9 Nov 90 13:15:00 EST (-0500)
Received: by mnetor.UUCP (smail2.3)
id AA02097; 9 Nov 90 03:42:33 EST (Fri)
Received: from [134.205.20.1] by uunet.uu.net (5.61/1.14) with SMTP
id AA26529; Thu, 8 Nov 90 22:29:38 -0500
Received: by afcsa.af.mil (4.1/SMI-4.1)
id AA02660; Thu, 8 Nov 90 22:29:30 EST
Message-Id: <9011090329.AA02660@afcsa.af.mil>
Subject: Re: SUN 4.1 UUCP question
To: bragrt!kck (Kevin Kimsa)
Date: Thu, 8 Nov 90 22:29:29 EST
In-Reply-To: <9011080001.AA01453@bragrt>; from "Kevin Kimsa" at Nov 7, 90 7:01 pm
From: uunet!afcsa.af.mil!aten (Bill Aten)
Organization: AF Center for Studies & Analyses, Washington, DC
Return-Receipt-To: uunet!afcsa.af.mil!aten
X-Mailer: ELM [version 2.3 PL8]
Status: RO
Quoting 'Kevin Kimsa':
|
| I need some help with setting up the new version on UUCP on our SUN 4/330
| running 4.1. Basically, I have a similar problem to a previous net msg but
Kevin,
I've attached some info regarding setting up UUCP and a Telebit T2500 modem.
Ignore the Telebit stuff, but you'll see some appropriate stuff for
/etc/uucp/[Devices,Dialers,Systems] and /etc/[gettytab,remote,ttytab].
Hope this helps...
_____________________________________________________________________________
Bill Aten | UUCP: ...!sun!sundc!samt19!aten
Commercial: (703) 697-2183 |
Autovon: 227-2183 | Internet: aten@afcsa.af.mil
_____________________________________________________________________________
Here's some comments on what we do very successfully with a T2500 using
SunOS 4.1 on a Sun 3/60 and Sparcstation 1+.
-------------------------
Here's my Systems file (names changed to protect the innocent):
site1 Any ACU2400A 19200 5551212 "" \d "" \r ogin:--ogin: logname1 ssword: passwd1
site2 Any ACUfastuA 19200 1,8005551212 "" \d "" \r ogin:--ogin: logname2 ssword: passwd2
site3 Never
-------------------------
Here's my Dialers file:
# Telebit TrailBlazer
#
tb1200 =W-, "" P_ZERO "" \dA\pA\pA\pTE1V1X3Q0S2=255S12=255S50=2\r\c OK\r \EATDT\T\r\c CONNECT\s1200
tb2400 =W-, "" P_ZERO "" \dA\pA\pA\pTE1V1X3Q0S2=255S12=255S50=3\r\c OK\r \EATDT\T\r\c CONNECT\s2400
tbfast =W-, "" P_ZERO "" \dA\pA\pA\pTE1V1X3Q0S2=255S12=255S50=255\r\c OK\r \EATDT\T\r\c CONNECT\sFAST
tbfastu =W-, "" P_ZERO "" \dA\pA\pA\pTE1V1X3Q0S2=255S12=255S50=255S111=30\r\c OK\r \EATDT\T\r\c CONNECT\sFAST/UUCP
-------------------------
Here's my Devices file:
ACU2400A cua0 - 19200 tb2400
ACUfastA cua0 - 19200 tbfast
ACUfastuA cua0 - 19200 tbfastu
Direct cua0 - 19200 direct
-------------------------
Here's how to make "/dev/cua0":
mknod /dev/cua0 c 12 128
chmod 666 /dev/cua0
chown uucp.uucp /dev/cua0
-------------------------
Here's my "/etc/ttytab" entry for 'ttya':
ttya "/usr/etc/getty std.19200" dialup on dialTBIT-A
-------------------------
Here's the modified sections of "/etc/gettytab":
# The default gettytab entry, used to set defaults for all other
# entries, and in cases where getty is called with no table name
#
#default:\
# :ap:lm=\r\n%h login\72 :sp#9600:
default:\
:ap:lm=\r\n\nAccess Restricted to Authorized Users Only!\r\n\n%h login\72 :sp#9600:
#
# Fixed speed entries
#
2|std.9600|9600-baud:\
:sp#9600:ht:
g|std.19200|19200-baud:\
:sp#19200:ms=crtscts:ht:
-------------------------
Also add these two lines to "/etc/remote" (note that the "^" is a caret,
ie. shift-6, and NOT a control-char indicator):
tb9600:dv=/dev/cua0:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
tb19200:dv=/dev/cua0:br#19200:el=^C^S^Q^U^D:ie=%$:oe=^D:
-------------------------
My modem configuration is as follows:
tip tb19200
connected
atn?
E1 F1 M1 Q0 P V1 W0 X0 Y0 &P0 &T4 Version GF7.00-T2500SA
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
S10=007 S11=070 S12=050 S18=000 S25=005 S26=000 S38=000
S41=000 S45=000 S47=004 S48:001 S49=000
S50=000 S51:005 S52:002 S54:003 S55=000 S56=017 S57=019 S58:002 S59=000
S61:000 S62=003 S63=001 S64=000 S65=000 S66:001 S67=000 S68=255 S69=000
S90=000 S91=000 S92=000 S93=008 S94=001 S95=000 S96=001 S97=000 S98=003
S100=000 S101=000 S102=000 S104=000 S105=001 S106=000 S107=020
S110=255 S111=255 S112=001
S121=000 S130=002 S131:001
S150=000 S151=004 S152=001 S153=001 S154=000 S155=000 S157=000 S158=000
S160=010 S161=020 S162=002 S163=003 S164=007 S169=000 S255=000
OK
-------------------------
The approach that we use is to run the TBit at 19200 all the time (modem to
computer baud rate) and let the Telebit figure out the speed desired for the
modem connection on incoming calls. The Dialers script will modify the
TBit configuration slightly on the outgoing calls to force the proper connection.
The "tbfastu" line, for example, will force a PEP connection with UUCP spoofing
enabled.
Hope this is helpful. Good luck!
***********************************************************************
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:05:59 CDT