Subject: | |
From: | |
Reply To: | |
Date: | Fri, 29 Jan 1999 17:51:10 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi all,
Gilles Schipper <[log in to unmask]> wrote:
>Hi Doug,
>
>I just retreived tapecopy.tar to my pc from jazz as per your note.
>
>How do I upload it to my HP3000 and make it executeable?
>
>Appreciate any help. You may also want to cc the list as I'm sure others
>would be interested.
>
>Thanks.
FTP to the 3000 as binary into hfs an hfs file.
ftp> open hp3000
ftp> user doug.werth
ftp> bin
ftp> put c:\download]\tapecopy.tar /WERTH/PURGEME/tapecopy.tar
ftp> quit
Go into the shell and untar the archive file. Here is a sample session where
I did it. There may be other parameters to tar that get rid of the warnings
concerning setting UID/GID but since the files were there I didn't bother to
explore them.
:xeq sh.hpbin.sys -L
shell/iX> ls -l
total 145
-rwx------ 1 DOUG.WERTH WERTH 74240 Jan 29 22:39 tapecopy.tar
shell/iX> tar -xf tapecopy.tar
tar: blocksize = 20
tar: TAPECOPY: cannot set uid/gid: Invalid argument
tar: TPCPYSRC: cannot set uid/gid: Invalid argument
shell/iX> exit
<SEVEN> PURGEME.WERTH:listfile ./@,2
PATH= /WERTH/PURGEME/
CODE ------------LOGICAL RECORD----------- ----SPACE---- FILENAME
SIZE TYP EOF LIMIT R/B SECTORS #X MX
1B BA 60 2147483647 1 16 1 * .sh_history
NMPRG 128W FB 170 170 1 176 2 * TAPECOPY
79B FA 781 204800 1 512 2 * TPCPYSRC
128W FB 290 204800 1 304 1 8 tapecopy.tar
>
>BTW, how is this program different from the TCPY program that I've used
>quite successfully to copy STORE tapes to disk and back to tape. Never
>tried it with SLTtapes though.
I have not used TCPY so I really can't comment. I know that TAPECOPY works
great. The only thing I have found that it would not handle is a TurboStore
tape created with ;MAXTAPEBUF parameter and that is documented in the
comments section of the source program.
HTH. Have a great weekend.
Doug.
Doug Werth Beechglen Development Inc.
[log in to unmask] Cincinnati, Ohio
The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.
|
|
|