diff --git a/_posts/2014-07-30-ega-support.md b/_posts/2014-07-30-ega-support.md index 2425209e2..5031e49bf 100644 --- a/_posts/2014-07-30-ega-support.md +++ b/_posts/2014-07-30-ega-support.md @@ -7,7 +7,7 @@ permalink: /blog/2014/07/30/ --- PCjs v1.14.0 now includes basic EGA support. It emulates the EGA hardware well enough to pass the IBM EGA BIOS -diagnostics and run [Windows 1.01](/devices/pcx86/machine/5160/ega/640kb/win101/) in color. Check out our +diagnostics and run [Windows 1.01](/devices/pcx86/machine/5160/ega/640kb/) in color. Check out our [Windows 1.01 "Server Array"](/devices/pcx86/machine/5160/ega/640kb/array/) demo. [Windows 1.01 "Server Array" Demo](/blog/images/win101-array-demo.jpg) diff --git a/_posts/2016-04-30-the-intel-8080-cpu.md b/_posts/2016-04-30-the-intel-8080-cpu.md index 8f4006a6a..e703e5a17 100644 --- a/_posts/2016-04-30-the-intel-8080-cpu.md +++ b/_posts/2016-04-30-the-intel-8080-cpu.md @@ -10,7 +10,7 @@ PCjs Project. Our first [8080 Test Machine](/devices/pc8080/machine/exerciser/) loads a copy of the [8080 Exerciser](https://web.archive.org/web/20151006085348/http://www.idb.me.uk/sunhillow/8080.html) -(specifically, [8080EX1](/devices/pc8080/rom/exerciser/8080EX1.MAC)) and intercepts the exerciser's CP/M console +(specifically, [8080EX1](/devices/pc8080/ram/exerciser/8080EX1.MAC)) and intercepts the exerciser's CP/M console calls so that you can see its progress in the Control Panel window. It's a "headless" test machine (no keyboard or display), so that's all you get. diff --git a/_posts/2016-11-13-curious-pdp-11-features.md b/_posts/2016-11-13-curious-pdp-11-features.md index 66e734995..d95a866f6 100644 --- a/_posts/2016-11-13-curious-pdp-11-features.md +++ b/_posts/2016-11-13-curious-pdp-11-features.md @@ -7,7 +7,7 @@ permalink: /blog/2016/11/13/ Last week, I ran PDPjs through a series of early [PDP-11 Paper Tape Diagnostics](/apps/pdp11/tapes/diags/). These tests were originally released in 1970 and are documented in such DEC publications as the -[MAINDEC USER REFERENCE MANUAL](http://archive.pcjs.org/pubs/dec/pdp11/diags/MAINDEC_User_Reference_Manual_Oct73.pdf) +[MAINDEC USER REFERENCE MANUAL](http://archive.pcjs.org/pubs/dec/pdp11/diags/MAINDEC-11-DZQAB-B-D_User_Reference_Manual_Oct73.pdf) (October 1973). [Tests 1-12](/apps/pdp11/tapes/diags/#tests-1-12) (MAINDEC-11-D0AA-PB through MAINDEC-11-D0LA-PB) diff --git a/apps/pdp11/boot/bootstrap/README.md b/apps/pdp11/boot/bootstrap/README.md index dd00f6199..944d11cac 100644 --- a/apps/pdp11/boot/bootstrap/README.md +++ b/apps/pdp11/boot/bootstrap/README.md @@ -8,7 +8,7 @@ DEC PDP-11 Bootstrap Loader --------------------------- The **Bootstrap Loader** is a small program that loads the [Absolute Loader](/apps/pdp11/tapes/absloader/), -which is then used to load other PDP-11 tapes in the "Absolute Format," such as [BASIC (Single User)](/apps/pdp11/tabes/basic/). +which is then used to load other PDP-11 tapes in the "Absolute Format," such as [BASIC (Single User)](/apps/pdp11/tapes/basic/). Here's what the **Bootstrap Loader** looks like: @@ -28,7 +28,7 @@ Here's what the **Bootstrap Loader** looks like: 037774 000765 037776 177550 -Using any [PDPjs](/modules/pdpjs/) machine with the built-in Debugger, such as this +Using any [PDPjs](/modules/pdp11/) machine with the built-in Debugger, such as this [PDP-11/20 Boot Monitor](/devices/pdp11/machine/1120/monitor/debugger/), the **Bootstrap Loader** is easily entered with a single Debugger EDIT ("e") command: diff --git a/devices/pcx86/machine/5160/ega/640kb/array/README.md b/devices/pcx86/machine/5160/ega/640kb/array/README.md index b85741c50..75339eaae 100644 --- a/devices/pcx86/machine/5160/ega/640kb/array/README.md +++ b/devices/pcx86/machine/5160/ega/640kb/array/README.md @@ -24,6 +24,9 @@ The simulations below are identical PC XT configurations, each with a clock spee and a 128Kb EGA connected to an Enhanced Color Display, using the original IBM EGA BIOS. {% include machine.html id="ibm5160a" %} + {% include machine.html id="ibm5160b" %} + {% include machine.html id="ibm5160c" %} + {% include machine.html id="ibm5160d" %} diff --git a/disks/dec/README.md b/disks/dec/README.md index 7d6056b35..c9edfb271 100644 --- a/disks/dec/README.md +++ b/disks/dec/README.md @@ -10,13 +10,13 @@ DEC Disk Images The DEC disk images we have archived are organized by type: * [RK03](rk03/) - * [RT-11 v4.0](rt11v4/) [[Source](http://skn.noip.me/pdp11/): RK1.DSK] - * [Unix v5](unixv5/) [[Source](http://skn.noip.me/pdp11/): RK0.DSK] - * [XXDP+ Diagnostics](xxdp/) [[Source](http://skn.noip.me/pdp11/): RK2.DSK] + * [RT-11 v4.0](/disks/dec/rk03/rt11v4/) [[Source](http://skn.noip.me/pdp11/): RK1.DSK] + * [Unix v5](/disks/dec/rk03/unixv5/) [[Source](http://skn.noip.me/pdp11/): RK0.DSK] + * [XXDP+ Diagnostics](/disks/dec/rk03/xxdp/) [[Source](http://skn.noip.me/pdp11/): RK2.DSK] * [RL01K](rl01k/) - * [RSTS/E v7.0](rstsv70/) [[Source](http://skn.noip.me/pdp11/): RL2.DSK] + * [RSTS/E v7.0](/disks/dec/rl01k/rstsv70/) [[Source](http://skn.noip.me/pdp11/): RL2.DSK] * [RL02K](rl02k/) - * [XXDP+ Diagnostics](xxdp/) [[Source](http://skn.noip.me/pdp11/): RL3.DSK] + * [XXDP+ Diagnostics](/disks/dec/rl02k/xxdp/) [[Source](http://skn.noip.me/pdp11/): RL3.DSK] * [RX01](rx01/) * [RT-11 v3.0](/disks/dec/rx01/rt11v3/) [[Source](http://www.headcrashers.org/comp/rx01/)] diff --git a/docs/c1pjs/embed/README.md b/docs/c1pjs/embed/README.md index b8e6e6488..2d04bdd07 100644 --- a/docs/c1pjs/embed/README.md +++ b/docs/c1pjs/embed/README.md @@ -21,13 +21,13 @@ If you want to read as little as possible, then just paste the following code on ```html
``` @@ -44,7 +44,7 @@ The order of the XML elements also determines the layout of the associated HTML **<keyboard>** element appears before the **<video>** element, then the keyboard controls will be displayed *above* the video display instead of *below*. There's an extensive set of attributes that you can add to any of the elements below to style and position them, including the usual *style* attribute, but at present, -there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl). +there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl). The example at the top of this page uses an [XML file](/devices/c1p/machine/8kb/embed/machine.xml) that looks like: @@ -81,7 +81,7 @@ Machine configuration files can also be "self-starting" if they contain the foll top of the file: ```xml - + ``` For example, here's a self-starting [machine.xml](/devices/c1p/machine/8kb/large/machine.xml) configuration. @@ -130,11 +130,11 @@ Step 3: Add the C1Pjs Simulator to your web page Somewhere on your page, you need to add the following **<script>** element: ```html - + ``` -To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.21.6/c1p-dbg.js) instead of -[c1p.js](/versions/c1pjs/1.21.6/c1p.js), and include some additional definitions in your machine +To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.34.0/c1p-dbg.js) instead of +[c1p.js](/versions/c1pjs/1.34.0/c1p.js), and include some additional definitions in your machine definition XML file: ```xml @@ -171,7 +171,7 @@ The **embedC1P()** function accepts three parameters: - the *id* attribute of the HTML element that will contain the simulator (eg, 'myC1P'); - the URL of your machine definition XML file (eg, 'embed.xml', since it's on the same server); - the URL of an XML stylesheet; unless you've created your own stylesheet, it's recommended you omit this -parameter and use the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl). +parameter and use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl). Step 5: Enjoy! --- @@ -179,7 +179,7 @@ All I ask is that any page that embeds the simulator also includes attribution, > [PCjs](http://pcjs.org) © 2012-2017 by [Jeff Parsons](mailto:Jeff@pcjs.org) ([@jeffpar](http://twitter.com/jeffpar)) -If you use the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl), attribution is automatically inserted, +If you use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl), attribution is automatically inserted, which relieves you from including it yourself. Feel free to copy any or all of the files listed above to your own server (it's probably better to share the server diff --git a/modules/markout/lib/markout.js b/modules/markout/lib/markout.js index 3dc8b201a..e314bb790 100644 --- a/modules/markout/lib/markout.js +++ b/modules/markout/lib/markout.js @@ -1019,7 +1019,7 @@ MarkOut.prototype.convertMDImageLinks = function(sBlock, sIndent) * (in case this Markdown file is part of a Jekyll installation) and convert them to Markdown-style links. */ var aMatch; - var reIncludes = /\{%\s*include screenshot\.html\s+(.*?)\s*%}/g; + var reIncludes = /\{%\s*include\s+screenshot\.html\s+(.*?)\s*%}/g; while ((aMatch = reIncludes.exec(sBlock))) { var option, aOptions = {}; diff --git a/modules/shared/README.md b/modules/shared/README.md new file mode 100644 index 000000000..1a6c50f4c --- /dev/null +++ b/modules/shared/README.md @@ -0,0 +1,13 @@ +--- +layout: page +title: Shared Components +permalink: /modules/shared/ +--- + +Shared Components +================= + +PCjs Machines share the following: + +* [Shared JavaScript Modules](lib/) +* [Shared XML/HTML/CSS Templates](templates/)