diff --git a/README.md b/README.md index b143a721a..4142b0e03 100644 --- a/README.md +++ b/README.md @@ -306,7 +306,7 @@ added, too. When a PCjs machine runs in a browser, an XML machine configuration file is transformed into HTML with a set of DIVs for each component: an "object" DIV whose *data-value* attribute provides the initialization parameters for the -corresponding component, along with a set of optional "control" DIVs that the component can bind to (eg, a "Run" button, +corresponding component, along with a set of optional "control" DIVs that the component can bind to (eg, a **Run** button, or a visual representation of DIP switches, or whatever). When a PCjs machine is run from the command-line, there is no XML, HTML, or DIVs involved; this is basically a @@ -379,7 +379,7 @@ where PCjs could run amok and destroy the planet. Other parameters that can be passed via the URL: - *autostart*: set it to "true" to allow all machines to start normally, "false" to prevent all machines from starting, -or "no" to prevent all machines from starting *unless* they have no "Run" button; e.g.: +or "no" to prevent all machines from starting *unless* they have no **Run** button; e.g.: http://localhost:8088/?gort=debug&autostart=false diff --git a/_posts/2015-07-17-windows-95.md b/_posts/2015-07-17-windows-95.md index d353494d0..1f04aaa59 100644 --- a/_posts/2015-07-17-windows-95.md +++ b/_posts/2015-07-17-windows-95.md @@ -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 diff --git a/_posts/2016-10-06-introducing-pdpjs-a-pdp-11-emulator.md b/_posts/2016-10-06-introducing-pdpjs-a-pdp-11-emulator.md index 11525b102..0a0e6db8b 100644 --- a/_posts/2016-10-06-introducing-pdpjs-a-pdp-11-emulator.md +++ b/_posts/2016-10-06-introducing-pdpjs-a-pdp-11-emulator.md @@ -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. diff --git a/_posts/2016-10-21-booting-pdp-11-basic.md b/_posts/2016-10-21-booting-pdp-11-basic.md index e49f84432..5fc3c874d 100644 --- a/_posts/2016-10-21-booting-pdp-11-basic.md +++ b/_posts/2016-10-21-booting-pdp-11-basic.md @@ -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" %} diff --git a/_posts/2016-11-08-you-should-have-voted-for-the-pdp-11.md b/_posts/2016-11-08-you-should-have-voted-for-the-pdp-11.md index dfbee1d9e..01ef5f467 100644 --- a/_posts/2016-11-08-you-should-have-voted-for-the-pdp-11.md +++ b/_posts/2016-11-08-you-should-have-voted-for-the-pdp-11.md @@ -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 diff --git a/_posts/2016-11-13-curious-pdp-11-features.md b/_posts/2016-11-13-curious-pdp-11-features.md index db1ce5ae2..6580c7f02 100644 --- a/_posts/2016-11-13-curious-pdp-11-features.md +++ b/_posts/2016-11-13-curious-pdp-11-features.md @@ -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. diff --git a/_posts/2016-12-02-debugging-pdp-11-issues.md b/_posts/2016-12-02-debugging-pdp-11-issues.md index 7225d3faa..c840dadcb 100644 --- a/_posts/2016-12-02-debugging-pdp-11-issues.md +++ b/_posts/2016-12-02-debugging-pdp-11-issues.md @@ -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: diff --git a/apps/pdp11/tapes/README.md b/apps/pdp11/tapes/README.md index 32a353915..04c962c87 100644 --- a/apps/pdp11/tapes/README.md +++ b/apps/pdp11/tapes/README.md @@ -11,13 +11,16 @@ To load any of the DEC PDP-11 paper tapes listed below, you will need to use a [ with a [PC11 High-Speed Paper Tape Reader/Punch](/devices/pdp11/pc11/), such as this [PDP-11/20](/devices/pdp11/machine/1120/basic/debugger), and then follow this three-step process: -- "Read" the [DEC PDP-11 Bootstrap Loader](/apps/pdp11/boot/bootstrap/) -- "Load" the [Absolute Loader](absloader/) tape image, and read it with the Bootstrap Loader -- "Load" one of the "Absolute Format" tape images below, and read it with the Absolute Loader +- **Read** the [DEC PDP-11 Bootstrap Loader](/apps/pdp11/boot/bootstrap/) +- **Load** the [Absolute Loader](absloader/) tape image +- **Run** the Bootstrap Loader to read the Absolute Loader +- **Load** one of the "Absolute Format" tape images below +- **Run** the Absolute Loader to read the selected tape image -This mirrors the three-step "real world" process of loading paper tape software. Moreover, any "Absolute -Format" tape (which should include all the tapes listed below) can be loaded directly into RAM using the -machine's "Read" button instead of "Load". In most cases, that eliminates the first two steps. +This mirrors the multi-step "real world" process of loading paper tape software. + +PDPjs simplifies that process: any "Absolute Format" tape (which should include all the tapes listed below) can be +loaded directly into RAM using the machine's **Read** button, replacing all the above steps with a single click. Paper Tape Diagnostics ---------------------- diff --git a/apps/pdp11/tapes/diags/README.md b/apps/pdp11/tapes/diags/README.md index 4d1eb80c9..562be6f7e 100644 --- a/apps/pdp11/tapes/diags/README.md +++ b/apps/pdp11/tapes/diags/README.md @@ -13,7 +13,7 @@ website, we have been able to archive the PDP-11 diagnostics shown below. The t [PC11](/modules/pdp11/lib/pc11.js), such as this [PDP-11/20 with Front Panel and Debugger](/devices/pdp11/machine/1120/panel/debugger/). As noted for other [DEC PDP-11 Tape Images](/apps/pdp11/tapes/), these "Absolute Format" tapes 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 +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. diff --git a/devices/README.md b/devices/README.md index 2d417dc82..ce2892d16 100644 --- a/devices/README.md +++ b/devices/README.md @@ -16,7 +16,7 @@ All PCjs machines are built from the following sets of devices: * [6502 Devices](c1p/) (e.g., [Challenger 1P](c1p/machine/)) * [8080 Devices](pc8080/) (e.g., [Space Invaders](pc8080/machine/invaders/), [VT100 Terminal](pc8080/machine/vt100/)) * [8086 Devices](pcx86/) (e.g., [IBM PC and compatibles](pcx86/machine/)) -* [PDP-11 Devices](pdp11/) (e.g., [PDP-11/20](pdp11/machine/1120/), [PDP-11/70](pdp11/machine/1170/)) +* [PDP-11 Devices](pdp11/) (e.g., [PDP-11/20](pdp11/machine/1120/), [PDP-11/45](pdp11/machine/1145/), [PDP-11/70](pdp11/machine/1170/)) These devices are user-installable components that you would typically find in a real personal computer, such as keyboards, disk drive controllers with one or more drives, video cards, etc. diff --git a/devices/pc8080/machine/invaders/debugger/README.md b/devices/pc8080/machine/invaders/debugger/README.md index 9bc60c43f..150aaf170 100644 --- a/devices/pc8080/machine/invaders/debugger/README.md +++ b/devices/pc8080/machine/invaders/debugger/README.md @@ -23,7 +23,7 @@ It is currently playable only in desktop browsers and uses the following hard-co - D: Move Right - L: Fire Missile -Click the "Run" button to start the simulation. You'll also find assorted +Click the **Run** button to start the simulation. You'll also find assorted [Space Invaders Hardware Notes](#space-invaders-hardware-notes) below. {% include machine.html id="invaders" %} diff --git a/devices/pc8080/machine/vt100/debugger/README.md b/devices/pc8080/machine/vt100/debugger/README.md index 3571a9ff8..b30e1001e 100644 --- a/devices/pc8080/machine/vt100/debugger/README.md +++ b/devices/pc8080/machine/vt100/debugger/README.md @@ -12,7 +12,7 @@ DEC VT100 Terminal with Debugger -------------------------------- The [PC8080](/modules/pc8080/) machine below is configured to simulate a [VT100 Terminal](/devices/pc8080/machine/vt100/) -with a Control Panel and Debugger. When you press the "Run" button, it will start running the original +with a Control Panel and Debugger. When you press the **Run** button, it will start running the original [VT100 Firmware](/devices/pc8080/rom/vt100/) inside the [PC8080](/modules/pc8080/) CPU emulator. Information about [VT100 Keys](#vt100-keys) and assorted [Hardware Notes](#vt100-memory-usage) are provided below, @@ -208,8 +208,10 @@ Consequently, a VT100 [machine XML file](machine.xml) must set the Video compone to "true", indicating that existing RAM should be used, and a new property, *bufferFormat* must be set to "vt100", enabling support for the VT100's line data format; eg: - -