Re: Please help with BinSCII

[Rubywand <rubywand@swbell.net>]

Jeff Blakeney writes ...
> 
> On Wed, 21 Jun 2000 15:21:52 -0500, Rubywand <rubywand@swbell.net>
> wrote:
> 
> > It sounds like you are trying to use the binscii.exe file from the TFFE
> > site (or maybe from some other site offering the same file).
> > A check of the file indicates a weird error-- it has $0A's (LF's)
> > where there should be
> > $0D's (CR's).
> 
> That isn't weird at all.  If the TFFE site is run on a Unix system
> then that is the normal end of line character.  If you FTP the file in
> ASCII or text mode (which is the way all text files, including BINscii
> files, should be transferred) the end of line characters will
> automatically be translated from whatever the FTP site uses to
> whatever the machine you are downloading to uses.
 ....

     Thanks for the info.

     Unfortunately, the format does _require_ that the user know that the
particular ".exe" file is a Text file and that it should be downloaded via an
ftp client set to force a Text download-- i.e. the usual "auto" or "binary"
settings will not produce the hoped for change.

     Plus, if you download the file via an ftp client running on a PC, the
change will be to add a CR for each LF. So, the file can not simply be
transferred via Z-modem and EXECed. And, if it is transferred via a Text
send, then one side or the other will need to be set to strip off the LF's in
order to have a ready-to-EXEC file.

     Given the above and that the file will not download correctly via a
browser on most machines, it is fair to say that the format makes no sense
for Apple II files on an Apple II ftp site.

     The correct format for an Apple II Text file intended for use on an
Apple II is to use just a single CR as a line ender. On most machines, a file
named with the .exe suffix will download with no hassle and no corruption via
a browser or ftp client. And, it will transfer fine via Z-modem, arrive with
the usual default Text filetype, and be ready to EXEC.



Rubywand