From:	CSBVAX::MRGATE!peter@hadrian.uwo.ca@SMTP  4-APR-1988 06:50
To:	ARISIA::EVERHART
Subj:	rexec 1 of 4


Received: from uwocc1.uwo.CA by CORNELLC.CCS.CORNELL.EDU ; Sun, 03 Apr 88 18:21:01 EDT
Received: from julian.uwo.ca by uwocc1.uwo.CA (Mailer X1.25) with BSMTP id
 0705; Sun, 03 Apr 88 18:17:56 EST
Received: by julian.uwo.ca (id AA12860); Sun, 3 Apr 88 17:12:48 est
Date: Sun, 3 Apr 88 18:11:22 EDT
From: Peter Marshall <peter@hadrian.uwo.ca>
Message-Id: <8804032211@myst.uwo.ca>
To: G. Eustace <G.Eustace@MASSEY.AC.NZ>, George D. Purvis <purvis@qtp.ufl.edu>,
        Glenn Everhart <Everhart%Arisia.decnet@CRD.GE.com>,
        John.Kimball@hadrian.uwo.ca,
        Honeywell Systems and Research Center <jkimball@src.honeywell.com>,
        Tim Russell <consult32%zeus@unlvax3>,
        Warren Boyd <wboyd@orion.cf.uci.edu>
Subject: rexec 1 of 4

The distribution of rexec for non-JNET/VMSDUMP sites consists of 4
separate mail messages:

        This introductory one (short)

        a VMS help file for the program (4k)

        the source files (a self unpacking .COM) (37k) and

        the uuencoded .EXE file rexec.exe (21k)

Note that uuencoded files don't always make it through some mail
systems intact.  BITNET/JNET links are notorious for stripping
trailing blanks.  Leading periods in lines can also cause problems to
older mailers.  I have another pair of routes known as atob and btoa
that I modified to work on VMS that avoid the trailing blanks
problems.  I could send out this if you have trouble with the
uuencoded file. (You need a C compiler for this code though).

I was able to recreate a working .EXE file when I transfered the
decoded file back to the VMS system using a binary FTP from the unix
machine on which the decoding was done.  I hope that this works for
you too.  Good luck.
---
Peter Marshall, Data Comm. Manager
CCS, U. of Western Ontario, London, Canada N6A 5B7
(519)661-2151x6032
pm@uwovax.BITNET; peter@julian.uucp; peter.marshall@uwo.ca

