Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!think!mintaka!dcw
From: dcw@lcs.mit.edu (David C. Whitney)
Newsgroups: comp.sys.apple
Subject: Re: BINSCII upload/downloads
Keywords: BINSCII
Message-ID: <1989Dec26.151907.23013@mintaka.lcs.mit.edu>
Date: 26 Dec 89 15:19:07 GMT
References: <1566@clmqt.marquette.Mi.US>
Sender: news@mintaka.lcs.mit.edu
Organization: MIT Spoken Language Systems Group
Lines: 36

I tried this by mail, but it failed...

To: harryw@clmqt.marquette.Mi.US
Subject: Re: BINSCII upload/downloads
Newsgroups: comp.sys.apple
In-Reply-To: <1566@clmqt.marquette.Mi.US>
Organization: MIT Spoken Language Systems Group
Cc: 
Bcc: 


BinSCII is remarkably easy to use once you've got it unpacked
properly. Unfortunately, you don't quite have it right yet. Exec that
text file until BinSCII is stored as a SYS file. Oddly, the
executioner program only sometimes properly adjusts the file's info.

Once it's a SYS file, you just run the program (ie, from a launcher or
by typing -binscii from BASIC). You may now convert or unconvert a
file. Binary files are automatically split up into several text files,
and unconverting the several text files will automatically reassemble
the original binary file. Absolutely any file may be converted to a
text file but only text files with a line "FiLeStArTfIlEsTaRt" in them
will unconvert.

BinSCII is not as picky about the file contents as executioner is. For
example, you do NOT have to edit out mailer headers and stuff. Also,
the text file you unconvert can have several converted parts in it
(each starting with the "FiLe..." line). It doesn't matter what order
you unconvert the parts in - BinSCII does the right thing.

Hope this is helpful...
--
Dave Whitney
dcw@sun-bear.lcs.mit.edu  ...!mit-eddie!sun-bear!dcw  dcw@athena.mit.edu
My employer pays me well. This, however, does not mean he agrees with me.
I wrote Z-Link & BinSCII. Send me bug reports. I use a //GS. Send me Tech Info.