Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'master' into gh-pages, and fix a few issues related to autoStart

Browse source 
# Conflicts:
#	_posts/2016-12-02-the-pdp-11-and-vt100-revisited.md
#	docs/pcx86/examples/pcx86-dbg.js
#	docs/pcx86/examples/pcx86.js
This commit is contained in:
Jeff Parsons 2016-12-04 11:26:10 -08:00 • committed by Jeff Parsons
commit 9ed580066c
33 changed files with 348 additions and 321 deletions
Download patch file Download diff file Expand all files Collapse all files

2
_posts/2015-07-17-windows-95.md
View file

@ -89,7 +89,7 @@ first prefix changed the instruction's addressing mode from 16-bit to 32-bit, an
16-bit. PCx86 should have simply ignored the second prefix.
With all of the above changes in place, PCx86 v1.18.4 is able to run Windows 95 Setup a bit farther, but still far from
completion. If you want to give it a spin yourself, start the machine below (click the "Run" button) and once it has
completion. If you want to give it a spin yourself, start the machine below (click the **Run** button) and once it has
finished booting, run SETUP from drive B, where the first Windows 95 diskette is already loaded.
If, when it crashes (and it will), you're interested in examining the instructions that were executed prior to the

2
_posts/2016-10-06-introducing-pdpjs-a-pdp-11-emulator.md
View file

@ -37,7 +37,7 @@ component, [device.js](/modules/pdp11/lib/device.js), which has now been convert
The first new device component is [serialport.js](/modules/pdp11/lib/serialport.js), which is currently the
only means PDPjs has of communicating with the outside world. So you can try
[PDPjs connected to a VT100 Terminal](/devices/pdp11/machine/1170/vt100/), by clicking the "Run" button on the test machine.
[PDPjs connected to a VT100 Terminal](/devices/pdp11/machine/1170/vt100/), by clicking the **Run** button on the test machine.
The test machine is running [custom boot code](/apps/pdp11/boot/test/), adapted from boot code written by Paul, but due to the
lack of other device support, nothing can be booted yet.

7
_posts/2016-10-21-booting-pdp-11-basic.md
View file

@ -24,9 +24,10 @@ and machines can now be configured to include a virtual paper tape reader, with
ready to be loaded.
In the real world, before you could load *any* paper tape, you had to first enter a
[Bootstrap Loader](/apps/pdp11/boot/bootstrap/). PDPjs has simplified that process by including the Bootstrap Loader as
just another paper tape image that you can "Read" directly into memory. Once that has been done, you can then load any
other paper tape image using the Bootstrap Loader, once you "Load" it into the paper tape reader.
[Bootstrap Loader](/apps/pdp11/boot/bootstrap/). PDPjs has simplified that process by including the "Bootstrap Loader"
as just another paper tape image that you can read directly into memory, using the **Read** button. Once that has been
done, you can then load any other paper tape image using the Bootstrap Loader, once you **Load** it into the paper tape
reader.
{% include machine.html id="test1120" %}

4
_posts/2016-11-08-you-should-have-voted-for-the-pdp-11.md
View file

@ -28,11 +28,11 @@ The latest release, v1.30.3, adds the following features:
- Support for DEC's [RL11 Disk Controller](/devices/pdp11/rl11/) has been implemented
To test RL11 support below, then select the "XXDP+ Diagnostics" disk from the "Disk Drive Controls",
click "Load", and wait for the message:
click **Load**, and wait for the message:
Mounted disk "XXDP+ Diagnostics" in drive RL0
Then start the machine (click "Run") and make sure the following prompt has been displayed:
Then start the machine (click **Run**) and make sure the following prompt has been displayed:
PDP-11 MONITOR V1.0

2
_posts/2016-11-13-curious-pdp-11-features.md
View file

@ -80,7 +80,7 @@ but unlike tapes like [PDP-11 BASIC](/apps/pdp11/tapes/basic/), they don't inclu
documentation for each test to learn the starting procedure, including any switches that should be set first.
However, PDPjs makes life a bit simpler for you. As noted for other [DEC PDP-11 Tape Images](/apps/pdp11/tapes/), any
"Absolute Format" tape can be read directly into RAM using the machine's "Read" button instead of "Load", allowing you
"Absolute Format" tape can be read directly into RAM using the machine's **Read** button instead of **Load**, allowing you
to bypass the usual three-step process of loading the [Bootstrap Loader](/apps/pdp11/boot/bootstrap/) in order to load the
[Absolute Loader](/apps/pdp11/tapes/absloader/) in order to load the desired tape.

6
_posts/2016-12-02-debugging-pdp-11-issues.md
View file

@ -10,13 +10,13 @@ I'm still trying to flush out lingering bugs in PDPjs. I'll give you an example
![Image of PDP-11/70 with 256Kb, Front Panel and Debugger](/blog/images/pdp-1170-panel-debugger.png)
After loading the "MD-11 11/70 CPU EXERCISER" paper tape image directly into memory using the "Load" button
(*not* "Attach"), and then loading the "RT-11 v4.0" disk image into drive RK0, and then finally issuing a few
After loading the "MD-11 11/70 CPU EXERCISER" paper tape image directly into memory using the **Read** button
(*not* **Load**), and then loading the "RT-11 v4.0" disk image into drive RK0, and then finally issuing a few
preliminary Debugger commands:
m rk11 on; bp 005254
we're ready to "let 'er rip," either by using the Debugger `g` command or clicking the "Run" button.
we're ready to "let 'er rip," either by using the Debugger `g` command or clicking the **Run** button.
You'll see a variety of disk-related messages from the RK11 component in the Control Panel window, which serves
both as the Debugger's output window and as the 11/70's terminal window. The output begins with: