The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org, segaloco@protonmail.com
Subject: [TUHS] Re: Original print of V7 manual? / My own version of troff
Date: Tue, 09 Jan 2024 13:05:14 -0500	[thread overview]
Message-ID: <202401091805.409I5EYv074287@ultimate.com> (raw)
In-Reply-To: <Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@protonmail.com>

Matt G wrote:
> On the subject of troff origins, in a world where troff didn't
> exist, and one purchases a C/A/T, what was the general approach to
> actually using the thing? ...  or say one of the DEC OSs?

Off-topic for this list, BUT:

At DEC/LCG (Large (36-bit) Computer Group) in the 80's when we got a
DEC LN01 (Xerox 2700 engine?) someone adapted an old typesetter
version of RUNOFF to drive it.  I heard tell that there was a dusty
C/A/T in one of the labs.

Mentions of Typeset-8, Typeset-10, and Typeset-11:
http://www.bitsavers.org/pdf/dec/pdp10/typeset-10/Typeset-10_Product_Proposal_197310.pdf

Typeset-8:
http://www.bitsavers.org/pdf/dec/pdp8/typeset8/
https://www.hewlettpackardhistory.com/item/at-the-turn-of-a-key/

  Digital Equipment Corporation’s TYPESET-8 pioneered the “turnkey”
  computer system, where a system was custom designed for a specific
  application and was ready to perform that application at the press
  of a button (or the turn of a key). The TYPESET-8 hardware and
  software package originally sold with the classic PDP-8 as its CPU
  and functioned as a computerized typesetting system. Digital
  Equipment Corporation joined Hewlett-Packard in 2002.

Typeset-11:
http://www.bitsavers.org/pdf/dec/pdp11/typeset-11/

