Xref: utzoo alt.comp.compression:164 comp.compression:29 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!spool.mu.edu!munnari.oz.au!brolga!uqcspe!cs.uq.oz.au!warwick From: warwick@cs.uq.oz.au (Warwick Allison) Newsgroups: alt.comp.compression,comp.compression Subject: Re: Trying to get maximum compression Message-ID: <393@uqcspe.cs.uq.oz.au> Date: 25 Mar 91 04:47:12 GMT References: <1991Mar24.152106.6333@pegasus.com> <1991Mar25.002730.11027@cs.umu.se> Sender: news@cs.uq.oz.au Reply-To: warwick@cs.uq.oz.au Followup-To: alt.comp.compression Lines: 41 In <1991Mar25.002730.11027@cs.umu.se> dvldbg@cs.umu.se (Daniel Brahneborg) writes: >> Well, if it is a HEX file, why don't you try to compress it by taking two >>bytes and putting them into one byte (range 0-255)? >> >Get serious! He said it was a 32-byte HEX file, not a 80-byte ASCII file. >Where were you during the lessons about bits and bytes? click. click. click. WOOOOOOOOMPH. Flame on. Gee, this group is off to a good start. What make the term "hex file" mean "binary file" ? A "hex file" isn't anything `defined in the literature'. I think the respondant was more likely to be right in interpretting the stupid question in a way which is at least slightly worth answering. Personally, I just saw the question and brushed it off. Whoever posted the question did not understand what they were asking, so it's no use responding via news. e-mail them and explain that the question is a pile of poop. As it turned out, we have prompted quite some discussion, and I guess we have established ground level information. Anyway, I'm off to ask a real question... FFFFFFFFFFfffffffffizzzzzzzssss s ss s... POP! Flame off. Warwick. -- _--_|\ warwick@cs.uq.oz.au / * <-- Computer Science Department, \_.--._/ University of Queensland, v AUSTRALIA.