Re: Getting files from Caltech

[dempson@actrix.gen.nz (David Empson)]

Edhel Iaur, Esq. <drsmooth@relex.com> wrote:

> If the subject of this message hasn't annoyed everyone away already, I
> would like to know if there's an article somewhere that has the
> instructions for fixing those files from the caltech site.  Is it in
> the site, or in the FAQ?

I just tried downloading a test file from Caltech to see if there was
anything strange about it.  The file was:

ftp://apple2.caltech.edu/Zocalo/pub/utils/about.shk

This is my ABOUT utility for the IIgs.  The file has been updated since
I last looked at it (it was dated September 1996, but it was originally
placed on Caltech several years ago and has not been updated since), so
the archive was probably recreated or modified at this time.

I used Fetch on a Mac, with the transfer mode forced to Binary.  It came
through fine, and a dump of the header revealed it to be a straight
ShrinkIt file, without a Binary II header.  

This means that it will end up on an Apple II without a meaningful file
type, but ShrinkIt (or any other NuFX extractor) will be able to handle
it fine (you might need to tell ShrinkIt to "show all files", not just
ShrinkIt files).

I was able to decode it using Shrink II on the Mac, and I would not
expect any problems if I tried it on UNIX (nulib) or the IIgs (ShrinkIt,
IIPlus.Unshrink, GShk, Yankit or Balloon).


If anyone is having problems dealing with a file downloaded from Caltech
(or another FTP site), make sure you using BINARY mode for the transfer
(not ASCII mode).  If you are using a web browser (e.g. Lynx), this is a
little tricky - Lynx defaults to ASCII mode unless it recognises the
file extension (this involves a special file in your home directory on a
UNIX shell account, and probably has similar mechanisms on other
systems).  To be sure you are transferring the file correctly, use a
standard FTP client, if possible, and make sure you tell it to do binary
transfers.

If you still can't get it to work, by all means post a message here, but
state PRECISELY which file you are having trouble with, and the exact
sequence of steps (and applications) used to get it to the Apple II, so
that other people can at least tell you that it is a problem with the
method you are using to transfer or decode the file, not a problem with
the file itself.

-- 
David Empson
dempson@actrix.gen.nz
Snail Mail: P.O. Box 27-103, Wellington, New Zealand