Document two more test disks

We're using the latest community GSOS release as a convenient example of a
large ProDOS volume with lots of directory structure, forks, and at least a few
files that can be identified by eyeball as having been extracted correctly.

Then I went looking for something DOS 3.3 with T type files on the disk to
verify those were being extracted correctly.  Randomly stumbled across The
Correspondent 4.4 which has them, but also had some surprises for us.  It
crashed cppo!  A combination of removing bashbyter functions and ensuring a
variable gets initialized caused cppo to be able to cat and dump it.  We do
nothing special about filenames made up entirely of control characters,
however, so they'll print incorrectly and extract as non-printable characters
in your filesystem.  It's legal (if crazy) on most UNIX filesystems.  I have
_no idea_ if or how to handle these things on macOS or Windows.
This commit is contained in:
T. Joseph Carter 2017-06-24 03:11:26 -07:00
parent 5266d532fc
commit a9c7b4e24e
1 changed files with 5 additions and 0 deletions

View File

@ -7,6 +7,11 @@ Here are the test disks I am using to test cppo:
- [Asimov](): images/masters/dos_3.3.dsk
- [Asimov](): images/magazines/nibble/nibble\[1991-01\].po
- [Asimov](): images/masters/prodos/ProDOS_2_4_1.dsk
- [Asimov](): images/productivity/word_processing/The\ Correspondent\ v4.4.dsk
- [Asimov](): images/gs/os/gsos/Apple_IIGS_System_6.0.4/Live.Install.po
"The Correspondent" actually doesn't work in pre -ng cppo, and AppleCommander
only seems to handle it by ignoring some of its "interestingness".
More will be added and at some point I'll make a point of describing why each
of these images is a good choice.