fnf@fishpond.UUCP (Fred Fish) (03/17/88)
Ok, so where is comp.sys.aux... :-) I have been frustrated for some time by not being able to use a HAYES compatible modem for dialins to A/UX by uucp from another system. The problem I was experiencing, and it was happening for both a true Hayes 2400 and an Avatex 2400, was that as soon as the modem on the A/UX end answered, the connection would be immediately broken. After trying several different configurations (and reading the A/UX manual :-), I finally got it working. This is what I believe the original problem sequence was, though my evidence is mostly trial-and-error results, and supposition: Remote Machine A/UX Machine -------------- ------------ getty starts up on dialin line and issues <lots of mumbletyfoo> login: uucico dials out modem detects ring and issues verbose result "RING" getty sees user "RING" and issues password: modem connects and issues verbose result "CONNECT" getty sees bogus user login and dies ***BAM***, disconnect uucico gets no carrier message and tries again see above I'd be embarrassed to admit how long it took me to figure out what was going on. Since everything worked fine with an Avatex 1200, which is NOT HAYES compatible, I was even considering the possibility of some sort of bizarre modem compatibility problem between both ends of the link. Anyway, the fix is easy: kermit kermit> set line /dev/tty0 kermit> set speed 2400 kermit> connect ATS0=1 OK ATQ1 AT&W This does make using the modem for dialouts via the changing of init levels as described in the A/UX documentation more complicated, as you now have to go back in and change the modem setup manually. If this gets to be too annoying I guess I'll try writing a little filter that gets called first from inittab, to set the Q1 mode dynamically, without writing the new configuration back to the nonvolatile memory. Anyone ported HD uucp to this guy yet? It's a shame that with the other enhancements like ksh, they decided to ship an inferior uucp. -Fred -- # Fred Fish hao!noao!mcdsun!fishpond!fnf (602) 921-1113 # Ye Olde Fishpond, 1346 West 10th Place, Tempe, AZ 85281 USA
sysop@stech.UUCP (Jan Harrington) (03/23/88)
in article <17@fishpond.UUCP>, fnf@fishpond.UUCP (Fred Fish) says: > > > I have been frustrated for some time by not being able to use > a HAYES compatible modem for dialins to A/UX by uucp from another > system. The problem I was experiencing, and it was happening for > both a true Hayes 2400 and an Avatex 2400, was that as soon as the > modem on the A/UX end answered, the connection would be immediately > broken. After trying several different configurations (and reading > the A/UX manual :-), I finally got it working. This is what I > believe the original problem sequence was, though my evidence is > mostly trial-and-error results, and supposition: > Not that this is any help to you in particular, but I thought people on the net might be interested in knowing that Hayes modems in general are not very friendly with Unix System V. It doesn't seem to matter what machine you're using. Just try getting one to work bi-directionally! Jan Harrington, sysop Scholastech Telecommunications UUCP: ihnp4!husc6!amcad!stech!sysop or allegra!stech!sysop BITNET: JHARRY@BENTLEY ******************************************************************************** Miscellaneous profundity: "No matter where you go, there you are." Buckaroo Banzai ********************************************************************************
cej@ll1a.UUCP (Jones) (03/25/88)
In article <484@stech.UUCP>, sysop@stech.UUCP (Jan Harrington) writes: > Not that this is any help to you in particular, but I thought people > on the net might be interested in knowing that Hayes modems in general > are not very friendly with Unix System V. It doesn't seem to matter > what machine you're using. Just try getting one to work > bi-directionally! > > Jan Harrington, sysop Uhhh, Jan, I got several Hayes modems working bi-directionally on several 3B2/300s and 3B2/400s running System V with no trouble at all. (Maybe that's because I didn't know I should have had trouble ;-) What may have made it easy is that the 3B2s come with modem connectors that have a few lines jumped together. (I don't recall which lines, right off hand, but if anyone would like to know, drop me some e-mail, and I can find out.) The problem some people seem to have is that (at least on 3B2s) the uugetty expects that CD will be high to indicate that the modem is alive *before* it will dial out, but expects that the CD line will be "winked" low on loss of carrier on both incoming and outgoing. If your modem won't "wink" CD on loss of carrier with the "CD always high" option set (my Hayes modems did), or (sometimes) if you don't have the proper lines jumped you will have problems getting a modem to work bi-directionally. I'm no A/UX expert, mind you. I don't know when I'll have the cash and desire to add A/UX to my Mac II. But I have gotten Hayes, Ventel, and AT&T modems working bi-directionally on several SysV systems. So feel free to send me e-mail, and I'll share my meager knowledge. ...ll1a!cej [Just me, not AT&T] Llewellyn Jones HASA Qualified - U.S. Approved