Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!timbuk!cs.umn.edu!uc!noc.MR.NET!nic.stolaf.edu!nic.stolaf.edu!swansonc From: swansonc@acc.stolaf.edu (Chris Swanson, St. Olaf College) Newsgroups: comp.dcom.modems Subject: Re: Help: Why MNP5? Message-ID: Date: 31 Jan 91 05:34:21 GMT References: <1991Jan18.194613.13435@watserv1.waterloo.edu> <0cD8V3w163w@ozonebbs.UUCP> <1991Jan27.160653.7104@nstar.rn.com> <15126@celit.fps.com> Sender: news@acc.stolaf.edu Organization: St. Olaf College / N.E.T. Ambulance Lines: 21 In-Reply-To: billd@fps.com's message of 27 Jan 91 21:44:07 GMT Whomever set up one of the MNP5 modems up that you had problems with really screwed up. MNP5 defines a method for negotiating between two MNP5 modems what kind of connection is to be used. If one of the modems had compression strictly disabled, then the other modem should have stepped down to the disabled modems capability level. If that did not happen, then the second modem had compression forced on (most MNP5 modems have 3 settings, 1-No compression ever, 2-compression if the other modem can handle it, and 3-compression no matter what). It seems as that whomever set-up the modem that was using compression set it up in "mode 3", a very stupid move; either that or the hardware was broken or the firmware did not impliment the MNP5 protocol correctly. Either way that is not cause to blame the protocol it self. -Chris -- Chris Swanson, Chem/CS/Pre-med Undergrad, St. Olaf College, Northfield,MN 55057 DDN: [CDS6] INTERNET: swansonc@acc.stolaf.edu UUCP: swansonc@stolaf AT&T: Work: (507)-645-6845 Home: (507)-663-6424 I would deny this reality, but that wouldn't pay the bills...