Path: utzoo!attcan!uunet!loft386!dpi
From: dpi@loft386.uucp (Doug Ingraham)
Newsgroups: comp.unix.sysv286
Subject: compiling compress (Was Re: how to compile pcomm in sysv)
Summary: Its a trick for 286 xenix
Message-ID: <1990Oct29.022804.20088@loft386.uucp>
Date: 29 Oct 90 02:28:04 GMT
References: <1990Oct22.092129.1@acad3.fai.alaska.edu> <501@tndsyd.oz> <917@iiasa.UUCP>
Organization: Lofty Pursuits Public Access Unix for Rapid City, SD USA
Lines: 23

In article <917@iiasa.UUCP>, wnp@iiasa.AT (wolf paul) writes:
> In article <501@tndsyd.oz> berny@tndsyd.oz (Berny Goodheart) writes:
> )The 286 is only capable of compressing to 12 BITS. Most
> )32 bit machines compress files to 16 bits. If the files you are trying
> )to de-compress where originally compressed on a 32 bit machine, ...
> 
> Apart from the fact that I have used a 16-bit uncompress on a 286
> several years ago, the reply above does not seem to have anything to
> do with the question it purports to answer. What is going on?
> 
There is an option in compress to allow the big array to be broken
into 64k chunks that will fit on a xenix box.  I think these patches
are ifdef XENIX although it has been a couple of years since I looked at
it.  Look at the sources for a couple of minutes and you will see what I
mean.  I have never used compress in this way, so I don't know if it
really works, but I saw nothing that would prevent it from working on 
any 286 system that allowed large model data segments.


-- 
Doug Ingraham (SysAdmin)
Lofty Pursuits (Public Access for Rapid City SD USA)
uunet!loft386!dpi