Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!dayvb!fac2
From: fac2@dayton.saic.com (Earle Ake)
Newsgroups: comp.sys.amiga
Subject: Re: A working UUEncode
Message-ID: <1029.260febef@dayton.saic.com>
Date: 28 Mar 90 03:40:47 GMT
References: <1966@dsacg3.dsac.dla.mil>
Organization: Science Applications Intl. Corp., Dayton, Ohio
Lines: 24

In article <1966@dsacg3.dsac.dla.mil>, nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg) writes:
> Not too long ago I tried to get a program up to a UNIX machine, but had little
> luck due to lack of being able to uuencode the .zoo file. I vaguely remember 
> talk in the distant past about a problem with uuencode (approx. Fish58 & 92). 
> Does it work or is there a better way available? It seems like I used it like
> this: 'uuencode source_file dest_file' or 'uuencode source_file >dest_file' but
> after about 5 minutes I would kill it and find a destination file of about 25
> bytes. I was getting the impression it was using the terminal for input instead
> of the source_file.
> 					       Thanks, Mike

	Use the command 'uuencode >dest_file source_file dest_filename'

where dest_file is where the uuencoded output will be written, source_file
is the source, and dest_filename is what it will use as an output filename
when uudecoding it after you send it.

-- 
_____________________________________________________________________________
             ____ ____    ___
Earle Ake   /___ /___/ / /     Science Applications International Corporation
           ____//   / / /__                 Dayton, Ohio
-----------------------------------------------------------------------------
Internet: fac2%dayton.saic.com@uunet.uu.net    uucp: dayvb!fac2