More README updates
This commit is contained in:
Jeff Parsons
parent
ab1d25c289
commit
7bfc81a286
5 changed files with 38 additions and 33 deletions
|
|
@ -1,4 +1,4 @@
|
|||
PCjs: JavaScript Machines
|
||||
PCjs Machines
|
||||
===
|
||||
|
||||
Welcome to PCjs, home of [PCx86](/docs/pcx86/), the original IBM PC simulation written entirely JavaScript. It is
|
||||
|
|
@ -15,8 +15,8 @@ and assorted mobile browsers.
|
|||
|
||||
[Embedded IBM PC](/devices/pcx86/machine/5150/mda/64kb/ "PCx86:ibm5150")
|
||||
|
||||
The [PCx86 Simulation](/devices/pcx86/machine/5150/mda/64kb/) above features an Intel 8088 running at 4.77Mhz,
|
||||
with 64Kb of RAM and an IBM Monochrome Display Adapter. For more control, there are also
|
||||
The [JavaScript Machine](/devices/pcx86/machine/5150/mda/64kb/) above uses [PCx86](/docs/pcx86/) configured with an Intel
|
||||
8088 running at 4.77Mhz, with 64Kb of RAM and an IBM Monochrome Display Adapter. For more control, there are also
|
||||
[Control Panel](/devices/pcx86/machine/5150/mda/64kb/debugger/) and [Soft Keyboard](/devices/pcx86/machine/5150/mda/64kb/softkbd/)
|
||||
configurations, featuring the built-in PCx86 Debugger. For even greater control, build your own PC. The
|
||||
[PCx86 Documentation](/docs/pcx86/) will help you get started.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Site settings
|
||||
|
||||
title: "PCjs: JavaScript Machines"
|
||||
title: "PCjs Machines"
|
||||
email: Jeff@pcjs.org
|
||||
description: >
|
||||
PCjs: Home of the original IBM PC emulator in a browser.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ redirect_from:
|
|||
IBM PC Application Archive
|
||||
---
|
||||
|
||||
Below are selected demos of classic IBM PC applications running on [PCjs](/docs/about/pcjs/).
|
||||
Below are selected [PCjs](/docs/about/pcjs/) demos of classic IBM PC applications:
|
||||
|
||||
* [VisiCalc (1981)](1981/visicalc/)
|
||||
* [Executive Suite (1982)](1982/esuite/)
|
||||
|
|
@ -17,36 +17,45 @@ Below are selected demos of classic IBM PC applications running on [PCjs](/docs/
|
|||
* [ThinkTank (1987)](1987/thinktank/)
|
||||
* [The Dungeons of Moria (1992)](1992/moria/)
|
||||
|
||||
A list of all the software available to PCjs machines can be found in the [IBM PC Disk Library](/disks/pcx86/).
|
||||
A list of all the software available to PCx86 machines can be found in the [IBM PC Disk Library](/disks/pcx86/).
|
||||
|
||||
### Creating IBM PC Application Demos
|
||||
|
||||
Demos in our [Application Archives](/apps/) combine [Software Application Manifests](/apps/#software-application-manifests)
|
||||
with [Machine Configurations](/devices/pcx86/machine/).
|
||||
Demos in our [Application Archives](/apps/) combine
|
||||
[Software Application Manifests](/apps/#software-application-manifests) with
|
||||
[Machine Configurations](/devices/pcx86/machine/).
|
||||
|
||||
We'll use the [VisiCalc Demo](1981/visicalc/) as an example. First you must choose a machine configuration.
|
||||
We'll use the [VisiCalc Demo](1981/visicalc/) as an example. First, we choose a machine configuration.
|
||||
For VisiCalc, we chose a Model 5150 machine with a Monochrome Display, and then inserted a link to that machine
|
||||
in the demo's [manifest](1981/visicalc/manifest.xml):
|
||||
|
||||
<machine href="/devices/pcx86/machine/5150/mda/64kb/machine.xml"/>
|
||||
```xml
|
||||
<machine href="/devices/pcx86/machine/5150/mda/64kb/machine.xml"/>
|
||||
```
|
||||
|
||||
Next, the [manifest](1981/visicalc/manifest.xml) required a disk image containing the VisiCalc program
|
||||
Next, the [manifest](1981/visicalc/manifest.xml) requires a disk image containing the VisiCalc program
|
||||
(VC.COM). We used the [DiskDump](/modules/diskdump/) module to create that disk image:
|
||||
|
||||
cd apps/pcx86/1981/visicalc
|
||||
node ../../../../modules/diskdump/bin/diskdump --path="archive/VC.COM;../README.md" --format=json --output=disk.json --manifest
|
||||
|
||||
The DiskDump command created a disk image named "disk.json" containing two files ("VC.COM" from the "archive" subdirectory,
|
||||
and "README.md" from the "archive" parent directory) and automatically added that disk image to the demo's [manifest](1981/visicalc/manifest.xml):
|
||||
The DiskDump command created a disk image named "disk.json" containing two files ("VC.COM" from the "archive"
|
||||
subdirectory, and "README.md" from the "archive" parent directory) and automatically added that disk image to the demo's
|
||||
[manifest](1981/visicalc/manifest.xml):
|
||||
|
||||
<disk id="disk01" size="163840" chs="40:1:8" dir="archive/" href="/apps/pcx86/1981/visicalc/disk.json" md5="61494f998d5fb0e31e7b8bd99f1cc588" md5json="3ad82ed815725e6bd786f92a4714e84f">
|
||||
<file size="27520" time="1981-12-16 23:00:00" attr="0x20" md5="28997dfedb2440c6054d8be835be8634">VC.COM</file>
|
||||
<file dir="../">README.md</file>
|
||||
</disk>
|
||||
|
||||
Now that the manifest contains a disk image, we were able to add the manifest to our set of [Sample Disks](/disks/pcx86/samples.xml):
|
||||
```xml
|
||||
<disk id="disk01" size="163840" chs="40:1:8" dir="archive/" href="/apps/pcx86/1981/visicalc/disk.json" md5="61494f998d5fb0e31e7b8bd99f1cc588" md5json="3ad82ed815725e6bd786f92a4714e84f">
|
||||
<file size="27520" time="1981-12-16 23:00:00" attr="0x20" md5="28997dfedb2440c6054d8be835be8634">VC.COM</file>
|
||||
<file dir="../">README.md</file>
|
||||
</disk>
|
||||
```
|
||||
|
||||
<manifest ref="/apps/pcx86/1981/visicalc/manifest.xml" disk="*"/>
|
||||
Now that the manifest contains a disk image, we were able to add the manifest to our set of
|
||||
[Sample Disks](/disks/pcx86/samples.xml):
|
||||
|
||||
```xml
|
||||
<manifest ref="/apps/pcx86/1981/visicalc/manifest.xml" disk="*"/>
|
||||
```
|
||||
|
||||
Next, we started a version of our chosen machine that's also configured to use the Debugger, by loading
|
||||
the following **machine.xml** into a web browser (it's assumed the Node web server is already running on port 8088):
|
||||
|
|
@ -58,10 +67,12 @@ clear the Debugger's output window, and typed the following Debugger command:
|
|||
|
||||
d state
|
||||
|
||||
We copied-and-pasted the entire contents of the Debugger's output window into a file named "state.json", and then updated
|
||||
the <machine> entry in the [manifest](1981/visicalc/manifest.xml):
|
||||
We copied-and-pasted the entire contents of the Debugger's output window into a file named "state.json", and then
|
||||
updated the <machine> entry in the [manifest](1981/visicalc/manifest.xml):
|
||||
|
||||
<machine href="/devices/pcx86/machine/5150/mda/64kb/machine.xml" state="/apps/pcx86/1981/visicalc/state.json"/>
|
||||
```xml
|
||||
<machine href="/devices/pcx86/machine/5150/mda/64kb/machine.xml" state="/apps/pcx86/1981/visicalc/state.json"/>
|
||||
```
|
||||
|
||||
It's important to use a state file *only* with the machine configuration it was created with; in this case, we're OK,
|
||||
because the only difference between the two chosen Model 5150 machines is the addition of the Debugger.
|
||||
|
|
|
|||
|
|
@ -21,22 +21,18 @@ desktop and mobile devices. Machines are created with simple XML files that def
|
|||
along with the features that each component should enable. More details about machine definitions and component
|
||||
capabilities can be found in the [Documentation](/docs/).
|
||||
|
||||
---
|
||||
|
||||
### Emulating the Challenger 1P
|
||||
|
||||
The first PCjs simulation was [C1Pjs](/docs/c1pjs/), a simulation of the
|
||||
The first PCjs emulator was [C1Pjs](/docs/c1pjs/), a simulation of the
|
||||
Challenger 1P, which was a 6502-based microcomputer introduced by Ohio Scientific in 1978.
|
||||
|
||||
C1Pjs v1.0 was released in July 2012. More information about the first release of C1Pjs was
|
||||
[posted](http://osiweb.org/osiforum/viewtopic.php?f=3&t=103) on the
|
||||
[OSI Discussion Forum](http://osiweb.org/osiforum/index.php) at [osiweb.org](http://osiweb.org/).
|
||||
|
||||
---
|
||||
|
||||
### Emulating the IBM PC
|
||||
|
||||
The next PCjs simulation was [PCx86](/docs/about/pcx86/), which simulates the original IBM PC, IBM PC XT,
|
||||
The next PCjs emulator was [PCx86](/docs/about/pcx86/), which simulates the original IBM PC, IBM PC XT,
|
||||
and IBM PC AT. PCx86 v1.0 was released in late 2012. Browse the source code [here](/modules/pcx86/) or on
|
||||
[GitHub](https://github.com/jeffpar/pcjs).
|
||||
|
||||
|
|
@ -47,8 +43,6 @@ cards, along with assorted motherboard and expansion bus components. It also in
|
|||
|
||||
Read [About PCx86](/docs/about/pcx86/) to learn more about its history, features, and upcoming improvements.
|
||||
|
||||
---
|
||||
|
||||
### Migrating to Node
|
||||
|
||||
The PCjs web server was originally written in PHP and hosted at [jsmachines.net](http://jsmachines.net/), but in 2014,
|
||||
|
|
|
|||
4
index.md
4
index.md
|
|
@ -25,8 +25,8 @@ and assorted mobile browsers.
|
|||
|
||||
{% include machine.html id="ibm5150" %}
|
||||
|
||||
The [PCx86 Simulation](/devices/pcx86/machine/5150/mda/64kb/) above features an Intel 8088 running at 4.77Mhz,
|
||||
with 64Kb of RAM and an IBM Monochrome Display Adapter. For more control, there are also
|
||||
The [JavaScript Machine](/devices/pcx86/machine/5150/mda/64kb/) above uses [PCx86](/docs/pcx86/) configured with an Intel
|
||||
8088 running at 4.77Mhz, with 64Kb of RAM and an IBM Monochrome Display Adapter. For more control, there are also
|
||||
[Control Panel](/devices/pcx86/machine/5150/mda/64kb/debugger/) and [Soft Keyboard](/devices/pcx86/machine/5150/mda/64kb/softkbd/)
|
||||
configurations, featuring the built-in PCx86 Debugger. For even greater control, build your own PC. The
|
||||
[PCx86 Documentation](/docs/pcx86/) will help you get started.
|
||||
|
|
|
|||
Loading…
Reference in a new issue