Re:GS.Shrinkit v1.1

[ericlob@cris.com (ericlob)]

In article <69gsnl$555$1@darla.visi.com>, Nathan Mates <nathan@visi.com> wrote:
>In article <34BBF2A1.5EF3@library.ucla.edu>,  <pubpc1@library.ucla.edu> wrote:
>>It is ironic, really.  That GSHK SEA archive should have been
>>uploaded as a binary II wrapped NON-BSCITed file!  If that
>>had happened, then your telcom program should automatically
>>set the filetype to GS Program after downloading and auto-
>>unwrapping and you would have been able to double click it.

Hmm, someone finally came up with a valid (current) use for binary2 ;).

The GSHK archive could also have been encased in an auto-decoding text
wrapper like I wrote for BscIT, but that was more for my amusement than
any perceived benefit.

Speaking of BscIT, I'll be releasing a new version soon.

>   And that kinda assumes you're only getting GSHK to your GS thru a
>telcomm program. Given that the OS can't clean up after a binary II
>wrapper by default, anyone trying to sneakernet or Appletalk in that
>file woulda been out of luck. Better to tell folks to use a less buggy
>binscii program than shaft those whose file transfers don't go solely
>thru a comm program.

Gscii+ is cool and I keep it around for the few times I need to extract
binhexed files, but it is pretty slow. I haven't ever run into the bug
that you're talking about though.