Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!hao!seismo!brl-tgr!gwyn From: gwyn@brl-tgr.ARPA (Doug Gwyn ) Newsgroups: net.unix-wizards Subject: Re: DMF-32 (and clones) versus DH-11 (and clones) versus DZ/KMC-11 Message-ID: <3283@brl-tgr.ARPA> Date: Sat, 14-Jul-84 20:23:45 EDT Article-I.D.: brl-tgr.3283 Posted: Sat Jul 14 20:23:45 1984 Date-Received: Thu, 19-Jul-84 02:30:02 EDT References: <832@bbncca.ARPA>, <4063@utzoo.UUCP> Organization: Ballistics Research Lab Lines: 13 The KMC11 is not at all horrid to program, if you use the software supplied with every AT&T UNIX release since System III. The source language is very like C, and about all that one would want to do is to make some very slight changes to the distributed source code, which is a lot easier than writing the whole driver. Most of the terminal driver was put into the KMC11, including input canonicalization and echoing. There should be no "Unibus problems" with the KMC11B. It can and does serve as a bus master, but so what? That is part of the Unibus design. I used to have a display processor (VR48) that was a second Unibus master; it worked fine.