Re: 601 Install Disk??

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

In article <3it9ru$miv@nic.umass.edu>,
Ian D House <donut0@twain.oit.umass.edu> wrote:
> Hi, does anyone know why the system 6.0.1 Install disk keeps coming out
> corrupted when i get it from ftp.apple.com?  I got all the other disks fine
> and I've tried this one over and over but gshk allways says it's corrupted.

To eliminate any possible chance of there being something wrong with
the file, I've just FTPed it (in binary mode), downloaded it,
unBinSCIIed it, unshrunk it, and compared it to my existing 6.0.1
Install disk.  There were no problems, and the disk is identical.

I tried decoding it using my own DESCII program, and also with GSCII+.
No problem in either case.  I also tried decoding it with SCIIBIN and
extracting with NULIB.  No problem there either.

The "install.bsc" file is 711096 bytes long.  The contained ShrinkIt
file "install.601.bxy" is 520576 bytes long.  It is a standard NuFX in
Binary II file, not a self-extracting archive or anything else
unusual.  Inside the ShrinkIt file is an 800k disk image of the
"Install" disk.

If transferred in binary mode, the "install.bsc" has line feed
characters on the end of each line, and no carriage returns.


I cannot think of any reason why an ASCII transfer would fail.  If you
transfer it in ASCII mode, the end of line characters will depend on
the convention used on your Internet host.  In any case, all BinSCII
decoders should cope with any end of line convention.

This is the largest of the files, so it seems that the most probable
cause is something causing data corruption in largish files.  I am
surprised that no error was reported by the BinSCII decoder in this
case.  The only case I can think of where no error would be indicated
until extracting with GSHK would be if a BinSCII segment was missing.

If you were using ASCII transfers (the default when using the standard
UNIX FTP program), try doing a binary transfer instead (enter the
BINARY command before using the GET command to get the file).

If you were using a binary transfer, I can only suggest that there is
a data corruption problem or bug somewhere in your communications
software or some utility you are using.  This doesn't seem very
likely, as other people have had problems with this disk.
-- 
David Empson
dempson@actrix.gen.nz
Snail mail: P.O. Box 27-103, Wellington, New Zealand