Notes on operating the Front Panel
Menus are as follows:
- File: Assemble a program or assemble the monitor.
- I/O: Control visibility of I/O device windows. Device windows that are
hidden or obscured may be raised by selecting the device.
- Debug: Some debug features.
File
FORTRAN
(Optional) Compile a FORTRAN IV program,
and assemble resulting code
into memory for running. This option only exists if there is the
Fortran4Embedded.jar file on the classpath (typically in the
current directory or location of H2000.jar).
Assemble
Assemble a program into memory. If the monitor has been activated,
the program will be assembled into a memory region that is relocated
above the monitor, and the monitor data structures will be filled-in
to indicate how to run the job.
Monitor
Assemble the monitor program and setup the Assemble option to use it.
There is a monitor program supplied in the sample programs tarball,
"monitor.ezc".
When the monitor is active, this menu option will be disabled (grayed-out).
Clicking INITIALIZE (after STOP) will reset monitor mode.
Disk Util
Initialize Volume
Initialize a disk pack for use with MOD1 programs.
Disk packs must be mounted onto disk drives before they can be initialized.
Both FMT and DAT PERMIT switches must be ON.
Input the disk drive unit, 6-character volume name, and
6-character volume serial number.
Map Volume
Show contents of a MOD1 disk pack volume.
Input the disk drive unit.
Options exist for adding Cylinder/Track map (file allocation usage)
and Partitioned Sequential Member Index contents.
Allocate File
Create a MOD1 disk file on a volume.
Both FMT and DAT PERMIT switches must be ON.
Input the disk drive unit, 10-character file name,
item/record/block parameters, and allocation units.
Deallocate File
Delete a MOD1 disk file from a volume.
The DAT PERMIT switch must be ON.
Input the disk drive unit and 10-character file name.
Bootstrap Generator
Write the bootstrap track on a disk volume.
The DAT PERMIT switch must be ON.
See "Bootstrap" in MOD1 Implementation for
more information.
Debug
Trace
Trace is enabled for the range of memory of the last assembled program.
Trace output will appear on the line printer.
Trace Full
A dialog is presented for specifying the range of memory to trace.
Trace Off
Cancel any active tracing.
Dump
A memory dump is printed to the Line Printer for the range of memory of the last assembled program.
Dump Full
A dialog is presented for specifying the range of memory to dump.
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:
- "1HDRΔ" record (skipped during bootstrap)
- The loader, bootmt.mti, including bootstrap and loader records
- The program image in BRT format, single segment, multiple records
- "1EOFΔ" record
- 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.