See also Notes on operating the Front Panel.

The simulator by default will attempt to optimize programs spinning on PCB instructions such that they sleep. This will be done after 100mS of spinning, and will avoid hogging a CPU on the host for things like the card reader running out of cards. This feature can be turned off using the property (passed on the commandline) "iosleep=no". This feature is also disabled when running throttled (see Debug menu).

Menus are as follows:

File Disk Util Debug

The assemble dialogs have a checkbox for "Listing". This causes an assembly listing to printed on the Line Printer, along with a dump of the symbol table.

The assemble dialogs also have options for creating a Magnetic Tape Image. This will produce a "Binary Run Tape" (BRT) with the bootstrap and loader records. Eventually, this will be a fairly-complete "Tape Monitor/Loader C" implementation, but right now it wraps a singe program in the self-loading code which allows for running the program. The procedure is similar to that described by "Tape Monitor/Loader C" documentation: BOOTSTRAP 40 twice, then RUN once. The following format is used:

  1. "1HDRΔ" record (skipped during bootstrap)
  2. The loader, bootmt.mti, including bootstrap and loader records
  3. The program image in BRT format, single segment, multiple records
  4. "1EOFΔ" record
  5. Two "1ERIΔ" records

The loader will restore punctuation based on the information in the tape image. Such a tape image may be mounted on tape drive 000 and used with the BOOTSTRAP and RUN buttons to load and run the program. The loader, bootmt.mti, was created from bootstrap.ezc and brtloader.ezc in the sample programs. These programs cannot be assembled from the front panel, as they require a different output format than BRT.

Tracing

Trace output has the basic format:

Where SR is the address in SR at the start of the fetch, OP is the fetched instruction opcode mnemonic, AAR is the starting AAR, BAR is the starting BAR, next AAR/BAR are the AAR and BAR at the end of instruction execution, VR... are the variant characters, and AIR is the contents of the AIR register at the end of instruction execution. AAR, BAR, or VR may be prefixed with '_' to indicate chained values, i.e. values were not specified in the current instruction. All numeric values are shown in octal.

Dumping

Dump output uses a format based on a traditional Honeywell core dump. Each 128 memory locations are shown in a row of 5 lines. The first line shows the address headings (octal) for the subsequent lines. The second line shows the printed character representation of each location. Lines 3 and 4 show the octal character representation, line 3 being the most-significant digit. Line 5 shows the punctuation, 'W' for word mark, 'I' for item mark, and 'R' for both (record mark).