From: Mary Ann Horton <mah@mhorton.net>
To: Brian Walden <tuhs@cuzuco.com>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] banner (was troff was not so widely usable)
Date: Sat, 13 Feb 2021 09:13:05 -0800 [thread overview]
Message-ID: <fbf5d918-2253-a986-dc78-60582b6ef57c@mhorton.net> (raw)
In-Reply-To: <202102130900.11D903MT021054@cuzuco.com>
Thank you for the kind words, and the inspiring story of your port to
FORTRAN! I was surprised to find there is a Wikipedia page for the
banner program.
This brings back earlier memories for me. In High School in 1972, our
school had an ASR33 and dial-up access to an HP BASIC system. We were
also lucky enough to be part of a scouting program that gave us access
to a UNIVAC 1108 mainframe at nearby Gulf General Atomic, where we could
keypunch and run FORTRAN programs and print onto a fast line printer.
One of my programs was a simpler banner program, printing large sideways
banners with the 5x7 dot matrix I'd seen on Decwriters and CRT
terminals. I drew and typed in the data by hand, a far simpler job since
it was only 5x7, and the output was blocky.
I supported upper and lower case, but like the terminals, there was no
room below the baseline for descenders, and characters like "g" wound up
elevated. I printed our high school catch phrase, "Debug Off Line!", and
posted above the ASR33 at school. I got lots of crap about how the g
looked like a 9.
One friend signed my senior high school yearbook with the tag line
"Debu9 Off Line!"
On 2/13/21 1:00 AM, Brian Walden wrote:
> Thank you for banner! I used the data, abliet modified, 40 years ago
> in 1981, for a banner program as well, on an IBM 1130 (manufactured 1972)
> so it could print on an 1132 line printer. The floor would vibrate
> when it printed those banners. I used "X" as the printed char as the
> 1132 did not have the # char. But those banners looked great!
> I wrote it in FORTRAN IV. On punched cards. I did this because
> from 1980-1982 I only had access to UNIX on Monday evenings from
> 7PM-9PM, using a DEC LA120 terminal, it was slow and never had
> enough ink on the ribbon.
>
next prev parent reply other threads:[~2021-02-13 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 9:00 Brian Walden
2021-02-13 15:20 ` Will Senn
2021-02-13 16:57 ` Warner Losh
2021-02-13 20:09 ` Dave Horsfall
2021-02-13 20:28 ` [TUHS] Any interest in a Dec Alpha or a Sun Sparc 4 Jim Capp
2021-02-13 20:36 ` Earl Baugh
2021-02-13 20:45 ` Jim Capp
2021-02-13 21:24 ` Earl Baugh
2021-02-13 22:13 ` Grant Taylor via TUHS
2021-02-13 22:21 ` [TUHS] banner (was troff was not so widely usable) Mike Markowski
2021-02-14 0:27 ` Mary Ann Horton
2021-02-14 3:33 ` Will Senn
2021-02-15 17:32 ` Tom Lyon
2021-02-13 17:13 ` Mary Ann Horton [this message]
2021-02-16 19:29 Brian Walden
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=fbf5d918-2253-a986-dc78-60582b6ef57c@mhorton.net \
--to=mah@mhorton.net \
--cc=tuhs@cuzuco.com \
--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).