Re: GSHK bug found

[johnlb@primenet.com (John Bowling)]

In article <5i7h9h$9je$1@darla.visi.com>, Nathan Mates <nathan@visi.com> wrote:
>Ok, I've been sitting on this bug for a while, and just spent a few
>hours trying to squash it. Essentially compressed files of size zero
>bytes (output file size, not .SHK file size) cause GSHK to give a
>corrupted file error. You can continue on with the next file, and
>decompress from there, or delete the empty file from the archive and
>go on from there. 

There is another problem with GSHK that I run into on occation.  It will
sometimes expand a file but fail to write it out, and will crash the
system when it does.  Usually I've found that the archive file was
corrupted in some way (not detected by GSHK), but that should not make
GSHK crash.  GSHK usually will detect corrupt files and will either say
the file is corrupt or that the checksum doesn't match.  When this error
occurs, files after the bad one can be decompressed if you begin after
the bad one, once you've rebooted.  One good thing with this problem,
it doesn't seem to leave a partial file anywhere (but it might be
allocating disk space that will then be lost).

If Andy is willing to work on GSHK, I request that he puts in a way of
writing a DSK file (one that contains a ProDOS directory) out to a hard
drive as a directory and not force use of a disk.

John

--
--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--
- John Bowling          -- Shouldn't you be commuting by bicycle?
- johnlb@primenet.com   -- No, that's not a valid excuse!
--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--