nftcon@log-hb.se (Conny Ohstr|m) (09/10/89)
I have found something strange with 'compress' if I try to compress already packed files (done with ZOO), then the compress program bails out, but it dosent show any error messages beccause there is a 'signal()' catch in the program. In my computer (SUN386i) the backupprogram 'bar' (bar=compress+tar) tries do compress the file and then rename it to the old name without .Z on the end. and then put it on the tape. however the compress bails out in a strange way so the bar program cant handle it. by looking in a PD version of compress I have found what the fault it: the 'HSIZE' is too low for 16BITS compression. The source says '#define HSIZE 69001' (if BITS == 16) but I have found that you need (atleast) '#define HSIZE 80001' (if BITS == 16) how do you see this bug? 1) take any file, a bunch of joined usenet-texts will do 2) pack them with zoo 'zoo a test junkfile' you got test.zoo 3) then do compress 'compress -v test.zoo' 4) then can three thing happen: 1) a correct report, meaning this file dosent show the bug, or you have fixed this bug already. 2) a boug report as in 'test.zoo: {yourshellprompt}' as if the program bailed out. Now I wounder "how is the formula to calculate the HSIZE for all the BITS combinations?" ANY misspelling are caused by a bad line, and I cannot be responsible for ANY misspellings above .... Conny Ohstrom televerket farsta HK farnebogatan 81-87 s-123 86 sweden phone: +46 8 713 40 31 usenet:nftcon@log-hb.se