Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!mintaka!oliveb!apple!mips!zaphod.mps.ohio-state.edu!usc!sdsu!crash!scotto From: scotto@crash.cts.com (Scott O'Connell) Newsgroups: comp.dcom.modems Subject: Re: Microcom Modems.....Are they any good? Message-ID: <947@crash.cts.com> Date: 20 Dec 89 21:03:15 GMT References: <2601@ucsfcca.ucsf.edu> <441@tabbs.UUCP> Reply-To: scotto@crash.cts.com (Scott O'Connell) Organization: Crash TimeSharing, El Cajon, CA Lines: 44 In article <441@tabbs.UUCP> wiz@tabbs.UUCP (Wiz) writes: >From article <2601@ucsfcca.ucsf.edu>, by jst@cca.ucsf.edu (Joe Stong): >> In article <89Nov30.204838est.58891@ugw.utcs.utoronto.ca> >> CS117341@YUSol.BITNET (Norman) writes: >> >> It was also my understanding that MNP was supposed to have invisible >> negotiations > >I too was under this impression, but my Octocomm OSI8224A MNP4 modem >always seems to play up when connecting to non-MNP modems. Most frequently >I get every character that the remote system sends preceeded with a "?". > >Also, I have had another problem with the MNP 4 emulation in the Octocom. >When I connected to an MNP 5 modem, our throughput with an error free >Z-Modem transmission was only 113 CPS, whereas if I turn off my error >correcting (MNP), I get 236 CPS. > >Any suggestions as to what I might be doing wrong, or is MNP 4 not all that >it is cracked up to be ? > >-- >Kean Johnston ..!uunet!ddsw1!olsa99!tabbs!wiz or wiz@tabbs.UUCP > > "Ahhhhhh! I see you have the machine that goes PING!" How did you get stuck with an Octocom modem? I won't go into detail as to how I know this, but I'll tell you that Octocom has the attitude that "Who cares if 99% of the other manufacturers do it one way, *WE* do it right and that makes *US* better!" I'd call technical support at Octocom and ask them why you're having those problems. I'd bet their answer is either a) that's the way it's supposed to work, or, b) you need to be using our modem on both ends, or, c) check the air in your left rear spare tire and call me tomorrow. I'm hoping that Octocom has gotten better since my exposure with them, but from the looks of the problems it's the same bunch of people doing the same things. Sigh. -- Scott O'Connell UUCP: {nosc, ucsd, hplabs!hp-sdd}!crash!ipars!scotto ARPA: crash!ipars!scotto@nosc.mil INET: scotto@ipars.cts.com