Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!HOSS.UNL.EDU!ho From: ho@HOSS.UNL.EDU (Tiny Bubbles...) Newsgroups: comp.dcom.modems Subject: Reliable and Compression Protocols -- how do they sync up? Message-ID: <9104170413.AA03912@ucbvax.Berkeley.EDU> Date: 17 Apr 91 04:12:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: Lines: 36 >Newsgroups: comp.dcom.modems >Path: unlinfo.unl.edu!hoss!ho >From: ho@hoss.unl.edu (Tiny Bubbles...) >Subject: Re: Reliable and Compression Protocols -- how do they sync up? >Message-ID: <1991Apr17.010942.10457@unlinfo.unl.edu> >Sender: news@unlinfo.unl.edu >Nntp-Posting-Host: hoss.unl.edu >Organization: >References: <1991Apr14.062847.16418@colnet.uucp> <3913.280b3f55@hayes.uucp> >Distribution: na >Date: Wed, 17 Apr 1991 01:09:42 GMT >Lines: 17 Say I have a dumb modem and I'm calling a smart modem, oh, for example, a Microcom QX-series MNP 10/LAPM modem. (Real hypothetical, huh? :-) ) I advise people not to type *anything* for 2.5 seconds after the dumb modem reports a connect to prevent being mistaken for an MNP modem. But is there anything (like spaces, backspaces, returns) that would actually cause a modem like that to screw up? I ask that because it seems to have happened to a few people, and nobody knows why. Also, some el-cheapo internal modems, most of them using very old chipsets, can't connect to the Microcoms *at all*. Is this a problem with other V.32 modems, or just Microcoms, or just our setup? -- ... Michael Ho, University of Nebraska Internet: ho@hoss.unl.edu | Harry was too homely for Sally. (I have proof.) Disclaimer: Views expressed within are purely personal and should not be applied to any university agency. -- ... Michael Ho, University of Nebraska Internet: ho@hoss.unl.edu | Harry was too homely for Sally. (I have proof.) Disclaimer: Views expressed within are purely personal and should not be applied to any university agency.