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: <1214@mtunb.ATT.COM>
Date: 13 May 88 16:43:00 GMT
References: <2307@ukecc.engr.uky.edu> <5237@mtune.ATT.COM> <2311@ukecc.engr.uky.edu> <1209@mtunb.ATT.COM>
Reply-To: rag@mtunb.UUCP (was-Richard Grant)
Organization: AT&T ISL Middletown NJ USA
Lines: 29

In article <1209@mtunb.ATT.COM> rag@mtunb.UUCP (was-Richard Grant) writes:
>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.
>
>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


Yuck! That foot tastes bad.  I was answering based on a poorly remembered
conversation of long ago.  It turns out that with version 3.5+ anyway, ATE
does exec /usr/bin/umodem.  I have not determined just what the full
interface is but the arguments passed for receiving a binary file over
tty000 seem to be:

	umodem -rbm /full/path/filename /dev/tty000

Good luck using this info.  Sorry about the initial bum steer.

	Rich Grant
	mtune!mtunb!rag