The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Date madness
Date: Sat, 16 Dec 2017 10:45:56 -0500	[thread overview]
Message-ID: <CAC20D2PVgWuLWwzRR39HknjVXGkur_QRYkEakHAS5k43QZb3Rg@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VRxQYpAFxzhy3DbXHafo9VAwzhKxGZfVjMpUUm9zE=eSA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]

Apologies to Warren and the list for keeping this OT for UNIX thread going,
but it is history....

On Fri, Dec 15, 2017 at 11:41 AM, Paul Winalski <paul.winalski at gmail.com>
wrote:

> The first two VAXen, the 11/780 and 11/750, both had TOY clocks that
> ran when the machine was powered off.  The 11/730 was designed to be a
> low-cost VAX, and one of the ways they lowered the cost was
> elimination of the TOY clock.  VMS (and I assume also UNIX) asked you
> to enter the time whenever you cold booted the 11/730.
>
> After the 11/730 came out, Dick Hustvedt (lead VMS architect and
> engineer) and Stan Rabinowitz put together an elaborate April fool's
> hack.  On April 1, the 11/730 in the VMS group's machine room had next
> to it a pedestal with a sundial on it and a ribbon cable leading into
> the 11/730, with sales brochures placed next to it.  The sales
> brochures announced the SD730 Fixed Head Solar Horologue, a sundial
> with a photocell for detecting noon that could be used to
> automatically set the 11/730's time-of-day clock.  The thing actually
> worked--it was connected via a UNIBUS real-time device controller, and
> Hustvedt had written a VMS device driver for it.
>
> All VAXen after the 11/730 had TOY clocks.
>
> -Paul W.
>

​As Paul and us ex-DECies remember, that hack lived on for years.   The ZK0
site (*a.k.a.* Spitbrook Road in Nashua, NH) was nominally DEC's SW
bldging.   At each site, there was a theme for naming the conference rooms;
*i.e.* LK0 (Littleton King St) it was towns/villages in New England.
It conference room being so name had a nice touch and much more fun than a
boring naming scheme of SITE_BLD-FLOOR-RM#-SIZE (such as Intel). **  The
ZK0 site theme had been historically famous people from science and
mathematics (CS, *etc*.).   Each room had painted on a wall a little
history about the person(s) and was 'dressed' with something, usually on
the walls, to depict one of their infamous ideas/inventions (e.g. Babbage
had difference engine, Ada, had pictures of things she used to program it,
I've forgotten what was in von Nueman but you get the idea).  After his
accident, one of the large conference rooms in VMS land, was renamed ​Hustvedt
and had the SD730 in the corner along with the story.   When we (Intel)
moved out the building, HP was closing shop in large sites in NE.   They
had already sold the bldgs to the local real-estate firm that sublets
them.  I've often wondered what happened to those rooms and in particular
the SD730 itself.  That one really should be in the Computer Museum.

Clem



** For the couple of years after the team was sold to Intel but not
moved desks, *i.e.* still on the second floor of ZK2, we had kept the DECs
names of our two large conference rooms which actually had official Intel
names, but everyone still called them by their DEC names.
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171216/d876a92e/attachment-0001.html>


  parent reply	other threads:[~2017-12-16 15:45 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 17:16 Noel Chiappa
2017-12-13 18:53 ` Tom Ivar Helbekkmo
2017-12-13 20:46 ` arnold
2017-12-15 16:41   ` Paul Winalski
2017-12-15 17:19     ` Dave Horsfall
2017-12-16 15:45     ` Clem Cole [this message]
2017-12-16  3:39   ` Dave Horsfall
2017-12-16  3:45     ` Lyndon Nerenberg
2017-12-17  1:43       ` Dave Horsfall
2017-12-14  3:08 ` Dave Horsfall
2017-12-14  3:13   ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2017-12-16 10:50 Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11   ` Ralph Corderoy
2017-12-13 22:16 Norman Wilson
2017-12-14  0:24 ` Chris Torek
2017-12-17 16:20   ` Ron Natalie
2017-12-17 18:53     ` Tom Ivar Helbekkmo
2017-12-17 20:07       ` Ron Natalie
2017-12-13 20:22 Noel Chiappa
2017-12-13 19:12 Doug McIlroy
2017-12-14  3:07 ` Random832
2017-12-15  3:04   ` Random832
2017-12-13 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 15:56 Noel Chiappa
2017-12-12 18:31 Noel Chiappa
2017-12-12 18:01 Noel Chiappa
2017-12-12 18:21 ` Warner Losh
2017-12-13 15:07 ` Random832
2017-12-13 17:00   ` Jason Stevens
2017-12-13 17:18     ` Ron Natalie
2017-12-13 18:02       ` Arthur Krewat
2017-12-13 15:39 ` Wolfgang Helbig
2017-12-14  0:57 ` Dave Horsfall
2017-12-14 14:09   ` William Cheswick
2017-12-17 16:19     ` Ron Natalie
2017-12-17 16:33       ` William Cheswick
2017-12-17 17:54         ` Random832
2017-12-17 22:15           ` Dave Horsfall
2017-12-17 22:54             ` Ian Zimmerman
2017-12-16 18:12 ` Wolfgang Helbig

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=CAC20D2PVgWuLWwzRR39HknjVXGkur_QRYkEakHAS5k43QZb3Rg@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).