Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!hellgate.utah.edu!cc.utah.edu!cc.usu.edu!jrd
From: JRD@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Kermit with FIXED FILE TYPE
Message-ID: <11748@cc.usu.edu>
Date: 21 Nov 89 01:49:50 GMT
Lines: 13

Andy,
        Perhaps someone has responded already to your problem with tranferring
VMS executables to MS-DOS machines and back to VMS, using Kermit. The intrinsic
problem is that VMS executables are not simple flat files, yet MS DOS supports
only a flat file system. Thus the gotcha will exist with any of the comms
programs. Solution: put the VMS executables in a DEC Saveset, on Kermit-32
(the VMS side) say SET FILE TYPE BINARY, get them to the PC with MS Kermit,
and later reverse this process, and finally use VMS BACKUP to unpack the
Saveset. Kermit-32 needs the SET FILE TYPE BINARY command whereas MS Kermit
does not (and does not even have it in all the current releases). As you
gather, Savesets are flat archive files and can hold just about anything
at all.
        Joe D.