Path: utzoo!utgpu!water!watmath!uunet!lll-winken!lll-tis!pacbell!gladys!bakerst!mtune!mtunx!lzaz!mtunb!rag
From: rag@mtunb.ATT.COM (Richard Grant)
Newsgroups: unix-pc.general
Subject: Re: Re: File Transfer Programs
Message-ID: <1209@mtunb.ATT.COM>
Date: 10 May 88 20:05:23 GMT
References: <2307@ukecc.engr.uky.edu> <5237@mtune.ATT.COM> <2311@ukecc.engr.uky.edu>
Reply-To: rag@mtunb.UUCP (was-Richard Grant)
Organization: AT&T ISL Middletown NJ USA
Lines: 16

In article <2311@ukecc.engr.uky.edu> edward@engr.uky.edu (Edward C. Bennett) writes:
>>> Is there a way to add more protocols to the ATE?
>
>There is a file /usr/bin/umodem that I assume contains the UMODEM code.
>Based on that, I assume the ATE forks off a umodem process and connects
>stdin and stdout to it. If that's right, then, theoretically, you could
>put a copy of rz inplace of /usr/bin/umodem. The ATE wouldn't know the
>difference. No, I haven't tried it but it seems like a safe experiment

Sorry, but it doesn't work that way.  umodem is in /usr/bin so that
it can be executed from the shell when called by another machine.
(Consider using the ATE on another UNIX PC and calling your UNIX PC.)
The umodem protocol is compiled into the ATE without hooks to provide
other protocols.

	Rich Grant
	mtune!mtunb!rag