Consolidated /docs into /pubs
This commit is contained in:
parent
9d356c582b
commit
71d117fa02
106 changed files with 350 additions and 317 deletions
|
|
@ -41,5 +41,5 @@ For example:
|
|||
The [PCjs Node Web Server](/server.js) also generates "onclick" handlers for links to **JSON** disk
|
||||
images that automatically invoke the API for you.
|
||||
|
||||
See [Creating PCx86-Compatible Disk Images](/docs/pcx86/#creating-pcx86-compatible-disk-images)
|
||||
in the [PCx86 Documentation](/docs/pcx86/) for more information about supported disks and formats.
|
||||
See [Creating PCx86-Compatible Disk Images](/pubs/pcx86/#creating-pcx86-compatible-disk-images)
|
||||
in the [PCx86 Documentation](/pubs/pcx86/) for more information about supported disks and formats.
|
||||
|
|
|
|||
|
|
@ -81,14 +81,14 @@ more detail, along with a live demonstration of the software, but that's not yet
|
|||
---
|
||||
|
||||
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](/apps/), but in the context of the Disk Library,
|
||||
it's simply known as a Disk Manifest.
|
||||
|
||||
A Disk Manifest can then be added to a *[Floppy Drive Controller (FDC)](/docs/pcx86/fdc/)* configuration file,
|
||||
A Disk Manifest can then be added to a *[Floppy Drive Controller (FDC)](/pubs/pcx86/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](samples.xml), *could* contain individual <disk>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Two of the PCjs disks shown below:
|
|||
|
||||
are from our private collection and should be exact copies of the original dBASE III v1.0 distribution disks, with the
|
||||
exception of `DBASE.EXE`, which was patched to eliminate copy-protection checks. Details of that patch are available
|
||||
in our collection of [Personal Documents of Dubious Historical Interest](/docs/personal/#dbase-iii-copy-protection),
|
||||
in our collection of [Personal Documents of Dubious Historical Interest](/pubs/personal/#dbase-iii-copy-protection),
|
||||
along with this [blog post](/blog/2017/08/11/).
|
||||
|
||||
Also, for completeness, the original `DBASE.EXE` has been recreated by "unpatching" it and saving it on the
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Multitasking MS-DOS 4.00
|
|||
|
||||
These disk images contain the first unearthed copy of Microsoft's "multitasking" version of MS-DOS
|
||||
since its *extremely* limited release around late 1985 or early 1986. They were were discovered by the
|
||||
[PCjs Project](/docs/about/) in March 2013. More information is available at
|
||||
[PCjs Project](/pubs/about/) in March 2013. More information is available at
|
||||
[Wikipedia](http://en.wikipedia.org/wiki/Multi-tasking_MS-DOS_4.0),
|
||||
[OS/2 Museum](http://www.os2museum.com/wp/?p=1769), and
|
||||
[MSDN Blogs](http://blogs.msdn.com/b/larryosterman/archive/2004/03/22/94209.aspx).
|
||||
|
|
|
|||
Loading…
Reference in a new issue