Xref: utzoo comp.binaries.ibm.pc.d:1295 comp.sys.ibm.pc:21005
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!labrea!rutgers!bellcore!clyde!watmath!watcgl!watmum!rmpinchback
From: rmpinchback@watmum.waterloo.edu (Reid M. Pinchback)
Newsgroups: comp.binaries.ibm.pc.d,comp.sys.ibm.pc
Subject: Re: WARNING! Vicious bug in GSARC
Keywords: GSARC, Archivers, Compression, Bugs
Message-ID: <6634@watcgl.waterloo.edu>
Date: 7 Nov 88 04:18:53 GMT
References: <6627@watcgl.waterloo.edu> <42285@yale-celray.yale.UUCP>
Sender: daemon@watcgl.waterloo.edu
Reply-To: rmpinchback@watmum.waterloo.edu (Reid M. Pinchback)
Organization: U. of Waterloo, Ontario
Lines: 26

In article <42285@yale-celray.yale.UUCP> spolsky-joel@CS.YALE.EDU (Joel Spolsky) writes:
>In article <6627@watcgl.waterloo.edu> rmpinchback@watmum.waterloo.edu (Reid M. Pinchback) writes:
>>As a result, I often end up with updated
>>archives that are 20-25% LARGER than they were with ARC or PKARC.  
>>
>>      Reid M. Pinchback
>
>Compressing what kind of files? 
>
>+----------------+---------------------------------------------------+
>|  Joel Spolsky  | bitnet: spolsky@yalecs     uucp: ...!yale!spolsky |
>|                | arpa:   spolsky@yale.edu   voicenet: 203-436-1483 |
>+----------------+---------------------------------------------------+

First:  All kinds of files are compressed the same way.
Second: The kinds of files where this seems to be a problem, appear to be
        text files, but I'm not yet sure exactly what kind of content
        causes the lousy compression.  I first noticed it when trying to
        archive a uuencoded archive (please don't ask why, its a
        long story) :-)
        Since then, I've noticed it cropping up often when I've been re-arcing
        some of the various archives i've had laying around on my hard disk
        for eons, these archives primarily being mixed text and executable
        binaries.


   Reid M. Pinchback