Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!mephisto!udel!princeton!phoenix!kadickey
From: kadickey@phoenix.Princeton.EDU (Kent Andrew Dickey)
Newsgroups: comp.sys.apple
Subject: Re: ProDOS HyperC
Message-ID: <13558@phoenix.Princeton.EDU>
Date: 4 Feb 90 02:57:33 GMT
References: <1990Feb3.013555.3252@eng.umd.edu> <2054@psuhcx.psu.edu>
Reply-To: kadickey@phoenix.Princeton.EDU (Kent Andrew Dickey)
Organization: Princeton University, NJ
Lines: 36

In article <2054@psuhcx.psu.edu> llp@psuhcx.psu.edu writes:
>In article <1990Feb3.013555.3252@eng.umd.edu> cyliao@eng.umd.edu (Chun-Yao
Liao) writes:
>|Had anyone successfully downloaded and unpacked the ProDOS HyperC from
>|ftp site plains.nodak.edu?  I tried 2 times, but when unshrink the disk, I
>|got internal error #81. Yes, I used binary mode while transfering using FTP.
>|I used kermit and xmodem to download file.
>
>Same here. I used binary mode from the ftp site and tried xmodem, ymodem,
>zmodem, and kermit.  None of them worked.  I also got the internal error #81.
>I sent mail to the person that's address was given in the file hyperc.READ to
>notify them of this problem.  
>
>	Laura

I sent the original uploader E-mail expaling what he did wrong, but he
has not replied yet...

What happened was he uploaded the binary file using some transfer
protocol that thought it was a text file--so all the returns in the file
($0D) become return-linefeed pairs ($0D $0A).  Needless to say, this has
sufficiently munged the files to make them unuseable.  (I wrote a
program to convert all $0D, $0A pairs into just $0D, but even the
converted copy won't unpack properly...)

The moral: BINSCII ANYTHING YOU PLACE ON THE NET!  Fine, it takes 33%
longer to upload and download, but then it's 99% more likely to work
(notice how often even a BINSCII file gets munged--binary files are 10
times more fragile...).  All it takes in one stupid EBCDIC computer to
munge a binary file.

The mini/mainframe world hasn't learned what 8-bit binary data is yet,
so please, BINSCII all binary files!

			Kent Dickey
kadickey@phoenix.Princeton.EDU