Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!lll-tis!lll-lcc!ptsfa!nonvon!gilsys!mc68020
From: mc68020@gilsys.UUCP (Thomas J Keller)
Newsgroups: comp.sources.d
Subject: Re: Problems with Compress
Message-ID: <1131@gilsys.UUCP>
Date: Tue, 6-Oct-87 11:07:08 EDT
Article-I.D.: gilsys.1131
Posted: Tue Oct  6 11:07:08 1987
Date-Received: Sun, 11-Oct-87 13:53:36 EDT
References: <13006@bu-cs.BU.EDU> <780@sugar.UUCP> <1493@cognos.UUCP> <4786@ncoast.UUCP>
Organization: Consequently Computers, Santa Rosa, Ca
Lines: 27
Summary: I dunno...my Tandy handles them just fine!

In article <4786@ncoast.UUCP>, allbery@ncoast.UUCP (Brandon Allbery) writes:
> As quoted from <1488@geac.UUCP> by satan@geac.UUCP (The Big One Himself):
> +---------------
> | In article <1493@cognos.UUCP> brianc@cognos.UUCP (Brian Campbell) writes:
> | >In article <780@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> | >! Will people who compress stuff for distribution PLEASE use 12-bit. 16-bit
> | >! uses a huge amount of memory and may not even be available on small machines
> | >! like PDP-11s and Intels.
> Nor are small machines alone.  Ncoast has fried its cache chips a few times
> as a result of 16-bit compresses... 68000, NOT an Intel or PDP-11!

   As I stated in my summary, I cannot imagine a smaller 68000 based machine
than the Tandy 6000, and my Tandy handles 16 bit compress/uncompress just fine.
I have to admit that I couldn't handle more than 13bits until I learned how to
patch my kernal to permit >256K user process limits, but once I did that, 
ZIPPETY-POW!, off it went!  (the ZIPPETY-POW!, by the by, comes from one
Katy the Caterpillar (Disney CHannel), to give attribution where attribution
is due)

   Brandon, if you are SERIOUS about 16 bit compresses causing hardware
failures, I strongly suggest that there is a ***MAJOR*** flaw in the design
of your hardware.

-- 
Tom Keller 
VOICE  : + 1 707 575 9493
UUCP   : {ihnp4,ames,sun,amdahl,lll-crg,pyramid}!ptsfa!gilsys!mc68020