Path: utzoo!telecom-request Date: Mon, 3 Jun 91 22:44:08 -0700 From: Steve Forrette Newsgroups: comp.dcom.telecom Subject: Question About PC Pursuit and MNP Message-ID: Organization: TELECOM Digest Sender: Telecom@eecs.nwu.edu Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 429, Message 9 of 12 Lines: 31 I hope that someone familiar with PC Pursuit or MNP-compatible modems in general can help me with this one: I need to know how to tell an MNP-compatible modem to pretend that it doesn't have MNP, so that when it calls out and reaches another MNP modem, it will "play dumb" and not enable MNP mode. In other words, the connection will be a standard 2400 baud connection. Presumably, this is done with an ATS command on the dialing end, prior to the dialing command. My situation is that I'm dialing into Telenet using a standard 2400 baud modem. The outdial modem in the remote city is dialing to an MNP (I think 5) modem, and returning a "CONNECT 2400 EC", indicating an MNP connection. The problem is that if the remote host sends data continuously for more than a screen or so, there is tremendous data corruption and loss. When the remote modems connect in standard, non-MNP mode, everything works dandy. The Customer Service people at Telenet were of no help - they couldn't quite understand the problem, and said that the only valid commands to give an outdial modem were ATZ and ATDT. I suspect that some other commands, such as ATS might work as well, but they would not tell me about them. Anyone have an answer? Thanks! Steve Forrette, forrette@cory.berkeley.edu