Will@cup.portal.com (Will E Estes) (05/12/91)
I'm probably missing something obvious, but today while doing
an FTP from a UNIX machine to a PC I was unable to transfer
files that had been both TARred and COMPRESSed. These files
were of the form <name>.tar.Z. Upon issuing the GET command
from the PC I got a message "Unable to open file". This was
using Wollongong's WIN/TCP For DOS. Is the inability to deal
with a three-part name a failure of the WIN/TCP product, or
is there a trick I can use here to get the file over to my PC?
Thanks,
Will Estes Internet: Will@cup.portal.com
UUCP: apple!cup.portal.com!Willsanders@gpu.utcs.utoronto.ca (Terry P Sanderson) (05/12/91)
In article <42236@cup.portal.com> Will@cup.portal.com (Will E Estes) writes: >I'm probably missing something obvious, but today while doing >an FTP from a UNIX machine to a PC I was unable to transfer >files that had been both TARred and COMPRESSed. These files >were of the form <name>.tar.Z. Upon issuing the GET command >from the PC I got a message "Unable to open file". This was >using Wollongong's WIN/TCP For DOS. Is the inability to deal >with a three-part name a failure of the WIN/TCP product, or >is there a trick I can use here to get the file over to my PC? Will, Try the command: get <name>.tar.Z <newname>.Z DOS really doesn't like filenames with multiple extensions (obviously), so the above command renames the file on the way over. We have this problem FTP'ing from a VM host to our PC's, where the default name is <filename> <filetype>, where each can be 8 chars long. Terry Sanderson Supervisor, Microcomputer Specialists University of Toronto Computing Services sanders@gpu.utcs.utoronto.ca
Will@cup.portal.com (Will E Estes) (05/13/91)
<I'm probably missing something obvious, but today while doing
<an FTP from a UNIX machine to a PC I was unable to transfer
<files that had been both TARred and COMPRESSed. These files
<were of the form <name>.tar.Z. Upon issuing the GET command
<from the PC I got a message "Unable to open file".
Yes, I was missing something obvious. The GET command takes
an optional second argument in case you don't want to use the
host filename as the template for the filename on the receiving
system (i.e., GET <fromfile> (<tofile>) ). Supplying the
<tofile> solved my problem. Thus, the correct command was:
GET asuperlongfilename.tar.Z tiny.taz
Thanks,
Will Estes Internet: Will@cup.portal.com
UUCP: apple!cup.portal.com!Willmark@TELESYS.NCSC.NAVY.MIL ("Mark L. Williams") (05/13/91)
Will Estes writes... >I'm probably missing something obvious, but today while doing >an FTP from a UNIX machine to a PC I was unable to transfer >files that had been both TARred and COMPRESSed. These files >were of the form <name>.tar.Z. Upon issuing the GET command >from the PC I got a message "Unable to open file". This was >using Wollongong's WIN/TCP For DOS. Is the inability to deal >with a three-part name a failure of the WIN/TCP product, or >is there a trick I can use here to get the file over to my PC? > >Thanks, >Will Estes Internet: Will@cup.portal.com > UUCP: apple!cup.portal.com!Will The problem _is_ kind of obvious when you hear what it was... DOS filenames must be filename.ext. There's no way to have two dots in a local PC filename. You'll have to use a GET remotefile localfile syntax, giving a legal local file name for the PC. I think that'll solve your problem. Mark
rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) (05/17/91)
In article <42236@cup.portal.com> Will@cup.portal.com (Will E Estes) writes: >I'm probably missing something obvious, but today while doing >an FTP from a UNIX machine to a PC I was unable to transfer >files that had been both TARred and COMPRESSed. These files >were of the form <name>.tar.Z. Upon issuing the GET command >from the PC I got a message "Unable to open file". This was >using Wollongong's WIN/TCP For DOS. Is the inability to deal >with a three-part name a failure of the WIN/TCP product, or >is there a trick I can use here to get the file over to my PC? > Try the following: ftp> binary ftp> get file.tar.Z file.taz the first command sets ftp into binary mode (needed for .Z files) the second says to get the file file.tar.Z and store on the PC as file.taz -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com