[net.dcom] hayes smart-modems and SYSV unix

rct@occrsh.UUCP (03/10/86)

(I'm mailing the following directly to slu70!pasken as requested, but
figured it might be worth rehashing here as well.)

Regarding Hayes Smartmodem 1200s and SYSV Unix...

I've found that the following switch settings produce good overall
results:
	1 2 3 4 5 6 7 8
	u u u d u d u d		u=up, d=down

Note the setting of switch 3, which sets the modem so that no result
codes are sent.

The following lines are from my L-dialers file (no, I haven't installed
Honey-Danber UUCP on my 3B2 yet...  I also use cgetty instead of the
newer uugetty):

# The HAYES entry commented out below (supplied by the folks at
# UNIX Hotline) works fine for dialing out, but if configuration
# switch 6 is down (as it must be to dial out) and the modem echos
# local commands, folks attempting to dial in don't get a carrier.
# Note that the HAYES entry installed below has this "feature" as
# an undesirable side effect of an unsuccessful dial out, i.e., no
# one will be able to dial in until a successful dial out occurs
# because the modem doesn't get reset to turn off echoing of local
# commands!
#
# HAYES =,-, "" \dAT\r\c OK\r \eATDT\D\r\c CONNECT
HAYES =,-, "" \dATQ0S2=36\r\c OK\r \eATDT\D\r\c CONNECT \d$$$\c OK\r \dATQ1S2=43O\r\c ""

The rest of the solution (with cgetty anyway) is to manipulate /etc/inittab
and /etc/gettydefs to provide the affected port(s) with a
9600-1200-300 circular autobauding getty, so that when getty is enabled
on the port, it comes up at 9600 baud and you avoid the nasty situation
of the modem trying to "log in" on the port.

I hope this helps!  Until I replaced my Hayes modems with Penrils, this
combination of kludges served admirably.

Note that if anyone out there is sufficiently masochistic, I might be
able to help out with Rixon modems as well.

--Bob Tracy	AT&T Technologies, Inc.		Oklahoma City Works
...!ihnp4!occrsh!rct
...!uokvax!occrsh!rct