Greg,

Try quote type L 8. It works for me.

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Stigers, Greg [And] [SMTP:[log in to unmask]]
> Sent: Friday, October 09, 1998 4:31 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] zips, SAMBA, and ftp types
>
> OK. I have a call in to HPRC about this, and will see where it goes. I
> worked with the engineer before on a rather nasty ftp problem before
> (where
> recommended but non-dependent NS patches solved the problem, and
> someone
> else's boss had held up the NS patches in the name of changing one
> thing at
> a time...). The engineer is sending the request a bit further up,
> although
> he was not encouraging that much would happen with it. I provide this
> on the
> remote chance that someone else moves binary files in batch with ftp,
> but
> still wants to access interactively them thru a SAMBA share.
>
> Here's the deal. The transfers work, using type bytestream. I get from
> an NT
> ftp server as type bytestream (more on this in a moment), and put to
> our box
> with SAMBA as type bytestream, and also put to another NT ftp server
> as type
> bytestream, and can open the file in WinZip anywhere I can see it.
> But. If I
> want to get or put FROM the NT side, there is no way to set type
> bytestream!
> What works is a binary send, with buildparms of
> ;REC=,,B;DISC=2147483647,32
> (thanks to Lars for responding with this idea).
>
> Now, one might wonder what happens on the remote host, MPE or NT, when
> one
> issues a type bytestream. With DEBUG on, the HP ARPA FTP Server
> responds
> "TYPE L 8", and the client responds "200 Type set to L (byte size 8)".
> When
> connected to an NT ftp server, and issue bytestream, the ftp client
> responds
> again with the message, "200 Type set to L", and status confirms that
> the
> ftp client is "Using byte-stream mode to transfer files.  (FTPINFO
> 60)",
> although the NT server does report "TYPE: BINARY, FORM: Nonprint;
> STRUcture:
> File; transfer MODE: STREAM", which does seem ambiguous, but does
> work.
>
> But what about going from NT WS to the 3000 as host? Can I get the
> 3000 host
> to behave the same as it does if I come from another 3000? No; the
> results
> are different. If I ask the host what types it supports with "quote
> help
> type", the HP ARPA FTP Server responds "214 Syntax: TYPE <sp> [ A | E
> | I |
> L ]". However, if I issue "quote type L" to set bytestream on the
> host, as
> seen when connecting between two 3000s, I get "504 TYPE command not
> implemented for parameter L" (E similarly fails; only A and I actually
> work). If I want to put a file on the host as a bytestream file, I
> cannot do
> it this way.