Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!tank!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.xenix
Subject: Re: communicating with DOS boxes
Keywords: cu uucp term
Message-ID: <1990Mar15.214141.3617@chinet.chi.il.us>
Date: 15 Mar 90 21:41:41 GMT
References: <876@cdin-1.UUCP> <1597@fallst.UUCP> <n> <878@cdin-1.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Chicago Public Access UNIX
Lines: 21

In article <878@cdin-1.UUCP> fred@cdin-1.UUCP (Fred Rump) writes:

>>Get Emmet Grey's Pro-comm lookalike 'pcomm' from your local comp.sources.unix
>>archive.

>Thankyou all for the many responses in mail and here. But ...
>I think it may not have been clear.

It still isn't clear who is calling whom.  If the xenix machine is
calling out, pcomm or kermit will do, depending upon what the other
end expects.  If the dos machines are calling into the xenix machine
then you just need a little shell script to give a choice of file
transfer protocols and construct the appropriate commands (or force
them into it by putting the script in their .profile.  Use the
rz/sz programs (and the rx/sx, rb/sb variations) for [zxy]modem
protocols and kermit for kermit (obviously).  That should cover all
the likely choices from DOS comm programs.  You weren't really thinking
of requiring a person to be at both ends, were you?

Les Mikesell
  les@chinet.chi.il.us