5. See if you can unpack it. You will need to get to Applesoft Basic
   under ProDOS to do this. [ProDOS identifies itself as such when
   booting, and Basic is the ']' prompt available by running
   'BASIC.SYSTEM' if you booted to the Finder]. From the prompt,
   change to the disk/directory with the BINSCII.TXT file in it. [A
   reference on Dos 3.3 and ProDOS commands is not part of this FAQ,
   but is available at http://www.visi.com/~nathan/a2/faq/dos.html]
   
   Next, verify that the file was transferred as a text file. From
   the prompt, type the following:

PR#3
CATALOG
If the "PR#3" command causes your computer to crash, hang, or display
garbage, you do not have an 80-column card in the normal place.
[This is rare, and only happens on ][+s, or stock //es.] Reboot
your computer and try again without the PR#3 command. The catalog
should have a line like the following (though the date and time
will vary)

BINSCII.TXTTXT1220-AUG-9620-AUG-963:145645
[If not in 80-column mode, that'll be wrapped to 2 lines.] Anyhow, the
number we wanted was the very last number, which should be 5645.
If that number is 5737, you downloaded in binary mode off an IBM
PC. That's fixable. If the number is 512, you disregarded the
warnings above about how the Macintosh will make an Apple II file
unreadable; see the section on file transfer from Macintosh to
Apple II for a Mac program to clean up after that problem.
Also, note the file type in the second column, which is 'TXT'
here. If it is already TXT, you can skip forward to step 5. Fixing
the filetype. First, note what it currently is. If it's not 'TXT',
common alternatives are 'BIN' or '$00', but almost anything is
possible. The second and fourth line of the following commands,
assume it's '$00', with file length 5645. Modify those two values
to match what you saw in the catalog listing above:

RENAME BINSCII.TXT,BINSCII.ORIG
BLOAD BINSCII.ORIG,A$2000,T$00,L5645
CREATE BINSCII.TXT,TTXT
BSAVE BINSCII.TXT,A$2000,TTXT,L5645
This first renames the old file, loads it up, creates a file of the
right length and then writes the new file.
6. Now that the file type is correct, trying to install binscii. Type
the following:

EXEC BINSCII.TXT
If you get a lot of ?SYNTAX ERRORs and beeps, then you most likely did
not download it in ascii mode. You should try again, making sure
of ascii mode, or try typing in this program. If the file size you
got from the CATALOG above is not 5645, change the 5645 in line 10
to whatever it is.

10 D$=CHR$(4): L=5645
20 PRINT D$"BLOAD BINSCII.TXT,A$2000,TTXT,L"L
30 FOR I=8192 TO 8192+L: IF PEEK(I)=10 THEN POKE I,13
40 NEXT: ONERR GOTO 60
50 PRINT D$"DELETE BINSCII2.TXT"
60 PRINT D$"CREATE BINSCII2.TXT,TTXT"
70 PRINT D$"BSAVE BINSCII2.TXT,A$2000,TTXT,L"L
Use the basic command 'RUN' (no 's) to run this program. After it is
done, you should have a better chance at being able to "EXEC
BINSCII2.TXT" and run it.