Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!super.upenn.edu!eecae!nancy!msudoc!sumrall
From: sumrall@msudoc.ee.mich-state.edu (Kenneth Sumrall)
Newsgroups: comp.sys.atari.8bit
Subject: Re: Using Kermit65 with either the XM301 or 1030, HELP!
Message-ID: <205@nancy.UUCP>
Date: Fri, 20-Nov-87 14:21:19 EST
Article-I.D.: nancy.205
Posted: Fri Nov 20 14:21:19 1987
Date-Received: Sun, 22-Nov-87 18:36:10 EST
References: <19871111164904.1.JRD@GRACKLE.SCRC.Symbolics.COM> <1485@bsu-cs.UUCP> <3518@uwmcsd1.UUCP> <723@potpourri.UUCP>
Sender: usenet@nancy.UUCP
Reply-To: sumrall@msudoc.UUCP (Kenneth Sumrall)
Followup-To: comp.sys.atari.8bit
Organization: Michigan State Univ., Engineering, E. Lansing
Lines: 57
Keywords: Kermit, Kermit65, XM301, 1030, HELP!
Summary: T handler is indeed in the 1030 and XM301

>No, no, no!!!  The T: handler in NOT built into the XM301 OR the 1030
>modems.  The T: handler is usually appended (or pre-pended) to the
>modem PROGRAM you are using.  Of course, some modem programs have the
>handler already incorporated (Express! is a good example).  Chameleon gives
>you the choice of handlers; you pick from a menu of supported modems and
>Chameleon loads up the appropriate handler.
>
>The only terminal programs that use the R: handler are the ones written for
>modems connected to a serial interface (R: = RS232??).
>

Ok.  Now for some facts.  The XM301 and 1030 modems do indeed have a
built in T: handler.  In fact, it is described in some great detail in
Antic magazine.  I'm not sure what issue it is in, but the article is
written by the same guy who wrote the Hometerm program.

Sending commands to the T: device driver is much different than sending
commands to the R: device driver.  The R: driver responds to XIO
commands from basic, or their equivilent CIO calls from assembly.  The
T: handler is accessed by setting memory location 7 to non-zero, and then
sending ESC sequences.  Memory location 7 is then set to zero, and the
ESC sequences are just sent through to the modem.  

There are many device drivers for the 1030 and XM301 modems that act
like T: and R: drivers, however, and they are often pre-pended to
terminal programs to supply the required device driver.  I have seen a T:
handler that uses XIO calls instead of using ESC sequences for control
of the modem.  I have also seen an R: driver for the 1030 and XM301 that
implement the stantard XIO calls of the 850 R: driver.  This driver also
implements additional XIO calls to support dialing, going on and off
line, and other various modem functions.  This is the device driver that
I am using to run the Omnicom terminal program posted to the net a while
ago. 

Now, to use Kermit 65 with the 1030 or XM301, one of two things must be
done.  The first is to find an R: driver for the 1030 and XM301 that
emulates the Hayes command set.  I have heard of a rumor that such a
driver exists, but I have never seen it.  If someone has one, please
post it to the net, as the rest of us would appreciate it.  The second
possibility is to teach Kermit 65 how to dial the 1030 and XM301 modems
if present.  This is not that hard to do, provided source code is
available.  I will send John R. Dunning info on how to do this as soon
as I am able to write it all down legibly.  Maybe he will release a 3rd
version of Kermit 65 then. :-)  

Well, I have gone on long enough, and I haven't even mentioned the MPP
modem and the similiar problems that it has.  I will have an MPP to play
with during Christmas break, and if I find anything interesting, I will
post it to the net.  Till then.

Kenneth Sumrall
ARPA:     sumrall@msudoc.egr.msu.edu
UUCP:     ihnp4!msudoc!sumrall

P.S.  I would appreciate any and all replies concerning the above, but
no flames please, my flame proof suit is at the cleaners. :-)