Xref: utzoo comp.dcom.modems:3698 comp.unix.questions:12855 comp.sys.ibm.pc:27402 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!amanue!oglvee!jr From: jr@oglvee.UUCP (Jim Rosenberg) Newsgroups: comp.dcom.modems,comp.unix.questions,comp.sys.ibm.pc Subject: Re: MNP Auto-Reliable + getty: happy accident or design? Message-ID: <476@oglvee.UUCP> Date: 13 Apr 89 19:14:31 GMT References: <475@oglvee.UUCP> <13575@steinmetz.ge.com> Reply-To: jr@.UUCP (Jim Rosenberg) Organization: Oglevee Computer Systems, Connellsville, Pa Lines: 21 In article <13575@steinmetz.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes: > I have had really bad luck autobauding with MNP modems. They seem to >eat the BREAK sent by uucp to force baudrate change. Fortunately other >characters seem to work, but I don't see any incoming data when sending >BREAK. I will not profess to be a complete wizard on this subject, but I think the trick to getting BREAK to work with MNP is to put enough delays into your send sequence that the MNP handshake has had a chance to succeed or fail. I run a link with cgh. Paul Homchick (cgh!paul) instructed all his net neighbors to be sure to put some delays before sending a BREAK when he ran an MNP modem. I had my system set up so it wouldn't send BREAK til the first timeout, & that always worked just fine. What has me puzzled is just how MNP seems to toggle getty *WITHOUT SENDING* the BREAK. -- Jim Rosenberg pitt Oglevee Computer Systems >--!amanue!oglvee!jr 151 Oglevee Lane cgh Connellsville, PA 15425 #include