Copying file(s) from DOS/Windows to HPUX

[Chris Bidwell]

Is there a way that you can copy a file (tar file) or even FTP the file from my Win2000 workstation into my HPUX box? i.e. the send [file] command...I'm not sure if there is a special switch that will allow it to be read in hpux or not. My dilemma is that I have a tar file that I downloaded in 2000 and I'm trying to FTP it to my HPUX box. It sends fine but when I try to untar it, it displays errors. Is there a DD command or something that will allow this to work properly? Thank you.

[Paula J Frazer-Campbell]

Hi
Try setting your ftp session to binary:-

ftp xxx.xxx.xxx.xxx
login- etc

>binary
>put filename
>quit

HTH

Paula

[Jim Turner]

Make sure you switch to binary mode before you transfer the file. To wit:

C:\>ftp neelix # hp-ux box
Connected to neelix.hertz.com.
220 neelix FTP server (Version 1.1.214.4 Wed Aug 23 03:38:25 GMT 2000) ready.
User (neelix.hertz.com:(none)): your-id
331 Password required for your-id.
Password: ********
230 User your-id logged in.
ftp> cd /tmp
250 CWD command successful.
ftp> bin # here's the important one for you
200 Type set to I.
ftp> hash
Hash mark printing On (2048 bytes/hash mark).
ftp> put some-file.tar
200 PORT command successful.
150 Opening BINARY mode data connection for some-file.tar.
########
226 Transfer complete.
32749 bytes sent in 0.05 seconds (654.98 Kbytes/sec)
ftp> bye
221 Goodbye.

[Chris Bidwell]

Thanks for the info....the is the error that I'm getting. I change the format to binary and type put hp1aa_ml.tar /netprin. The transfer goes fine. I attempt to untar the file: tar xf hp1aa_ml.tar. The output is (directory checksum error). Any ideas? Thanks

[Paula J Frazer-Campbell]

Hi

Does the file "untar" and then produce the error?

Meanwhile tar error codes:-

NOTE: exit code is considered as 'NONFATAL_ERRCODE'

exit(0)
no error & no warning.

exit(1)
Tar: cannot create temporary file (%s)
Invalid blocksize. (Max %d)
tar: blocksize %d too big, can't get memory
tar:Invalid or non-existent device file %s
Can only create standard output archives
tar: cannot open %s
tar: option not supported for this device %s
tar: cannot write to %s: write protected
tar: usage tar [-]{txruc}[eONvVwAfblhm{op}][0-7[lmh]] ......
Attempt to create archive of no files. Nothing dumped.
tar: cannot preserve extent attributes for %s. aborting...
Tar: cannot create temporary file (%s)
Invalid blocksize. (Max %d)
tar: blocksize %d too big, can't get memory
tar:Invalid or non-existent device file %s
Can only create standard output archives

exit(2)
directory checksum error
tar: %s: HELP - extract write error
tar: Cannot close %s
Tar: tape write error

exit(3)
Tar: tape read error
Tar: tape blocksize error
Tar: blocksize = 0; broken pipe?
Tar: error! blocksize changed

exit(4)
Tar: tape backspace error
Tar: ioctl to write filemarks failed (%d). aborting...
Tar: ioctl to determine device online failed. aborting...

exit(5)
tar: Cannot change directory to '%s'
tar: Path '%s' skipped
tar: cannot open %s
Missing links to %s
tar: %s: cannot access file
tar: Out of memory. Cannot detect symbolic link loops
tar: Loop of symbolic links detected, tar terminated
tar: cannot stat %s. Not dumped.
tar: Size of %s > %s. Not dumped.
tar: %s: directory read error
tar: %s: directory read error
tar: %s: symbolic link too long
tar: can't read symbolic link
tar: %s: cannot open file
tar: %s: link to name too long
Out of memory. Link information lost
%s: file changed size
tar: %s is not a file. Not dumped
tar: %s: symbolic link failed
%s: cannot link
tar: %s couldn't create character device
tar: %s couldn't create block device
tar: %s couldn't create fifo
tar: %s couldn't create directory
tar: %s couldn't create directory
tar: %s - cannot create
tar: chmod failed
tar: chown failed
tar: couldn't get uname for uid %d
tar: couldn't get gname for gid %d
tar: pwd failed
tar: %s: pathname too long
tar: %s: prefix too long
tar: %s: file name too long
%s: file name too long

NOTE: exit code is condsidered as 'NONFATAL_ERRCODE'

[Patrick Wallek]

It looks like you are trying to put the file onto a directory that already exists. I assume /netprint is the directory you want the file in?

After you bring up ftp and get logged into your machine, do this:

bin
cd /netprin
put hp1aa_ml.tar

Quit out of FTP and then go back to your HP-UX system and try to untar the file. Try this first on the system:

# cd /netprint
# tar -tvf ./hp1aa_ml.tar

If you see the contents of the file scrolling up the screen the the file is good. The 'tar -tvf....' prints a listing of the tar file, it does NOT extract anything.

At this point if the tar file is good you can do:

# tar -xvf ./hp1aa_ml.tar


Hope this helps you.

[Paula J Frazer-Campbell]

Hi
Also try tar -xvf and see where it errors out.

Paula

[Chris Bidwell]

I did everything as mentioned and still come up with the directory checksum error. Is this because this is in a DOS formatted tar file? Does it have to be directly download from the FTP site for this to work. I'm thinking maybe since this is originally being downloaded on a x86 system that it formats the file as such....

[Paula J Frazer-Campbell]

Hi
Tar files are multi platform,
although your problem could be the download, can you pick it up from the server or via ftp from you windows machine?

Paula

[Sachin Patel]

Hi Bidwell,
I have same problem on my PC. It was working before and then it stops suddenly. I have always checksum error now. It might be one of the window installations. I don?t recall why and how this happen.
So I go around. I launch Netscape from one of my Unix box display back to my PC and download my .tar file directly in to the Unix box.

Sachin

[Mark Vollmers]

Christopher-

An alternative to FTPing the file is to use a file sharing program. We use DiskAccess to move from the NT stations to UNIX, and I know that I have seen threads here where people have listed a number of other programs (search for mounting NT, maybe?. I don't know if that is worth it or not, depends on the number and frequency of files being moved (we do it becuase we move a lot of files back and forth and backup a few NT folders to boot on UNIX).
Just a thought.

Mark