The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Ronald Natalie <ron@ronnatalie.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 11:17:38 -0400	[thread overview]
Message-ID: <CABH=_VRiSt6kCrFbOBOkxxsN=bEN-6wf5E6r_gX22Mc0dczz1w@mail.gmail.com> (raw)
In-Reply-To: <emc238c437-aa92-43b8-bb56-2eac700fab91@6b571117.com>

On 11/2/22, Ronald Natalie <ron@ronnatalie.com> wrote:
> I’m not sure the model 33 required a carriage return delay.   At 110
> baud it had plenty of time to move the carriage. back.
> Other printers (especially faster ones) weren’t so lucky, but the LA36
> decwriter had a catchup mode to print the backlog after a return.
> The LA120 was boustrophedonic so returns weren’t as much of an issue.

The model 33 had a very fast and powerful carriage return mechanism,
good for cracking walnuts, but it took up to two character times to
complete a CR.  If you didn't send two non-printing characters (such
as NUL), you risked having your character struck somewhere in the
middle of the line.

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.  There was a company that sold modified LA36
controller boards that were hacked so that the LA36 always thought it
was in catch-up mode and could thus be run at double speed, provided
that you inserted NUL padding after a CR.  But that greatly reduced
the longevity of the print mechanism.

-Paul W.

  parent reply	other threads:[~2022-11-03 15:19 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 [this message]
2022-11-03 16:18         ` Clem Cole
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='CABH=_VRiSt6kCrFbOBOkxxsN=bEN-6wf5E6r_gX22Mc0dczz1w@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=ron@ronnatalie.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).