Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!ucbvax!agate!e260-3f.berkeley.edu!labc-3dc
From: labc-3dc@e260-3f.berkeley.edu (Andy McFadden)
Newsgroups: comp.sys.apple
Subject: Re: Shrinkit/Binary II stuff
Summary: Why?!?
Message-ID: <24631@agate.BERKELEY.EDU>
Date: 20 May 89 03:11:50 GMT
References: <8905190506.AA19084@obsolete.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 23

In article <8905190506.AA19084@obsolete.UUCP> delton@pro-carolina.UUCP (Don Elton) writes:
[ stuff thwacked ]
>                                  Perhaps comm programs should automatically
>package SHK files as Binary II if they aren't already in Binary II format at
>the time of an upload.  Upon download they would be extracted out of the
>Binary II file and ready for decompression with Shrinkit.  For folks with
>programs that don't do auto-binary II on uploads, Shrinkit should ideally let
>the user put the file into that format.

Why?  What's the point?

ShrinkIt can unpack BLU and ACU archives.  Why not just do the following:

1) Instruct the user to TURN OFF Binary II auto-extraction.
2) Instruct the user to unpack the file with ShrinkIt.

THAT'S ALL YOU NEED TO DO!!!

If you are *really* concerned about confusing the usr, have the comm
program check the first six bytes of the file for the "NuFile" header.  If
it finds that, have it store the file as type $e0/8002.  (or is it e0/0002?)

>INET: delton@pro-carolina.cts.com