Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uwm.edu!ogicse!milton!cpac.washington.edu!dennis From: dennis@cpac.washington.edu (Dennis Gentry) Newsgroups: comp.sys.next Subject: Re: Modem dial-up problems Message-ID: Date: 19 Mar 91 04:02:11 GMT References: <3265@unccvax.uncc.edu> <1991Mar14.204058.14941@wam.umd.edu> <7283@idunno.Princeton.EDU> Sender: news@milton.u.washington.edu Organization: /u1/cpac/dennis/.organization Lines: 26 In-reply-to: js@sidney.Princeton.EDU's message of 18 Mar 91 17:33:06 GMT In article <7283@idunno.Princeton.EDU> js@sidney.Princeton.EDU (Jay Sekora) writes: In article <1991Mar14.204058.14941@wam.umd.edu>, mikec@wam.umd.edu (Michael D. Callaghan) writes: >Your modem is echoing back everything the computer sends it. >So, when you're computer says go, the modem says "OK". The >computer thinks someone is trying to log in. So it says, >"Log In" and your modem says, "ERROR" and your computer says >"Password:" and your modem says, "ERROR" and so on and so on... Sounds like a klugey way to deal with this would be to create a user ERROR, whose password is ERROR, and whose shell is something like /bin/true. What's the right way? Actually, the modem doesn't typically say "ERROR." Typically, the modem echoes everything. If the computer says "login:" the modem says "login:" right back, and things deteriorate from there. The right way is to turn off echoing and command responses in the modem, and save that setting in its NVRAM, typically via the ATE0Q1&W command (E0 means no echo, Q1 means "Quiet mode on", and the &W writes the settings to NVRAM). My advice is to get the NeXT Tech support document on serial port connectivity for lots more details. I believe this document is available via anonymous ftp from the archive servers, or, for registered developers, direct from NeXT tech support. Dennis