Xref: utzoo comp.sources.d:2022 comp.binaries.ibm.pc.d:100
Path: utzoo!mnetor!uunet!husc6!maynard!campbell
From: campbell@maynard.BSW.COM (Larry Campbell)
Newsgroups: comp.sources.d,comp.binaries.ibm.pc.d
Subject: Re: Standard for file transmission
Message-ID: <1082@maynard.BSW.COM>
Date: 4 May 88 23:36:07 GMT
References: <292@cullsj.UUCP> <55@psuhcx.psu.edu> <4740@teddy.UUCP>
Reply-To: campbell@maynard.UUCP (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 21
Keywords: protocol compression source

In article <4740@teddy.UUCP> jpn@teddy.UUCP (John P. Nelson) 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 .
<>
<>This myth has been repeated several times, so I felt it was necessary to
<>speak up.  PCs most certainly CAN do a 16 bit compress/uncompress.  ...

Only a subset of PCs can do 16-bit compress/uncompress.  Mine can't.
I'm running VENIX/86 2.0, which is basically V7;  the PCC-derived
C compiler has only the tiny and small memory models (exactly
corresponding to non-split and split PDP-11s, which also cannot
handle 16-bit compress).

So it is true that PCs with a C compiler that supports multiple data
segments can handle 16-bit compress, but that hardly encompasses all
PCs in the world.
-- 
Larry Campbell                                The Boston Software Works, Inc.
Internet: campbell@maynard.bsw.com          120 Fulton Street, Boston MA 02109
uucp: {husc6,mirror,think}!maynard!campbell         +1 617 367 6846