Re: AppleCommander and RDOS dsk files

[fadden <fadden@android.com>]

On Apr 15, 3:09 pm, Toinet <antoine.vig...@laposte.net> wrote:
> There are two official RDOS formats (headers are given for SSI's
> disks):

Here's how I broke it down in CiderPress (which has roots in my ProDOS
RDOS converter); see CiderPress/diskimg/RDOS.cpp:

/*
 * See if this looks like a RDOS volume.
 *
 * There are three variants:
 *      RDOS32 (e.g. ComputerAmbush.nib):
 *              13-sector disk
 *              sector (1,0) starts with "RDOS 2"
 *              sector (1,12) has catalog code, CHAIN in (1,11)
 *              uses "physical" ordering
 *              NOTE: track 0 may be unreadable with RDOS 3.2
NibbleDescr
 *      RDOS33 (e.g. disk #199):
 *              16-sector disk
 *              sector (1,0) starts with "RDOS 3"
 *              sector (1,12) has catalog code
 *              uses "ProDOS" ordering
 *      RDOS3 (e.g. disk #108):
 *              16-sector disk, but only 13 sectors of each track are
used
 *              sector (1,0) starts with "RDOS 2"
 *              sector (0,1) has catalog code
 *              uses "physical" orering
 *
 * In all cases:
 *              catalog found on (1,0) through (1,10)
 *
 * The initial value of "pFormatFound" is ignored, because we can
reliably
 * detect which variant we're looking at.
 */

"RDOS 3.2 NibbleDescr" refers to the copy-protected 13-sector format
with the D4 AA B7 sector header (track 0 was unreadable in this mode
because it had standard sectors so the disk could boot).  I only had
one copy-protected 13-sector disk to work from (Computer Ambush), and
that's what it used.

IIRC, the file with the bonus copy protection was either QWERTY or
@WERTY.