Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rutgers!aramis.rutgers.edu!porthos.rutgers.edu!friedman From: friedman@porthos.rutgers.edu (Gadi ) Newsgroups: comp.sys.apple Subject: Re: .tar.Z Message-ID: Date: 27 Jun 89 15:13:04 GMT References: <8906260924.aa01054@SMOKE.BRL.MIL> <10458@smoke.BRL.MIL> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 21 In article <10458@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes: > The hash table is used only for compression, not decompression. > It's a standard LZW scheme, most likely using 16-bit codes. > An Apple IIGS should have enough room to uncompress it. > However, your best bet is to transfer the file to a real computer > and do the work there. Well, from what I undestand (and I am looking at the source) it is a dynamic LZW scheme. It starts out using 9-bit codes, and can go up to 12-16 depending on compiler flags (with 12 bits used on 16bit machines). It also has provisions for clearing the table, if it gets too full. Your probably right about the hash tables, though, I can't really tell. The code contains too many macros and #ifdefs Gadi -- uucp: {ames,att,harvard,ucbvax,iuvax}!rutgers!aramis.rutgers.edu!friedman arpa: FRIEDMAN@ARAMIS.RUTGERS.EDU