IBM PC Disk Archive
---
Below are selected Disk Sets featuring "Ready-to-Boot" machine configurations:
* [IBM PC (Model 5150), MDA, 64K, CP/M-86](/disks/pc/cpm/)
* [IBM PC (Model 5150), MDA, 64K, IBM Diagnostics v2.20](/disks/pc/diags/ibm/2.20/)
* [IBM PC (Model 5150), CGA, 64K, Zork I](/disks/pc/games/infocom/zork1/)
You can browse the rest of the disk archive by type. There is no search capability at this time.
Learn more about
[Disk Sets](https://github.com/jeffpar/pcjs/tree/master/disks/pc) in the
[PCjs Project](https://github.com/jeffpar/pcjs) on [GitHub](https://github.com/).
### Developer Notes: Disk Sets and Manifests
Collections of related disks are organized into *Disk Sets* which can then be loaded from the
[FDC (Floppy Disk Controller)](/docs/pcjs/fdc/) component of an [IBM PC Machine Configuration](/devices/pc/machine/).
Disk Sets are stored in their own folders, along with a **manifest.xml** file listing the individual diskettes.
Manifests also record a variety of metadata about the software; more information about the manifest format
is available in [Application Archives](/apps/).
A simple FDC XML file, such as [samples.xml](samples.xml), *could* contain <disk> entries like:
PC-DOS 1.0PC-DOS 1.1PC-DOS 2.0 (Disk 1)PC-DOS 2.0 (Disk 2)
...
listing all the diskettes available for the machine to load. However, listing individual diskettes is tedious,
so the FDC also supports **manifest.xml** files. Instead of listing the PC-DOS 2.0 diskettes individually,
they can be added to [samples.xml](samples.xml) with a single line:
The same feature works with [Application Manifests](/apps/#software-application-manifests). Here's how you might
add [VisiCalc](/apps/pc/1981/visicalc/) to [samples.xml](samples.xml):
The application must have a **manifest.xml** with <disk> section containing an *id* value that matches the
*disk* value specified above:
VC.COMREADME.md
VisiCalc License
If multiple disks are defined in the manifest, and you want to include them all, you can set the *disk* value to '*', as in:
As an added bonus, PCjs will automatically display the descriptive <link> whenever this item is selected, and it will
dynamically generate a disk image containing all the specified <file> entries when the selected item is loaded.
Pre-generated disk images are preferred to dynamically-generated images, and you can now include those in the application
**manifest.xml** as well, by adding an *href* value to the <disk> section that was used to create the image:
VC.COMREADME.md
VisiCalc License
The PCjs [DiskDump](/modules/diskdump/) module is used to create all our pre-generated JSON-encoded disk images.
In the above example, a pre-generated disk image could be created from the command-line with either the "--dir" option
(which will traverse all subdirectories as well):
node diskdump --dir=./apps/pc/1981/visicalc/bin/ --format=json --output=./apps/pc/1981/visicalc/disk.json
or with the "--path" option, which specifies either a single file or a set files separated by semi-colons:
node diskdump --path="./apps/pc/1981/visicalc/bin/vc.com;../readme.md" --format=json --output=./apps/pc/1981/visicalc/disk.json
or via the PCjs server's DiskDump API:
http://www.pcjs.org/api/v1/dump?path=/apps/pc/1981/visicalc/bin/vc.com&format=json
Learn more about PCjs disk image formats [here](/disks/).