modem control (was: Abandoned shell)

LCDR Michael E. Dobson rdc30med at nmrdc1.nmrdc.nnmc.navy.mil
Tue Dec 18 03:19:47 AEST 1990


In article <1990Dec10.192820.12812 at eci386.uucp> woods at eci386.UUCP (Greg A. Woods) writes:
>
>Make sure your modem is supplying a DCD signal that follows the true
>carrier (by setting the right options/switches), and that HUPCL is
>specified in all of the gettydefs lines for the port your modem is
>connected to.  Needless to say, use the proper RJ-45 -> DB-25 adapter
>too (i.e. an "005" modem connector).
>
>Warning:  If you are using this modem bi-directionally, i.e. you call
>out on it too, make sure you are running SysVr3.2, since the older
>BNU's don't support modem control properly (i.e. they didn't really
>support bi-directional modems, regardless of the presence of uugetty).
>

They still don't do it properly, at least on my 3B2/600G (aka 1000/80)
running SysVr3.2.2.  In order to dial out with cu or uucp, I have to force
DCD high which effectively means I can't do full modem control on bi-directional
lines.  It seems uugetty is still broken :-(

Anyone got a working replacement source that is PD (I don;t have a source
license)?
-- 
Mike Dobson, Sys Admin for      | Internet: rdc30med at nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30med
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson at usuhsb or nrd0mxd at vmnmdsc
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719 at mcimail.com



More information about the Comp.sys.att mailing list