Path: utzoo!utgpu!watserv1!maytag!xenitec!zswamp!root
From: root@zswamp.uucp (Geoffrey Welsh)
Newsgroups: comp.dcom.modems
Subject: Re: Reliable and Compression Protocols -- how do they sync up?
Message-ID: <7243.28151108@zswamp.uucp>
Date: Tue, 23 Apr 91 11:36:55 EST
Organization: Izot's Swamp BBS (FidoNet), Kitchener, Ontario

 >From: tnixon@hayes.uucp

 >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...

   That's the thing: it appeared to connect in V.42 mode to modems such as the 
USRobotics HST.  I was wondering if this was explainable...

>    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.

   No, it's a SendFAX modem.  MNP initiation requests don't seem to bother it, 
but a call from a V.42 modem doesn't result in a usable connection.  Oddly, my 
Hayes Smartmodem 2400 won't recognize its answer tone when I call at 2400, but 
it will at 1200 (a recent occurrence, though a USR HST in my area doesn't have 
the problem... once I configured that system to call this one with LAP-M 
disabled, he has all good connects)

   You're right about one thing: *nothing* about modem connectivity should 
surprise us anymore.
 

--  
UUCP:     watmath!xenitec!zswamp!root | 602-66 Mooregate Crescent
Internet: root@zswamp.uucp            | Kitchener, Ontario
FidoNet:  SYSOP, 1:221/171            | N2M 5E6 CANADA
Data:     (519) 742-8939              | (519) 741-9553
The mile is traversed not by a single leap, but by a procession of coherent 
steps; those who insist on making the trip in a single element will be
failing long after you and I have discovered new worlds. -- me