Log script commands to the browser console

devices/pdp11/machine/1170/panel/debugger/xxdp/README.md

@@ -38,9 +38,7 @@ This machine is ready to boot [XXDP+ Diagnostics](/disks/dec/rl02k/xxdp/) ("BOOT
 - [EKBBF0: 11/70 CPU DIAGNOSTIC (PART 2)](/disks/dec/rl02k/xxdp/ekbbf0/)
 - [EKBEE1: 11/70 MEMORY MANAGEMENT DIAGNOSTIC](/disks/dec/rl02k/xxdp/ekbee1/)
 
-Step-by-step instructions are included below.  Other interesting things to know about this machine:
+[Instructions](#test1170) for running those diagnostics are provided below.
-
-* It includes an [M9312 ROM](/devices/pdp11/rom/M9312/) at address 165000.  The exact ROM is [23-616F1](/devices/pdp11/rom/M9312/23-616F1.txt).
 
 {% include machine.html id="test1170" %}
 

modules/shared/lib/component.js

@@ -717,11 +717,21 @@ class Component {
     static processCommands(idMachine, aaCommands, iCommand)
     {
         var fSuccess = true;
+
+     // var dbg = Component.getComponentByType("Debugger", idMachine);
+
         while (iCommand < aaCommands.length) {
 
             var aTokens = aaCommands[iCommand];
             var sCommand = aTokens[0];
 
+            /*
+             * It's possible to route this output to the Debugger window with dbg.println()
+             * instead, but it's a bit too confusing mingling script output in a window that
+             * already mingles Debugger and machine output.
+             */
+            Component.println('script: ' + aTokens.join(' '));
+
             var fnCallReady = null;
             if (Component.asyncCommands.indexOf(sCommand) >= 0) {
                 fnCallReady = function processNextCommand(iNextCommand) {