diff --git a/devices/pc/machine/README.md b/devices/pc/machine/README.md index 8bfce09e1..677987dbc 100644 --- a/devices/pc/machine/README.md +++ b/devices/pc/machine/README.md @@ -3,9 +3,9 @@ IBM PC Machine Configurations Here you'll find sample Machine Configurations for all the IBM PC models that PCjs currently supports. -* [Model 5150](/devices/pc/machine/5150/) -* [Model 5160](/devices/pc/machine/5160/) -* [Model 5170](/devices/pc/machine/5170/) +* [Model 5150](/devices/pc/machine/#model-5150-machine-configurations) +* [Model 5160](/devices/pc/machine/#model-5160-machine-configurations) +* [Model 5170](/devices/pc/machine/#model-5170-machine-configurations) ### Model 5150 Machine Configurations diff --git a/docs/c1pjs/README.md b/docs/c1pjs/README.md index 940fb0416..59a57f3d9 100644 --- a/docs/c1pjs/README.md +++ b/docs/c1pjs/README.md @@ -12,6 +12,27 @@ information on [customizing and embedding](embed/) your own configurations. ### Using C1Pjs +> **NOTE:** For those of you who never used a *real* Challenger 1P machine, if any of the operational +details of the machine seem bizarre, that's not the simulator's fault. It's how the machine +actually operated. + +> Some of those details are artifacts of teletype-based interfaces, which were more common +than a video monitor interface in the 1970's. On a teletype, there was no way to physically +erase printed characters, so you had to count underscores to know how many characters had been +erased internally. + +> Also, the wide margins on either side of the screen were a side-effect of how the machine +displayed video on a conventional television set; they helped ensure that no characters would be +displayed off-screen and therefore unreadable. As a result, even though the machine contained +enough video memory for 32 rows of characters, each with 32 columns, the usable portion was much +smaller. + +> The original C1P, with its more modern keyboard and video monitor interface, obviously could +have done a better job processing and displaying user input (and in fact, I wrote some +machine-language extensions back in the day that did exactly that). And Ohio Scientific did improve +later models, but the original C1P functioned exactly as shown, with all its teletype-like +idiosyncrasies and television-related limitations. + #### Starting the Simulator > Press the **RUN** or **BREAK** button to start the C1Pjs Simulator. diff --git a/docs/c1pjs/embed/README.md b/docs/c1pjs/embed/README.md index d7fb6d0da..138c338b3 100644 --- a/docs/c1pjs/embed/README.md +++ b/docs/c1pjs/embed/README.md @@ -6,13 +6,13 @@ If you want to read as little as possible, then just paste the following code on
@@ -28,7 +28,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.15.3/components.xsl). +there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.17.1/components.xsl). The example at the top of this page uses an [XML file](/devices/c1p/machine/8kb/embed/machine.xml) that looks like: @@ -62,7 +62,7 @@ The example at the top of this page uses an [XML file](/devices/c1p/machine/8kb/ Machine configuration files can also be "self-starting" if they contain the following XML stylesheet reference at the top of the file: - + For example, here's a self-starting [machine.xml](/devices/c1p/machine/8kb/large/machine.xml) configuration. After it loads, use your browser's "View Source" command and you'll see that it's very similar to the @@ -107,10 +107,10 @@ Step 3: Add the C1Pjs Simulator to your web page --- Somewhere on your page, you need to add the following **<script>** element: - + -To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.15.3/c1p-dbg.js) instead of -[c1p.js](/versions/c1pjs/1.15.3/c1p.js), and include some additional definitions in your machine +To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.17.1/c1p-dbg.js) instead of +[c1p.js](/versions/c1pjs/1.17.1/c1p.js), and include some additional definitions in your machine definition XML file: