MU-VMS Archives

March 1996

MU-VMS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Kent Covert <[log in to unmask]>
Reply To:
Miami University OpenVMS <[log in to unmask]>
Date:
Wed, 13 Mar 1996 08:00:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
In article <1996Mar12.191437@miavx1>, [log in to unmask] writes:
> Well, I've messed around and I think the problem is with the kermit transfer.
> When I download a binary file with kermit I just type "SEND filename"and
> everything works fine.  When I upload one I type "RECEIVE filename".  Is
 kermit
> defaulting to some non-binary mode when I use the RECEIVE command, and if so
> how can I change this?  I uploaded a file to the Vax and then downloaded it
> right away using the above commands and it became corrupted.  Please Help.
 
Kermit will try to guess the type of the file before transferring, but it
has been known to "guess" wrong.  Therefore, you should put Kermit in
binary mode to be safe if you know you'll be transferring a binary file.
The following command should do this:
 
    SET FILE TYPE BINARY
 
I would recommend issuing this command on the both MIAVX1 and on your
PC.
 
You could also issue the command:
 
    UNZIP -t fname.zip
 
at the $ prompt after you transfer the file.  This should test the
integrity of the zip file after you've transferred it to MIAVX1.  You may
also want to using UNZIP to unzip the file completely on MIAVX1 to test it
also.
 
--
                                     Kent Covert, Software Coordinator
                                     Miami Computing and Information Services
                                     Miami University, Oxford, OH
                                     [log in to unmask]

ATOM RSS1 RSS2