Path: utzoo!utgpu!water!watmath!clyde!wtr@moss.ATT.COM
From: wtr@moss.ATT.COM
Newsgroups: comp.sources.d
Subject: Re: Standard for file transmission
Keywords: protocol compression source
Message-ID: <25816@clyde.ATT.COM>
Date: 3 May 88 19:34:18 GMT
References: <292@cullsj.UUCP> <55@psuhcx.psu.edu>
Sender: nuucp@clyde.ATT.COM
Reply-To: wtr@moss.UUCP (Bill Rankin)
Organization: AT&T Bell Laboratories, Whippany NJ
Lines: 30

In article <55@psuhcx.psu.edu> wcf@psuhcx (Bill Fenner) writes:
>Just one thing that needs to be known -- PC's can do no more than
>12-bit compression.  So if you are compressing your file from a
>UNIX system, you need to say comress -b12 filename. 

Sorry, but....

The posted patches for compress(4.0) to get it running on a 
Microport SV/AT (286) system have the patches to allow full 16-bit
compression on a 16-bit PC (an AT clone, in this case) It should not
prove too difficult to apply these patches to any other 16-bit
System (read: MS-DOS).

{ No flames intended, it took me ~1 month to figure out the 12/16
bit problem and locate the patches } 

Personally, I use cpio & compress to move files.  I don't care 
about execution time, rather transmission time is my most important
consideration, and so I desire the highest compression ratio I can
find.  I agree that for "real time" communication, compress is
totally inaddiquate because of it's processing needs.

=====================================================================
Bill Rankin
Bell Labs, Whippany NJ
(201) 386-4154 (cornet 232)

email address:		...![ ihnp4 ulysses cbosgd allegra ]!moss!wtr
			...![ ihnp4 cbosgd akgua watmath  ]!clyde!wtr
=====================================================================