The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: earl.baugh@gmail.com (Earl Baugh)
Subject: [TUHS] Anyone know what a LANTERN is
Date: Mon, 31 Jul 2017 17:25:21 -0400	[thread overview]
Message-ID: <CANcLFn4yv4+uQCsYq_9G8o5dWMW5_P3n_gJP417Ka65xFpK5dA@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfpS794BAkHojf=_D63TvV-rVkBs6ACRYbBv5gCWkGboYg@mail.gmail.com>

I'll take any sound vs. the "visual bell" flash that I had on the first
terminal I used to learn VI on.
Had I had epilepsy like my sister, I'd have never survived :-)

Earl

On Mon, Jul 31, 2017 at 4:04 PM, Warner Losh <imp at bsdimp.com> wrote:

>
>
> On Mon, Jul 31, 2017 at 11:52 AM, ron minnich <rminnich at gmail.com> wrote:
>
>> ah, on the vt52, that "bell" was called the "feep". It sure was not a
>> bell.,
>>
>> The vt52 was a real money saving device. From what we could tell, the
>> printed circuit board on it was cardboard.
>>
>
> On the VT52 terminals I used, the bell seemed to come in two flavors. One
> was a very iconic "gear grinding" sound where there was a small motor that
> spun a toothed wheel that ran over a slender finger of plastic. A few,
> maybe retrofitted, had what sounded like a random 555 noise that was gated
> on/off.
>
> Warner
>
>
>> On Mon, Jul 31, 2017 at 9:51 AM Paul Winalski <paul.winalski at gmail.com>
>> wrote:
>>
>>> On 7/30/17, Alec Muffett <alec.muffett at gmail.com> wrote:
>>> > Dumb question: is there any chance that just as BEL goes <beep>,
>>> perhaps
>>> > LAMP illuminated a red warning light or similar?
>>>
>>> BEL *did* ring a bell on the model 33 Teletype.  On the DEC VT52, it
>>> sounded a buzzer that was sort of like an electronic raspberry.  On
>>> the VT100, LA36, and other later terminals, it was the familiar feep
>>> sound.
>>>
>>> The character we're discussing here was named LANTERN, not LAMP, but
>>> you may have something there regarding it turning on a light.  We'd
>>> need to find an AT&T 4410 terminal, or someone who's used one, to be
>>> sure.
>>>
>>> -Paul W.
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170731/56e9c167/attachment-0001.html>


  reply	other threads:[~2017-07-31 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 11:14 Doug McIlroy
2017-07-30 11:17 ` Alec Muffett
2017-07-31 16:50   ` Paul Winalski
2017-07-31 17:52     ` ron minnich
2017-07-31 20:01       ` Warner Losh
2017-07-31 20:04       ` Warner Losh
2017-07-31 21:25         ` Earl Baugh [this message]
2017-07-31 23:46     ` Kevin Schoedel
2017-07-30 17:43 ` Lyndon Nerenberg
2017-07-30 22:33 Norman Wilson

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=CANcLFn4yv4+uQCsYq_9G8o5dWMW5_P3n_gJP417Ka65xFpK5dA@mail.gmail.com \
    --to=earl.baugh@gmail.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).