Path: utzoo!attcan!uunet!cs.utexas.edu!usc!srhqla!denwa!stb!michael
From: michael@stb.info.com (Michael Gersten)
Newsgroups: comp.dcom.modems
Subject: Re: HST's vs. Telebits (was Searching for inexpensive V.32...)
Message-ID: <1990Apr14.174417.13843@stb.info.com>
Date: 14 Apr 90 17:44:17 GMT
References: <1438@mindlink.UUCP> <139@dynasys.UUCP> <1319@faatcrl.UUCP>
Organization: The Serial Tree BBS, +1 213 397 3137
Lines: 26

In article <1319@faatcrl.UUCP> jimb@faatcrl.UUCP (Jim Burwell) writes:
>on a full duplex connection, Telebit put "File Transfer Protocol Support" into
>it's modems.  You enable this by setting an S register (S111 on a T2500) to
>the value for the protocol you'll be using for that call.  The modem detects
>when the file transfer starts and "spoofs" the file transfer between the 

Exactly. This is the problem--you have to specify in a register which
protocol you are using on that call. And both sides have to specify the
same one. **ARRGGHH**.

Effectivly, it is UUCP only spoofing, unless you let your users change
their end and your end to kermit (in which case they can change your
end into a real mess).

Much better would have been either two registers (so kermit or xmodem
could be spoofed as well), or simply a toggle register (and allowing
any of the protocols supported to run), or even a bitmask (it supports
less than 8 protocols, right?). <SIGH>.

As mail says, ubluit.

		Michael
-- 
		Michael
michael@stb.info.com denwa!stb!michael anes.ucla.edu!stb!michael 
Disclaimer: It works for me.