[comp.sys.handhelds] TAR on a PC and detarring STAR-1.04.4.tar.Z

CW%APG.PH.UCL.AC.UK@CUNYVM.CUNY.EDU (05/27/91)

         Dear Roger Yee,

          First of all, thankyou for posting the PC UNUX utilities (by the
     way the uncompress works amazingly) , and so I no longer have to
     borrow somebodies account on a UNUX machine to uncompress file from
     abroad. However I can't get TAR to behave itself. So are there any
     UNUX users out there who can help me:

               I am in the directory C:\HP48\STAR and in this directory
     I have the file STAR.Z ( what I called STAR-1.04.4.tar.Z on my PC).
     I type

               C>UNCOMPRE STAR

     with UNCOMPRE.EXE in the current path and it works a while and
     STAR.Z dissapears and low and behold STAR is in the directory

     (about 3 times as large). I can only assume this would be the equivalent
     of STAR-1.04.4.tar on a UNUX machine after decompression (i.e. the Z is
     removed.) I then type

              C>TAR -x -f STAR

     and I get the response

              tar: .: Permission denied
              tar: .: Permission denied
              tar:..: Skipping to next fileheader

     and all that is extracted is the file MAKEFILE about 1.6K long (I don't
     think that is what is stored in the archive). So how do I extract the
     rest??????? Any comments and help would be greatly appreciated.

            Conrad W.

gingell@aurs01.UUCP (Mike Gingell) (05/28/91)

W%APG.PH.UCL.AC.UK@CUNYVM.CUNY.EDU writes:

"I can't get TAR to behave itself. So are there any UNUX users out there
who can help me"

I have had similar problems with tar programs for the PC. The problem
seems to be that they cannot untar sub-files with illegal PC file names
such as star.1.04.Z.  One tar prog I have asks for a replacement name
but does not seem to function properly when I give it one.  I have even
tried going in with a PC-Tools type program and editing sectors of the
file to change the names. When I do this tar ignores the files
presumably because a sum check is now invalid.

The solution would be for tar files to be posted with names obeying
some common constraints satisfying all likely destination machines.

Mike Gingell, Alcatel, Raleigh, NC USA  (919) 850-6444
UUCP:       ...!mcnc!aurgate!aurfs1!gingell
Internet:   gingell%aurfs1%aurgate@mcnc.org