rct@occrsh.ATT.COM (Bob_Tracy) (09/05/87)
Many moons ago, I posted this same information. Since the topic comes up repeatedly, I'm determined to drive a stake through its heart this time and put to rest all those nasty rumors to the effect that one can't use a Hayes Smartmodem 1200 on a bidirectional line. The fact of the matter is, you can... BUT, this solution is at best a compromise. More on that in a minute. On your 3B2 (not verified on other machines), use this entry for "hayes" in your "Dialers" file (HDB UUCP assumed, but this also worked with standard SVR2 UUCP): =============--CUT HERE--=============== # Hayes Smartmodem -- modem should be set with the configuration # switches as follows: # # S1 - UP S2 - UP S3 - UP S4 - DOWN # S5 - UP S6 - DOWN S7 - UP S8 - DOWN # hayes =,-, "" \dATQ0S2=36\r\c OK\r \eATDT\T\r\c CONNECT \d$$$\c OK\r \dATQ1S2=43O\r\c "" =============--CUT HERE--=============== Note the switch settings and USE them. Also note that I haven't mentioned any hardware modifications: none are required with this approach. No funky cables, no buggered connectors, etc. Here's the catch: :-( This setup works reliably until an unsuccessful dialout occurs. Then, no one attempting to dial in will get a carrier until a successful dialout occurs. This behavior should be apparent when you examine the "Dialers" entry and note the 'Q0' 'Q1' settings and where they take place during the calling sequence. A workaround is to poll a reliable site frequently (perhaps once an hour) in order to reset the possibly hung modem. Bottom line: The Hayes Smartmodem 1200 is clearly not the modem of choice for this application, but it can be made to work if you are sufficiently hard-up. Believe me, you could do worse... Details to those with masochistic tendencies on request :-). --Bob Tracy AT&T Network & Data Systems Oklahoma City Works {most AT&T sites}!occrsh!rct