HP3000-L Archives

October 1998, Week 1

HP3000-L@RAVEN.UTC.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:
"Stigers, Greg [And]" <[log in to unmask]>
Reply To:
Stigers, Greg [And]
Date:
Mon, 5 Oct 1998 12:58:26 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Here is what I am working with. We run a job to ftp get (binary) some large
ZIP files from an NT server, and we also send them to another NT server,
were we are able to open them with WinZip32, so that's working great. It
occurred to us to use SAMBA to make these available on our development box
where we run SAMBA/iX, so I configured a SAMBA/iX share. If we drag and drop
ZIPs from the LAN onto the SAMBA share, we can open the file with WinZip32.
But, if I ftp send (binary) those files from the one 3000 to the other 3000,
in the SAMBA shared account, I cannot open them with WinZip32. I have tried
sending them as bytestreams, and I tried converting them to bytestreams with
tobyte.

So I tried getting the file as type bytestream, and that will let me open
them with WinZip32. Is this the only way this will work? Do I need to use
type bytestream during the get? If so, how do I get files with an ftp client
that does not have a type bytestream? During bytestream mode, a quote STAT
shows TYPE: BINARY on the NT side. I tested the get - then put using type
bytestream, and at least that still works; I can open the resulting ZIP on
the NT server, as well as the copy on the 3000.

ATOM RSS1 RSS2