Note that this is not the fully general Massbus implementation people were dreaming of. MB#1 is for RP/RM, MB#2 is for TU, and MB#3 is for RS.
I know that there were requests for four Massbus channels and multiple RP/RP subcontrollers, but if people want more disks, they can use the RQ.
- Fixed set MTAB dispatching to not dispatch to unit specific routines when only a device is specified in the command
- Fixed HELP dev SET output to avoid displaying SET commands which aren't valid for SHOW only cases
Prior fix for cursor tracking allowed this to now be observed.
The description of the prior change should have been:
The status bits need to be set in the upper byte of the DUART receiver buffer. This is not mentioned in the DEC manual but I found a Phillips datasheet for the 2681 chip, which has a small footnote about it.
sim> set debug -r -a -t -p somefile
-a produces seconds.msec time format
-t produces hh:mm:ss.msec time format
-r causes time values displayed to be relative to the wall clock time when the 'set debug' command was issued
-r by itself will cause default of -t
-a and -t can both be specified if desired
-p adds display of current PC value to the debug timestamp output
sim> show debug
Show IOSPACE doesn't always get the number of devices right due to device creativity.
o The distinction between UNIT and DEVICE has blurred
o MUX devices merge several physical devices into one device/unit
o Dynamic device sizing has made things more volatile.
This edit solves the problem for SHOW IOSPACE by adding an (optional) word to the DIBs.
The word contains the amount of IO space consumed by each instance of the physical device that's being emulated.
E.G., if it's a DZ11, the device is the DZ11 module, or 8 lines, even though the MUX device may support 32.
This enables SHOW IOSPACE to determine the number of physical devices being emulated, which is what folks need when configuring software. The word may have other uses - in a generic dynamic device sizing routine - which is why the amount of IOSPACE per device was chosen rather than the 'number of physical devices.'
The edit should not make any existing device regress. If the new word (ulnt) is zero (not initialized), SHOW IOSPACE will default to the number of units in the device, or if there's no device (CPUs), 1 as before. If it is present, the number of devices is the calculated as total allocation/allocation-per-device.
The edit updates all the devices that seem to require this treatment, and all the processors that define the UNIBUS/QBUS DIBs.
EA calc of interrupt instructions is an extension by SimH, and performed incorrectly. Indirect references are resolved in current context, not exec mode.
Since the Console Execute emulation takes advantage of this extension, correct it to calculate the EA in EXEC mode.
Make the card reader work on TOPS-10 and TOPS-20.
Augmented Image ECO was not implemented.
Simplify UI by defining commands for the various options/models emulated based on the simulator being built.
Document, and make the help conditional on model where that reduces clutter.
Deal with <CR><LF> reading ASCII files (file is opened 'rb' in scp's attach ; it shouldn't be.
Add translation support for DEC 026/029 full 7-bit ASCII, an ANSI standard & used by TOPS-10/20.
Deliver EOF at the correct time(s).
Preliminary support for update to card image spec being negotiated with the author.
Add Optical VFU support
Correct some inconsistencies with the hardware.
Add documentation and help.
Flush output file after 10 seconds of idleness to allow external watchers/processors to access entire job without forcing a simulator halt or detach/attach.
Make CR return to column 0, not column 1.
Make DAVFU contents accessible via SHOW.
Initialize RAM structures on power-up reset, but not reboot.
Implement keep-alive and os-requested reload functions of FE.
Preserve HW config flags during (re-) boot.
Allow IPL30 device to interrupt.
Add 18-bit DMA functions.
Implement DMA to/from I/O space.
Optimize DMA memory mapping - once per page, not once per byte.
Teach SHOW IO to report vectors and BR levels as well as CSR addresses.
Add DUP and KDP to Autoconfigure table.
Make the boot ROMs a bit easier to maintain.
Add assertion that the two variants of each are the same size.
Add offsets to the comments so it's easier to see where jumps are going.
The boot rom for tape didn't handle a tapes coming on-line, didn't take
the RH/TM/addresses from the FE. The launcher also didn't handle
autoboot.
Now it does, with the restriction that ITS will only talk to UBA1.
The boot rom for tape didn't handle a tapes coming on-line, didn't take
the RH/TM/addresses from the FE. The launcher also didn't handle
autoboot.
Now it does, with the restriction that ITS will only talk to UBA1.
The KS10's 8080 interfaces to the OS thru a small communications region.
The documentation is rather lacking, and the 8080 microcode is difficult
to follow. Many years ago (while still at DEC), I worked it out, and
put definitions into TOPS-10. They're now here, too.
Also, properly initialize the KLINIK communication words and the
keep-alive word.
