[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why *.bsq.Z - How about *.SHK ?



In article <C7nnJq.7L7@news.cso.uiuc.edu> kls0@uxa.cso.uiuc.edu (Kent Squires ) writes:
> 
> I've never had GScii hose a .SHK file...a .SEA file, yes.

There are at least two bugs in GSCII (and SSCII, the shell-based
version of the same program):

1. When compressing files, it munges the auxiliary type if the most
significant bit is set.  For example, a ShrinkIt archive (auxtype
$8002) gets turned into auxtype $8102.

2. When decompressing files, it rounds the file length up to the next
multiple of 48 bytes.

This isn't a problem for ShrinkIt, since the extra bytes contain zero.
It is a problem for SEA files, since the System Loader can't interpret
the extra data on the end of the file (it thinks there is another
program segment with a damaged header).
-- 
David Empson                                                               
dempson@swell.actrix.gen.nz                                                
Snail mail: P.O. Box 27-103, Wellington, New Zealand