The @ TECO binary is from the . directory on many backup tapes going
all the way back to 1971. The LPT 11 and MACTAP F68 sources come
unchanged from Peter Samson's "RandomSystem" DECtape. The TECO DUMMY
file is close to the undated SYSENG; TECODM 2 file.
The source files can be assembled with MIDAS 73, and linked with the
Muddle version of STINK. The link order is TECO DUMMY, LPT, MACTAP,
TECO.
This results in a binary that is identical to the original @ TECO with
a few exceptions:
- @ TECO has a loader in 20-37, and something in 776000-777777.
- MOBY is set to 174000 for 64K core, which results in MACDMP being
1777400 and MACCR being 177777. The @ TECO binary has it set to
DSKDMP at 777700.
- The buffer size in MEMSIZ is not the same.
- CONSTANTS has one additional zero at the end, shifting the rest
of the memory image up by one word.
The links to RAKASH NAMDRG and TVFIX were wrong due to an added
semicolon at the end of the :LINK command. This would cause the
automatic TV-11 stuffing to fail, and also not start the name dragon.
KA10 specific programs: DECtape tools, programs related to the Rubin
10-11 interface (including the Knight TV), programs using the 340
display, and programs using the PDP-6.
KL10 specific programs: microcode, frontend programs, and LSPEED.
KS10 specific programs: microcode, frontend programs, MTBOOT, and TENTH.
disk parameters to separate file (system;rp04 >) from system;rh10 >.
Made build default to RP04 when RH10 is specified, but switches
can select RP06 for relevant components. Resolves#1648.
C; [CREL] 16 is timestamped 1981, but [CLIB] 16 is dated 1986.
Probably the latter was patched not to use the obsoleted UFA
instruction not supported by the KS10 machines.
Since we're interacting with ITS through the system console, one cause
of build failures is the messages the system job prints to the console
at unpredictable times -- for example, periodic timestamps and
notifications of changes to files in system directories. If one of these
gets printed while we're expecting something else, it's hard for the
Expect script to recover.
Avoid this by patching STYO, the system job's character-printing
routine, to return without doing anything if this system is up.
Adjust the pdset routine so it's matching PDSET's output rather than the
system job's to tell when the time has been set.
- Add packs to SALV.
- Increase NQS in ITS.
- Add new drives to the emulator configuration.
- Mark two more packs in SALV.
- Before booting into the new ITS, use UCOP to copy the MFD to the fresh packs.
