Re: Transfering Executables to a VAX by a tortuous route - help please
From: Alan Greig (greigaln_at_netscape.net)
Date: 03/12/05
- Next message: Joe Database: "comparison: Rdb vs. Mimer"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: Mozilla suite freezing; whats to become of HPSWB?"
- In reply to: Jeff Cameron: "Re: Transfering Executables to a VAX by a tortuous route - help please"
- Next in thread: Jeff Cameron: "Re: Transferring Executables to a VAX by a tortuous route - help please"
- Reply: Jeff Cameron: "Re: Transferring Executables to a VAX by a tortuous route - help please"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 12 Mar 2005 05:33:50 -0800
Jeff Cameron wrote:
> If you don't have an IMAGE transfer file type, you can still use
binary and
> then enter in the VMS command:
>
> $SET FILE/ATTRIBUTE=(RFM:FIX,LRL:512) executable-file.EXE
Unfortunately not with Kermit-32 as it used 510 byte RMS records when
storing in binary mode. Of course you can convert the record format but
just changing the attribute won't work.
-- Alan Greig
- Next message: Joe Database: "comparison: Rdb vs. Mimer"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: Mozilla suite freezing; whats to become of HPSWB?"
- In reply to: Jeff Cameron: "Re: Transfering Executables to a VAX by a tortuous route - help please"
- Next in thread: Jeff Cameron: "Re: Transferring Executables to a VAX by a tortuous route - help please"
- Reply: Jeff Cameron: "Re: Transferring Executables to a VAX by a tortuous route - help please"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]