From: Lawrence Stewart <stewart@serissa.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BTL summer employees
Date: Mon, 10 Aug 2020 13:08:20 -0400 [thread overview]
Message-ID: <81311578-1C53-47F3-930C-8F0A950D4284@serissa.com> (raw)
In-Reply-To: <20200810140216.47CB418C082@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 2870 bytes --]
> On 2020, Aug 10, at 10:02 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
>> From: Lars Brinkhoff
>
>> I haven't investigated it thoroughly, but I do see a file .DOVR.;.SPOOL
>> 8 written in C by Eliot Moss.
>> ...
>> When sending to the DOVER, the spooler waits until Spruce is
>> free before sending another file.
>
> Ah, so there was a spooler on the ITS machine as well; I didn't know/remember
> that.
>
> I checked on CSR, and it did use TFTP to send it to the Alto spooler:
>
> HOST MIT-SPOOLER, LCS 2/200,SERVER,TFTPSP,ALTO,[SPOOLER]
>
> I vaguely recall the Dover being named 'Spruce', but that name wasn't in the
> host table... I have this vague memory that 'MIT-Spooler' was the Alto which
> prove the Dover, but now that I think about it, it might have been another one
> (which ran only TFTP->EFTP spooler software). IIRC the Dover as a pain to run,
> it required a very high bit rate, and the software to massage it was very
> tense; so it may have made sense to do the TFTP->EFTP (I'm pretty sure the
> vanilla Dover spoke EFTP, but maybe I'm wrong, and it used the PUP stream
> protocol) in another machine.
>
> It'd be interesting to look at the Dover spooler on ITS, and see if/how one
> got to the CHAOS network from C - and if so, how it identified the protocol
> translating box.
>
> Noel
“A pain to run” and “tense” indeed! The Dover printing system was an Alto (6 MIPs <microinstructions>) driving “Orbit” hardware about half the size of the Alto itself*, driving the raster video to the printer. The hardware was called “orbit” because it could directly “OR” bits into the raster image, rather than requiring read-modify-write cycles. “Spruce” was the spooler and printer driver that ran on the Alto. Evidently the hardware is a typical Butler Lampson knife edge design up in the corner of what was possible, implemented by Bob Sproull and Severo Ornstein. Additional software by Dan Swinehart.
There’s a page about this in https://bwlampson.site/38-AltoSoftware/Abstract.html <https://bwlampson.site/38-AltoSoftware/Abstract.html> and a patent https://patents.google.com/patent/US4203154 <https://patents.google.com/patent/US4203154>. I have a feeling I’ve seen a longer description of Orbit somewhere but I can’t remember where.
Like most Stanford folks of the era I printed my thesis on one, assisted about 1 AM by Lyle Ramshaw who knew where to get a new drum for the printer.
In any event, a vast improvement over the XGP and a godsend for those of us who <didn’t> have a phototypesetter.
* An earlier one-off called EARS had printer hardware about 3 times the size of the attached Alto. That one was font-image based. To do things like lines and graphics the software constructed custom font glyphs to make up the image.
[-- Attachment #2: Type: text/html, Size: 4108 bytes --]
next prev parent reply other threads:[~2020-08-10 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:02 Noel Chiappa
2020-08-10 17:08 ` Lawrence Stewart [this message]
2020-08-10 18:13 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
2020-08-10 12:53 Noel Chiappa
2020-08-10 13:21 ` Lars Brinkhoff
2020-08-02 13:40 Doug McIlroy
2020-08-02 13:57 ` arnold
2020-08-02 17:13 ` Doug McIlroy
2020-08-03 9:24 ` arnold
2020-08-02 15:12 ` Robert Diamond
2020-08-02 19:05 ` Jon Steinhart
2020-08-03 5:14 ` Heinz Lycklama
2020-08-03 12:55 ` John P. Linderman
2020-08-03 16:26 ` Jon Steinhart
2020-08-10 0:48 ` Dave Horsfall
2020-08-10 0:53 ` Larry McVoy
2020-08-10 6:33 ` Lars Brinkhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81311578-1C53-47F3-930C-8F0A950D4284@serissa.com \
--to=stewart@serissa.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).