wek@point.UUCP (Bill Kuykendall) (11/15/89)
>In Appendix B of the X5 document it states to set up the DEFAULT modem >settings with the ATE1 command which means: "modem echos commands back to >the terminal". If I do this, I get a runaway condition where the getty >keeps sending data to the modem, the modem sends it back and both the >etc. It sounds like you're getting messed up by the different modem configurations required by uugetty and cu. {uu}getty requires NO echo and NO responses sent (E0 Q1). cu requires the opposite for it's scripts to work (E1 Q0). The trick is to set your dip switches to reflect getty's requirements, and add the E1Q0 to the modem init string in your Dialers entry (Xenix may use a different file name). The crucial element to getting this to work is to ensure that the modem reinitializes when DTR is dropped (thus resetting for the getty process when cu is finished). On my US Robotics and Telebit modems there is a register value (different on the different modems) that specifies this behavior. I don't know how Hayes handles this. Hope this helps. ------ Bill K
marc@dumbcat.UUCP (Marco S Hyman) (11/21/89)
Another option for those using verbose modem settings is to use the -r
option to uugetty. The inittab entry should look like:
00:234:respawn:/usr/lib/uucp/uugetty -r -t 60 ttyd0 DIAL96
The -r tells uugetty not to talk until it sees a \r. This allows it to work
with smart modems or on back-to-back connections with the machine on the
next desk. A dialers entry that will work with hayes type modems is:
hayes =,-, "" \M\dAT\r\c OK\r \EATDT\T\r\c CONNECT \m\c
direct =,-, "" \M\dAT\r\c OK\r \c
This assumes the Dialers entry uses the M flag, e.g.
ACU ttyd0,M - 2400 hayes
The modem should be programmed something like:
AT &F
AT &D2 V1 Q E1 S0=1 &C1 &S1 &W
Since my distributor has not received the X5 update yet I'm making do with
the vanilla 2.0.2 release. This works OK in that environment.
--marc
--
// Marco S. Hyman {ames,pyramid,sun}!pacbell!dumbcat!marc