Skip to content

Capabilities

AppleCommanderFX differs from AppleCommander, not only in the user interface, but also in the underlaying APIs. The ultimate goal is to shift all components over. During transition, this will hopefully help understand some of the non-visual differences.

Disk image organizations

Description AppleCommander AppleCommanderFX
Compressed images (*.gz) Yes Yes
140K DOS-ordered images (*.do, *.dsk, *.d16) Yes Yes
140K ProDOS-ordered images (*.po) Yes Yes
13-sector and 16-sector Nibble images (*.nib) Yes Yes
13-sector DOS-ordered images (*.d13) Yes Yes
32MB ApplePC Hard Disk images (*.hdv) Yes Yes
Universal Disk Images (*.2mg, *.2img) Yes Yes
Disk Copy Images (*.dc) Yes Yes
WOZ Disk Image, version 1 and 2 (*.woz) - 5.25" only Yes Yes

Disk formats

Description AppleCommander AppleCommanderFX
DOS (13-sector) Read-only Read-only4
DOS (16-sector) Read/Write Read/Write4
UniDOS, OzDOS (800K formats only) Read/Write Read/Write4
ProDOS Read/Write Read/Write4
Apple Pascal (140K and 800K formats) Read/Write Read/Write4
SSI's RDOS (140K formats only) Read-only Read-only4
CP/M (probably only 140K formats) Read-only Read-only4
Gutenberg Word Processor Read-only Read-only4
NakedOS (see the Super-Mon page) Read-only Read-only4
GameDOS N/A Read/Write/Format3

Archive formats

Description AppleCommander AppleCommanderFX
ShrinkIt Read-only1 Read-only2
AppleSingle Import/Export Import/Export
Apple Archive Format N/A Read-only
Zip N/A Read/Write/Create

  1. The archive will be automatically extracted into a ProDOS disk. ↩

  2. The archive will be handled in it's native format. ↩

  3. When format is called out, this implies the the disk is bootable as well. ↩

  4. The "legacy" implementations work through a shim that maps the old APIs into the new APIs. It is a short-term fix. ↩↩↩↩↩↩↩↩↩