Reconstruct Google Code wiki history from r385 on 2013-12-30: release 0.18.

WebUIUsingTheConsole.wiki

@@ -43,7 +43,7 @@ When the emulator is first loaded into a browser, only the *POWER ON* button is
 
 When the SPO window opens, it will print a short message indicating the emulator version. Please wait for this message to finish printing before attempting to press the *LOAD* button.
 
-Once you load the system, there is nothing you need to do with the console, except watch the pretty lights, until you are ready to halt the system. The SPO window will probably be the one you use the most.
+Once you load the system, there is generally nothing you need to do with the console, except watch the pretty lights, until you are ready to halt the system. The SPO window will probably be the one you use the most.
 
 The emulator, like the B5500, is fairly robust. You can halt or power off the system at any time. You can even just quit the browser at any time. We recommend, however that you do an orderly shutdown when you are finished with the system -- press *HALT*, then *POWER OFF*, then quit the browser if desired.
 
@@ -60,7 +60,11 @@ Since the emulator is not a physical system, it is often difficult to tell exact
 
 In non-purist mode, the console displays the current version of the emulator below the Burroughs logo and to the left of the retro-B5500 logo.
 
-The console attempts to update its display every 50 milliseconds. This update period applies not only to the annunciators below, but also to the A/B Normal/Control lights described above. Generally, an annunciator is lit if the corresponding element of the system had any activity since the last update of the display.
+The `MEMORY CHECK` inidicator was a lamp and not a pushbutton on the B5500. If you click this lamp when the emulator is in a powered-on state, however, the console will generate a full dump of processor and core memory state in a separate window. You may save the contents of this window or copy/paste it into another program for analysis.
+
+The `NOT READY` indicator was also a simple lamp on the B5500. As a temporary measure, however, if you click this lamp, the emulator will toggle the second processor into or out of the system configuration. To indicate the state of the second processor, the version annunciator to the left of the "retro-B5500" logo will be yellow when the second processor is enabled and white otherwise. The availability of the second processor will be evaluated only at the time the `POWER ON` button is clicked, so it is best to change the state of the second processor just before powering up the emulator.
+
+The console attempts to update its display every 50 milliseconds. This update period applies not only to the additional annunciators below, but also to the A/B Normal/Control lights described above. Generally, an annunciator is lit if the corresponding element of the system had any activity since the last update of the display.
 
 The top row of annunciators displays activity for the I/O Units (channels) and external interrupts for the system:
 
@@ -104,8 +108,8 @@ The second row of annunciators displays activity for the peripheral devices in t
 
 At the far right of the lower portion of the console are two statistics that indicate how well the emulator for Processor 1 is performing:
 
-    * *P1 Slack:* the average percentage of time the emulated processor is delaying its execution in order to throttle its performance to that of a real B5500. Numbers closer to 100% indicate the processor emulation is using relatively small amounts of your workstation's physical processor. Numbers closer to zero indicate the emulator is barely able (or perhaps unable) to run at the speed of a real B5500.
-    * *P1 Delay:* the average amount of time (in milliseconds) the processor emulation is delayed during throttling _in excess of_ the amount of time it requested to be delayed. This is a running average over the last 1000 delays, and is an indication of how precise the Javascript `setTimeout()` implementation is for your browser.
+    * *P1 Slack:* the exponential moving average for the percentage of time the emulated processor is delaying its execution in order to throttle its performance to that of a real B5500. Numbers closer to 100% indicate the processor emulation is using relatively small amounts of your workstation's physical processor. Numbers closer to zero indicate the emulator is barely able (or perhaps unable) to run at the speed of a real B5500.
+    * *P1 Delay:* the exponential moving average amount of time (in milliseconds) the processor emulation is delayed during throttling _in excess of_ the amount of time it requested to be delayed. This is a running average over the last 1000 delays, and is an indication of how precise the Javascript `setTimeout()` implementation is for your browser.
 
 In our experience with Mozilla Firefox and Google Chrome, the delay number is typically about half the browser's actual precision, plus one or two milliseconds. HTLM5 standards specify that browsers must have a precision of at least four milliseconds, so you should see values in the 3-4ms range for a compliant browser. Lower values are better, as all of the emulation takes place on one Javascript thread, and shorter delays allow the emulation to switch among processor and I/O tasks more efficiently.
 

WebUIUsingTheSPO.wiki

@@ -144,7 +144,7 @@ If you enter an invalid SPO command, or one that has errors in its syntax or ope
 || `TO`         || "Type Options" -- list all of the MCP run-time options and their current setting, e.g., `TO`. ||
 || `TR`         || "Time Reset" -- set the system time of day in 24-hour notation, e.g., `TR 1345`. ||
 || `TS`         || "Type Schedule" -- list all jobs currently in the schedule, e.g., `TS`. ||
-|| `UL`         || "Unlabeled" -- reply to a `#NO FIL` message and assign a peripheral unit with unlabeled media to the job with the specified mix number, e.g., `4UL MTD`. ||
+|| `<mix>UL`    || "Unlabeled" -- reply to a `#NO FIL` message and assign a peripheral unit with unlabeled media to the job with the specified mix number, e.g., `4UL MTD`. ||
 || `WD`         || "What Date" -- display the current system date, e.g., `WD`. ||
 || `WI`         || "What Intrinsics" -- display the name of the current System Intrinsics file being used by the system, e.g., `WI`. ||
 || `WM`         || "What MCP" -- display the name of the current MCP file being used with the system and the compile-time options that are enabled for it, e.g., `WM`. ||