1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
IMPORTANT NOTICE: The gscii plus NDA (and related unpackers, like the
sscii command) can NOT correctly unpack the GS-Shrinkit 1.1 file. You
_MUST_ use the binscii program that was mentioned and downloaded in
stage 1, or wait for GS-Shrinkit 1.1A.
Run them Shrinkit program you just unpacked. GS-Shrinkit can be run by
double-clicking on its icon in the Finder or the equivalent for other
launchers. For the other programs, from the Basic ']' command in the
disk/directory where you unpacked the program type 'CAT' to get a list
of files. Find the filename of the program, and then '-FILENAME' to
run it. (Replace 'FILENAME' with the name you saw in the list)
5.13 How do I unpack a generic .SHK or .BSQ file?
Now that you have all the files you want on your Apple II, you will
first need to run the binscii program on any BINSCII'd files you
downloaded, and then the Shrinkit program on the results of the
un-binsciiing and/or any .SHK/.BXY files you downloaded. Once you're
done with that, it's up to you to play around with the files you
unpacked.
After unpacking the .BSQ files, you'll notice that .SHK files are
usually produced. You do not need to keep the .BSQ files around to
unpack the .SHK files; you may delete the .BSQ file(s) at your
convenience. Similarly, once the .SHK file is unpacked, you can delete
it if you do not expect to need to unpack it again anytime soon.
5.14 I can download .BSQ files fine, but .SHK files can't unpack. What's
wrong?
If these files are coming from a standard Apple II ftp site, such as
those listed in section 5.2, they should unpack fine as long as you
download the files in BINARY mode at every stage, which includes from
the ftp site to any intermediate machines along the way. Any single
text download will usually corrupt a .SHK file enough to make it
impossible to unpack. Make sure that you're downloading in binary at
each and every stage. Binscii (.BSQ) files contain enough extra
information so that they aren't affected by ascii downloads.
There are the occasional bad uploads to the ftp sites, but these tend
to be reported quickly and dealt with. If you're having a problem with
a file, and are very sure that the file is bad on the ftp server,
please email the administrator to resolve the problem. Administrators
should have tools to verify the integrity of any files on their sites,
and deal with any problems on their end. [Administrator's email
addresses are usually listed when you connect to a ftp site.]
5.15 Apple Archive Format (aaf)
Apple Archive Format was invented as a standard way to post source
code to comp.sources.apple2. The C and Basic source code to aaf
unpackers are available on the various FTP sites, in aaf format.
Fortunately, files in aaf format can be turned back into source code
with a simple text editor. Just break the file up into component files
and remove the first character of each line.
ftp://apple2.archive.umich.edu/apple2/unix
Alternative location, including dox: http://www.openix.com/~jac
_________________________________________________________________