Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!nrl-cmf!ames!ucbcad!pasteur!ucbvax!MITRE-BEDFORD.ARPA!jhs
From: jhs@MITRE-BEDFORD.ARPA
Newsgroups: comp.sys.atari.8bit
Subject: kermit65 and XM301
Message-ID: <8801201529.AA16115@mitre-bedford.ARPA>
Date: 20 Jan 88 15:29:19 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 52

Glenn Euloth writes...
>      I am running an Atari 130XE and a 1050 drive.  I am using an XM301
>  modem with this configuration and I would like to know how I can get
>  Kermit-65, which was posted a while back, to work.  I have two files, one I
>  am told is Kermit with NO rs232 port (XM301 modem?) and one with rs232.  I
>  am also using this at home with a phone.  Could someone who has such a
>  thing working please explain to me how theirs is set up.  I have heard some
>  good things about Kermit but I have yet to get it to work.  Also, how do
>  you (or can you) get it to dial?  The documentation makes no mention of it.
>  Any help would be greatly appreciated!
>
>                                               Glenn Euloth

The two versions of kermit65 are identical except that the one "with"
is "with" an RS-232 handler attached (prepended or appended, I am not
sure which).  CDY's OmniCom is "shipped" ONLY WITHOUT a handler (unless
someone has tacked one on).  If you had an 850 or very compatible rs-232
controller, you could use kermit65 "with" the standard handler.  I'm not
familiar with the XM301, but I believe it requires a special, i.e. different,
handler.  I seem to recall seeing one posted that was written in ACTION! and
included autodialing and emulation of other Hayes features in the handler
itself.  In any case, you DEFINITELY will need to load a handler along with
the bare bones kermit65 just as you do with OmniCom, in order to make it
work with ANY serial comms device.

It is usually convenient to select a handler, then tack it on either in front
of or at the end of the terminal emulator program.  The DOS loader (program
that runs when you use the L command) then will load both the handler and the
terminal emulator "automatically" (what else, its a computer after all!!??).
Concatenating the two load modules is easy: just copy the one you want first
to a file with the desired name, e.g.

     C<RETURN>
     FILE1.OBJ, TERMPROG.COM<RETURN>.

Then copy the one you want second to the SAME FILE, but use the /A (append)
switch on the end of the destination file's name, with no spaces, e.g.

     C<RETURN>
     FILE2.OBJ, TERMPROG.COM/A<RETURN>.

Deciding which to put first and which to put second may be harder; in general
it is probably safest to put the handler file first, as the terminal emulator
program probably will most likely be designed to start running upon being
loaded.  This has to do with which type of "load vector" the files end with.
Sometimes binary files are incompatibly assembled so that neither order will
work.  In that case, you have to go in and patch the final load vectors of one
or both using a sector editor/debugger.  However, if you find an XM301 handler
and put it in front of kermit65 or OmniCom, I suspect you will be "on the
air".

-John Sangster / jhs@mitre-bedford.arpa