Path: utzoo!attcan!uunet!fed!m1edb00
From: m1edb00@fed.FRB.GOV (Eric D. Boutilier)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: XXEncode/Decode
Message-ID: <279@fed.FRB.GOV>
Date: 27 Sep 88 17:04:22 GMT
References: <1524@cs.Buffalo.EDU>
Reply-To: m1edb00@fed.UUCP (Eric D. Boutilier)
Organization: Federal Reserve Board, Washington, DC
Lines: 27

In article <1524@cs.Buffalo.EDU> uggersho@cs.Buffalo.EDU (Greg Gershowitz) writes:
>
>   I recently FTP'd XXEncode and XXDecode from SIMTEL20.  However, after
>I compiled them w/Microsoft C 5.0, I attempted to encode a file.  It 
>encoded fine, but instead of being sent into the destination file, the
>output got sent to the screen...

These programs were originally designed to encode standard
input, give it a name, and pipe it to standard output.
It would operate something like this:

someprogram | uuencode filename | mail ....

But, like you, I'm usually encoding an existing file and
want to create a new file... no pipes involved.
To do this, give the source file name, another name 
for what you want it to be called when it's de-coded 
(usually the SAME name), and then direct the output to a file:

EXAMPLE:

uuencode procomm.exe procomm.exe > procomm.enc

-- 
Eric Boutilier
UUCP: uunet!fed!m1edb00
(202) 452-2734