Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!hayes!tnixon
From: tnixon@hayes.uucp
Newsgroups: comp.dcom.modems
Subject: Re: Reliable and Compression Protocols -- how do they sync up?
Message-ID: <3918.2812af47@hayes.uucp>
Date: 22 Apr 91 09:39:18 GMT
References: <7220.280D2809@zswamp.uucp>
Organization: Hayes Microcomputer Products, Norcross, GA
Lines: 29

In article <7220.280D2809@zswamp.uucp>, root@zswamp.uucp (Geoffrey
Welsh) writes: 

>    During my experimentation with the GVC Super Modem 9600 (V.32 & V.42), I 
> found that my Hayes Smartmodem reported only 0x91 characters; is there a 
> logical explanation for this, or might this have been the source of 
> occasional problems I had with the GVC V.32?

If the GVC modem only sends 0x91 characters, a V.42-compliant 
answering modem will not recognize it as supporting LAPM protocol.  
It should connect in MNP after fallback, I hope...

>    I have found many modems which don't like being blasted with a V.42 
> negotiation request, and sometimes dropping them to MNP only solved the 
> problem.  One example is a SendFAX modem sold under the name "Hedaka"; I 
> can't call it with V.42 modems such as the ATI 2400etc and the latest 
> revision of HST, but the older HSTs (which only requested MNP) and modems 
> such as the Cardinal 2400MNP work fine.  The Hedaka locks up completely when 
> called by a V.42 compliant modem!

Does the Hedaka have MNP itself?  Or is it a non-error-control 
modem?  It's strange that it would "lock up", but then nothing much 
surprises me in modems anymore.

-- 
Toby Nixon, Principal Engineer    | Voice   +1-404-840-9200  Telex 151243420
Hayes Microcomputer Products Inc. | Fax     +1-404-447-0178  CIS   70271,404
P.O. Box 105203                   | UUCP uunet!hayes!tnixon  AT&T    !tnixon
Atlanta, Georgia  30348  USA      | Internet       hayes!tnixon@uunet.uu.net