pcjs/disks/pc

layout	title	menu_title	menu_order	permalink
page	IBM PC Disk Library	Disks	4	/disks/pc/

IBM PC Disk Library

This Disk Library collects all the Disk Manifests in the PCjs Project. These disks are available to any IBM PC Machine in the project that uses the library. However, most machines use the compiled form of the library in order to reduce machine load time.

The list below is not a complete list of everything in the library, just highlights. For some of the disks, we have provided more information about the software, and in some cases, machines that automatically run the software. Ideally, everything in the library would also be listed below, and linked to a page that describes the software in more detail, along with a live demonstration of the software, but that is not yet a reality.

For application demos, see the IBM PC Application Archive, which focuses excusively on applications. The Disk Library is a superset, including operating systems, application software, diagnostics, and more.

PC-DOS (IBM)

• PC-DOS 1.00 (1981)
• PC-DOS 1.10 (1982)
• PC-DOS 2.00 (1983)
• PC-DOS 2.10 (1983)
• PC-DOS 3.00 (1984)
• PC-DOS 3.10 (1985)
• PC-DOS 3.20 (1986)
• PC-DOS 3.30 (1987)
• PC-DOS 4.00 (1988)
• PC-DOS 5.00 (1991)
• PC-DOS 6.00
• PC-DOS 6.10 (1993)
• PC-DOS 6.30 (1993)
• PC-DOS 7.00 (1994)

MS-DOS (Microsoft)

• MS-DOS 1.25
• MS-DOS 2.00
• MS-DOS 3.20
• MS-DOS 3.21
• MS-DOS 3.30
• MS-DOS 3.31
• MS-DOS 4.00
• MS-DOS 4.01
• MS-DOS 4.0M
• MS-DOS 5.00
• MS-DOS 6.00
• MS-DOS 6.20
• MS-DOS 6.22

MS-DOS (COMPAQ)

• COMPAQ MS-DOS 1.11
• COMPAQ MS-DOS 1.12
• COMPAQ MS-DOS 2.12
• COMPAQ MS-DOS 3.10
• COMPAQ MS-DOS 3.31

IBM OS/2

• IBM OS/2 1.0
• IBM OS/2 1.1
• IBM OS/2 1.3

Microsoft OS/2

• MS OS/2 1.0
• MS OS/2 1.1
• MS OS/2 1.2

Other OS/2 Disks

• OS/2 Prototype Disks

Microsoft Windows

• Microsoft Windows 1.00
• Microsoft Windows 1.01
• Microsoft Windows 1.02
• Microsoft Windows 1.03
• Microsoft Windows 1.03a
• Microsoft Windows 1.03b
• Microsoft Windows 1.04
• Microsoft Windows 2.03
• Microsoft Windows/386 2.01
• Microsoft Windows/386 2.03
• Microsoft Windows/286 2.10
• Microsoft Windows/386 2.10
• Microsoft Windows/286 2.11
• Microsoft Windows/386 2.11
• Microsoft Windows 3.00
• Microsoft Windows 3.10
• Microsoft Windows 3.11
• Microsoft Windows 95 (Build 499)
• Microsoft Windows 95 (Build 950)

Other Operating Systems

• CP/M-86
• Minix 1.1
• PC/IX 1.0
• Microport's AT&T UNIX System V-AT 2.3
• SCO Xenix 8086 Operating System v2.1.3

Applications

• Lotus 1-2-3 1.0A
• Microsoft Chart 2.02
• Microsoft Word 3.0
• Microsoft Word 3.1
• Microsoft Word 5.0
• Microsoft Word for Windows 2.0C

Borland Tools

• Borland Pascal 3.00B
• Borland Pascal 3.01A

IBM Tools

• IBM Diagnostics v2.20

Microsoft Tools

• Microsoft BASIC
• Microsoft C 4.00
• Microsoft MASM 4.00
• Microsoft Mouse 5.00
• Microsoft OS/2 SDK 1.02
• Microsoft Windows SDK 1.01
• Microsoft Windows SDK 1.03
• Microsoft Windows SDK 1.04
• Microsoft Windows SDK 2.03
• Microsoft Windows SDK 3.00

NOTE: We also have links to all the Microsoft Languages NewsLetters that were published in PC Tech Journal.

Microsoft Games

• Microsoft Adventure (1981)
• Microsoft Flight Simulator (1984)

Other Games

• Infocom Zork I

PCjs Test Suites

• VGA "Black Book" Tests

---

Disk Manifests

Typically, all the distribution disks for a single version of a piece of software are placed in a single folder, along with a manifest.xml file containing metadata about the software and a list of the individual disks. This is generally referred to as a Software Manifest, but in the context of disk management, it is also known as a Disk Manifest.

A Disk Manifest can then be added to a Floppy Disk Controller (FDC) configuration file, making all its disks available to any machine loading that particular configuration file.

A simple FDC configuration file, such as samples.xml, could contain individual <disk> entries like:

<disk path="/disks/pc/dos/ibm/1.00/PCDOS100.json">PC-DOS 1.00</disk>
<disk path="/disks/pc/dos/ibm/1.10/PCDOS110.json">PC-DOS 1.10</disk>
<disk path="/disks/pc/dos/ibm/2.00/PCDOS200-DISK1.json">PC-DOS 2.00 (Disk 1)</disk>
<disk path="/disks/pc/dos/ibm/2.00/PCDOS200-DISK2.json">PC-DOS 2.00 (Disk 2)</disk>
...

However, listing individual diskettes like that is tedious, so support was added for Disk Manifests.

So instead of listing the PC-DOS 2.00 diskettes individually, they can be added to samples.xml with a single line:

<manifest ref="/disks/pc/dos/ibm/2.00/manifest.xml" disk="*"/>

When you want to include only one particular disk from a manifest, set the disk value to the id of the disk. Here's how you would include only the first disk from PC-DOS 2.00:

<manifest ref="/disks/pc/dos/ibm/2.00/manifest.xml" disk="disk01"/>

For reference, here's what the entire Disk Manifest for PC-DOS 2.00 currently looks like:

<manifest type="software">
    <title>PC-DOS</title>
    <version>2.00</version>
    <type>DOS</type>
    <category>Operating System</category>
    <author>IBM/Microsoft</author>
    <releaseDate/>
    <disk id="disk01" size="184320" chs="40:1:9" img="archive/PCDOS200-DISK1.img" href="/disks/pc/dos/ibm/2.00/PCDOS200-DISK1.json" md5="d57ceef82122790d1c0ff7bebc12f90a" md5json="2507c02da6cbafe9a94a35cbdd993be2">
        <name>PC-DOS 2.00 (Disk 1)</name>
    </disk>
    <disk id="disk02" size="184320" chs="40:1:9" img="archive/PCDOS200-DISK2.img" href="/disks/pc/dos/ibm/2.00/PCDOS200-DISK2.json" md5="1c7aac53c78446992f8821cf42d04c4a" md5json="b66e296319c1f97990b596b1aa376d39">
        <name>PC-DOS 2.00 (Disk 2)</name>
    </disk>
</manifest>