[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HELP!!! Binscii...



In article <3hluit$ftk@netaxs.com>, Wonko The Sane <sane@netaxs.com> wrote:
>	I'll use the file "GSCII.BSC" for my example. You know, the GS 
>Binscii? Anyway, accordin' to dox, I typed [exec gscii.bsc] and I got 
>half a billion ?SYNTAX ERROR's!!! DAMN!!!!!!! 

   Nope. Only the original binscii.exe can be exec'd. If the dox say
to exec gscii.bsc,something's darn wrong. Basically, the .bsc is an
asciified version of a binary file, not executable or anything. The
binscii.exe file is executable, and is designed to self-unpack to
disk.

>Anyway, the dox continue by 
>sayin I should then [-binscii]. Doesn't work. At very best I get a bunch 
>of "*"s in inverse. 

   Yep. A .bsc file is not exec'able, and will not create the binscii
file. Here's what you need to do:

1. Get the files 'binscii.exe' and 'binscii.txt'. There's only one
Apple II ftp site that has these for easy access that I could find
reasonably quickly: ftp.io.org, directory
pub/systems/apple2/8bit/Comm.  Read the binscii.txt file, then
download the binscii.exe file IN ASCII MODE every time you transfer
it. (Download in binary, it won't work)

2. From basic, type 'exec binscii.exe'. It will unpack.

3. Then, run the System file (binscii or binscii.system; I forget which)
and use that to unpack gscii.bsc.

4. Install, then you can use gscii.bsc.



-- 
* Nathan Mates   http://www.ugcs.caltech.edu/~nathan/              <*>
* Ftp humor archiver: ftp to ftp.cco.caltech.edu, look in pub/humor *
* "Always listen to experts. They'll tell what can't be done, and   *
*  why. Then do it."  -- Robert A. Heinlein, Lazarus Long           *