jnc at mercury.lcs.mit.edu
Wed Jan 10 07:07:22 CST 2018
> From: Phil Budne
> ISTR the DTE was a DMA interface, not memory mapping like the DL10
I don't know either; I could probably work it out from looking at the DTE
documentation, which I'm too lazy/busy to do... :-)
> I also seem to recall that MC was designated as a "1080" which the above
> URL says means "Model A, External channels only, tall cabs
Yup, that's what it was.
> I remember finding documentation on MC for "KLDCP" the original DEC
> front-end software (suitably defaced) which DEC later replaced with a
> modified version of RSX-11
MC, on the other hand, ran KLDCP ('KL Diagnostic Console Program') until the
end. (The sources of DEC KLDCP version 7 are still available from the MC
dumps, if anyone wants them, along with the MIT-modified version.) The console
-11 on MC ran a 'combination' of IOELEV and KLDCP - the two remained pretty
much separate, just cooperated to share the machine:
KLDCP does JSR PC, [to 03000] when it has nothing to do and 10 is
running. IOELEV should INIT if it hasn't already, then go into its main
loop. It should CLC, RTS PC if the 10 goes down; KLDCP will print
appropriate message. To go into temporary KLDCP command mode, SEC, RTS PC.
I get the impression from the IOELEV source that it ran on the -11 connected
to the DL10 first (stand-alone, by itself), and was later adapted to share the
console -11 with KLDCP.
Amusing comment in the KLDCP source:
WE HAVE GONE TO CONSIDERABLE DIFFICULTY AND EXPENSE TO ASSEMBLE A STAFF OF
SORCERERS, SHAMANS, CONJURERS AND LAWYERS TO VISIT NETTLESOME AND MYSTIFING
DISCOMFORTS ON ANY NINNY WHO ENDEAVORS TO REPRODUCE OR USE THIS PROGRAM IN
ANY FORM OR BY ANY MEANS, ELECTRONIC OR OTHERWISE, INCLUDING COMPUTERS AND
INFORMATION SYSTEMS, WITHOUT PERMISSION FROM THE DEVELOPER. WATCH YOURSELF!
> diagnostic KLINIC (sp?) line).
KLINIK, according to KLDCP stuff.
More information about the cctalk