Re: BINSCII problems...

[rubywand@aol.com (RUBYWAND)]

In article <dmz-2202961231520001@babylon.caltech.edu>, dmz@cco.caltech.edu
(Daniel Zimmerman) writes:

>
>I believe the version at Caltech is correct, and as soon as I put the
>archive back up (should be any day now, I'm just waiting on the copy of
>Shrink II that has been generously donated to the archive by Diz at EGO
>Systems), the person who needs it can grab it from there...
>
>

    That should take care of that.

    However, there is another problem which has nothing to do with
availability. Both GSCII (v2.3.1) and BINSCII (v1.0.3) seem have a fairly
serious bug: they incorrectly encode some self-extracting GSHK files which
include some Teach files. This can cause the decoded self-extracting file
to bomb.

    Evidently, the bug is most likely to appear when encoding text stuff
and may mess up any GSHK archive which includes Teach, Text, etc. files.
(The BINSCII 1.0.3 docs do mention a problem with white spaces in text.)

    Perhaps someone knows: has the bug has been fixed?

   

Rubywand