The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: steve jenkin <sjenkin@canb.auug.org.au>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Thu, 3 Nov 2022 12:18:22 -0400	[thread overview]
Message-ID: <CAC20D2PC=k-OO7wNFC0sawgQ0z4CNwESzvVREe-6P8Rspt6quA@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VRiSt6kCrFbOBOkxxsN=bEN-6wf5E6r_gX22Mc0dczz1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

On Thu, Nov 3, 2022 at 11:19 AM Paul Winalski <paul.winalski@gmail.com>
wrote:

> The LA36 DECwriter had a rather slow carriage return.  It would buffer
> characters while a return was in progress and then print the buffered
> characters at 60 characters/second, slowing down to the normal 30 cps
> when caught up.
>

The key point here is that with the DEC Writer (LA36) DEC started to split
the print speed (*in cps*) from the line interface speed (*in baud* as it
was larger than an often character as it would have at least one start bit,
one or more stop bits, and maybe a parity bit too).   Herein also lies
another problem, the mechanical interface, be it how fast the carriage
moved, or the head was positioned, etc, could be much longer than the
single character transfer time.  As Paul mentioned on some
mechanical devices without any buffering, the print might be random as the
carriage moved the head.

Teletype made an amazing mechanical device that had a minimum amount of
electronics in it.  By the time of the LA36, you start to see the
microprocessor revolution and the use of cheap transistors to replace
mechanical things to make faster/better devices with new features (like
buffering and being able to have different speeds for data transfer and
printing).   But you also start to see the distinction between the
mechanics (the keyboard/printer) and things like the communications scheme
become even more obvious and terminology starts to be used to address the
specific part of the problem.
ᐧ

[-- Attachment #2: Type: text/html, Size: 2490 bytes --]

  reply	other threads:[~2022-11-03 16:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole [this message]
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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='CAC20D2PC=k-OO7wNFC0sawgQ0z4CNwESzvVREe-6P8Rspt6quA@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=paul.winalski@gmail.com \
    --cc=sjenkin@canb.auug.org.au \
    --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).