Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!uc!noc.MR.NET!gacvx2.gac.edu!hhdist
From: CW%APG.PH.UCL.AC.UK@CUNYVM.CUNY.EDU
Newsgroups: comp.sys.handhelds
Subject: Uncompress and Tar on PC...
Message-ID: <49B10EBBC0001259@gacvx2.gac.edu>
Date: 4 Jun 91 12:14:53 GMT
Article-I.D.: gacvx2.49B10EBBC0001259
Lines: 31
Return-path: <@CUNYVM.CUNY.EDU:CW@APG.PH.UCL.AC.UK>
To: HANDHELDS@gac.edu
Via:      UK.AC.UCL.PH.APG;  4 JUN 91 12:28:08 BST


     Hi again,
       Thanks to the people that gave advice to me on using the
     Uncompress, Tar etc for the PC that were posted to the board a
     while back. The following information may be useful to those
     using them.
       I find it necessary to include the -i qualifier in the uncompress
     command, otherwise 'tar' does not seem able to cope with the
     uncompressed file, e.g.

                       C:>uncompre -i 'filename'

     Does anybody know why, since it does notexplain what -i means
     anywhere? When I untar the file I use the command line

                       C:>tar -xf 'filename'

     which 'seems' to work. By 'seems' I mean that executables seem
     to work and ascii files become ascii files...HOWEVER...The executables
     behave a bit oddly (I won't go into this) and the ascii files
     are untarred as one very long line with the line feed/carriage returns
     subsituted with funny coloured 'J' characters. The text is all intact
     but it appears that the control characters are not understood. I have
     tried a lot of different qualifiers for both Tar and uncompre but
     they either don't work or do work with the above problems...

                             Any ideas?

        Thanks for listening


            Conrad