Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!SFAUSTIN.BITNET!Z4648252 From: Z4648252@SFAUSTIN.BITNET (Z4648252) Newsgroups: comp.sys.atari.st Subject: PACKER vs. DoubleClick's DCSquish Message-ID: <890909.21205810.030768@SFA.CP6> Date: 10 Sep 89 03:20:58 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 44 Hello all, I've received several comments regarding PACKER 2.0 and DoubleClick's DCSquish. In summary, comments have it that PACKER 2.0 typically compresses files more so than Squish without loss of execution speed. A kind soul also earlier provided a comparison chart illustrating the results of PACKER and Squisher on various programs. True enough, PACKER gave more compressed programs. However, in spite of that, I've had some problems with PACKER 2.0. Hopefully, I can create a list while on-line: 1) User interface for PACKER works but is not particularly friendly. a. User is unable to see backspace progress while correcting spelling if program name is fat-fingered. 2) No File Selecter Box is used for program choice. Bummer... 3) No attempt is made to provide for original program in the root directory. In other words, an error condition occurs if your OUTPUT program name is the same as that of the original (unless I've missed something which is probable and typically true of my detective work). 4) Compression result problems with PACKER 2.0 a. DCOPY SHELL program does not work properly with DCOPY program. Why? b. Many programs just didn't behave correctly or caused error messages. ------------------- In summary, in my usual "Dumb Joe End User" evaluation is that the interface for PACKER is terribly rough. DCSQuish's interface is intuitive. Fewer error conditions, if any, will occur with Squish. PACKER, when it does work, does a marvelous job, but it needs much more work, better error trapping which, in turn, would allow it to work with better predictability. When working with a hard drive that has several programs and applications, DCSquish will cut down on the time consumed in preparing these files. Indeed, DCSquish 'is fun' to use. PACKER is anything but fun. This is not to down PACKER, though. Experimentation will result in some excellent results with the program but Squish will result in a less frustrating session. As STers, I think that we can be thankful that utilities such as DCSquish and PACKER are available. We have a choice and a flavor. I prefer Squish, others will prefer PACKER. ENJOY!!! Larry Rymal in East Texas