TMS-11 is pretty sophisticated: RSX-11D with options a real disk
(RP03) or RK05, and a swap device (RF11/RS11), OCR input, VT20 (VT05 +
11/05-- first I've heard of it) but still with up to four paper tape
readers/punches.

The diagram at
http://www.bitsavers.org/pdf/dec/pdp11/typeset-11/EK-T11SY-OP-001_TMS-11_System_Managers_and_Usrs_Guide_Feb1975.pdf
shows direct hardware connection to a "photocomp machine", or via punched tape.

But, I haven't spotted any mention of specific typesetter hardware.

https://terminals-wiki.org/wiki/index.php/DEC_VT20 says:
The DEC VT20 terminal is a variant of the DEC VT05 terminal with special facilities for typesetting.

The VT20/B is another variant with a different enclosure.

  Two VT20/B terminals were connected to single PDP-11/05 (a variant
  of the 11/10) which was connected via RS232 to a host system, either
  a larger PDP-11 or a DECsystem-10, running Typeset-11 or
  Typeset-10. Newspapers using Typeset-10 were The Kansas City Star,
  the Chicago Tribune, and the London, Ontario, Free Press. The
  PDP-11/05 was booted by toggling in the bootstrap using the switches
  on the front of the machine, then downloading the abs loader and
  actual software through the RS232 interface from the host. The
  PDP-11/05 buffered text (news stories) downloaded from the host and
  allowed editing on the VT20. On Typeset-11 it was page oriented, a
  page would be downloaded, edited, then uploaded back to the host. On
  Typeset-10 the text was downloaded, but an associated memory system
  mirrored changes made on the text in the -11 to a copy on the
  -10. When the "save" button was pressed, the text was copied from
  associative memory into the actual text file on the
  DECsystem-10. This allowed for virtual scrolling through large files
  without having to save and load pages. The VT20s were eventually
  replaced by the VT72s, which featured a micro PDP-11 internally,
  with twice the memory of the old PDP-11/05s that controlled the
  VT20s. Interestingly enough, Digital no longer supported the
  associative memory version of the editing software, requiring page
  level editing. The Kansas City Star rewrote the PDP-11 software for
  the VT20s to run on the VT72, allowing for further virtual scrolling
  of large files, and making saving edits faster. The VT72 was
  replaced by the VT172, virtually the same terminal but in a VT100

  reply	other threads:[~2024-01-09 18:05 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 22:17 [TUHS] Original print of V7 manual? Mychaela Falconia
2024-01-05 23:19 ` [TUHS] " segaloco via TUHS
2024-01-06  0:12   ` Will Senn
2024-01-06  1:26   ` Mychaela Falconia
2024-01-06  5:08     ` segaloco via TUHS
2024-01-06  6:12       ` Mychaela Falconia
2024-01-06 15:06       ` Will Senn
2024-01-06  1:06 ` Al Kossow
2024-01-06  1:45   ` segaloco via TUHS
2024-01-06 14:42     ` amp1ron
2024-01-06  3:02   ` Mychaela Falconia
2024-01-06  3:22     ` G. Branden Robinson
2024-01-06  4:06       ` Jonathan Gray
2024-01-06  4:06       ` Mychaela Falconia
2024-01-06 18:33         ` Clem Cole
2024-01-06 21:04           ` Rich Salz
2024-01-06 21:38             ` Clem Cole
2024-01-10 16:32             ` Michael Parson
2024-02-10 19:43               ` Al Kossow
2024-01-07  2:17           ` Mychaela Falconia
2024-01-07  2:25             ` Al Kossow
2024-01-07  2:54             ` Phil Budne
2024-01-07  3:21               ` Mychaela Falconia
2024-01-07  3:55             ` Clem Cole
2024-01-10 16:53             ` Michael Parson
2024-01-10 17:45               ` Clem Cole
2024-01-07 10:54         ` Brian Walden
2024-01-07 12:12           ` arnold
2024-01-08  0:20           ` Mychaela Falconia
2024-01-07 21:59             ` [TUHS] My own version of troff Mychaela Falconia
2024-01-08  3:24               ` [TUHS] Re: Original print of V7 manual? / " G. Branden Robinson
2024-01-08  5:10                 ` Mychaela Falconia
2024-01-08  7:11                   ` G. Branden Robinson
2024-01-09  9:38                     ` Mychaela Falconia
2024-01-09 16:27                       ` Al Kossow
2024-01-09 17:18                         ` segaloco via TUHS
2024-01-09 18:05                           ` Phil Budne [this message]
2024-01-09 18:30                             ` Grant Taylor via TUHS
2024-01-09 20:29                           ` Al Kossow
2024-01-09 20:31                             ` Al Kossow
2024-01-09 22:07                           ` Clem Cole
     [not found]                   ` <CAGcdajdc5GfTOeP_Vw_AC0E6BdnrBLape1+GEd2JGDCg4n31eQ@mail.gmail.com>
2024-01-17 14:08                     ` G. Branden Robinson
2024-01-17 15:32                       ` Brad Spencer
2024-01-17 15:48                         ` Clem Cole
2024-01-17 16:25                           ` Rich Salz
2024-01-18  7:00                     ` Mychaela Falconia
     [not found]                       ` <CAGcdaje=RHbLNZv2Cy=xtuEMaYU7RXMtnom7gYuAMMju2xrHgw@mail.gmail.com>
2024-01-18  8:22                         ` Mychaela Falconia
2024-01-18 13:27                       ` G. Branden Robinson
     [not found]                     ` <ZalHs6DAuvRwXTuS@fluorine>
2024-01-19 16:52                       ` G. Branden Robinson
2024-01-06 14:52       ` [TUHS] Re: Original print of V7 manual? Will Senn
2024-01-06 16:52         ` Al Kossow
2024-01-06 16:54           ` Al Kossow
2024-01-06 18:28         ` G. Branden Robinson
2024-01-10 18:50 [TUHS] Original print of V7 manual? / My own version of troff tuhs
2024-01-10 22:04 ` [TUHS] " Diomidis Spinellis
2024-01-10 23:46   ` segaloco via TUHS
2024-01-11  2:20     ` Mychaela Falconia
2024-01-11 13:52 ` Sebastien F4GRX
2024-01-11 22:48 ` Dave Horsfall
2024-01-11 23:47   ` Greg 'groggy' Lehey

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=202401091805.409I5EYv074287@ultimate.com \
    --to=phil@ultimate.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@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).