The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tom Ivar Helbekkmo via TUHS <tuhs@minnie.tuhs.org>
To: Robert Clausecker <fuz@fuz.su>
Cc: coff@tuhs.org, TUHS@tuhs.org
Subject: Re: [TUHS] Monitoring by loudspeaker
Date: Sun, 23 Aug 2020 10:58:19 +0200	[thread overview]
Message-ID: <m27dtpu4b8.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <20200712145822.GA72854@fuz.su> (Robert Clausecker's message of "Sun, 12 Jul 2020 16:58:22 +0200")

Robert Clausecker <fuz@fuz.su> writes:

> When the computer is in a tight endless loop, the accumulator takes the
> same series of values every time it's in the loop.  Thus, instead of
> white noise you get a sound whose frequency is the clock frequency of
> the machine divided by the number of cycles spent by one loop iteration.

A buddy and I did something somewhat related back in the early eighties,
when we were teaching ourselves programming, using, among other things,
his Tandy TRS-80 home computer.  We discovered that a cheap "transistor
radio", sitting close to the computer, would be affected by the noise
generated by it, and then we figured out that if we didn't tune it to a
radio station, we'd get only the noise.  Leaving that on as we worked on
a program, we got familiar with the sound of the code, and became able
to follow the execution by the changing patterns -- and if it did get
stuck in a loop somewhere, we'd not only hear it, but we would also have
a pretty good idea where it happened.

-tih
-- 
Most people who graduate with CS degrees don't understand the significance
of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay

  parent reply	other threads:[~2020-08-23  9:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  1:08 [TUHS] AT&T Research John P. Linderman
2020-07-11  1:32 ` Larry McVoy
2020-07-11  1:51   ` John P. Linderman
2020-07-11 15:36 ` Clem Cole
2020-07-11 20:30   ` Warren Toomey
2020-07-11 20:36     ` Jon Steinhart
2020-07-11 21:58     ` Rob Pike
2020-07-11 22:29       ` Larry McVoy
2020-07-12  7:55         ` Ed Bradford
2020-07-12  2:22     ` [TUHS] BTL pranks [was AT&T Research] Doug McIlroy
2020-07-12 11:58       ` [TUHS] Monitoring by loudspeaker (was: BTL pranks) Michael Kjörling
2020-07-12 13:25         ` Dan Cross
2020-07-12 14:58         ` Robert Clausecker
2020-07-12 16:09           ` [TUHS] Monitoring by loudspeaker Al Kossow
2020-07-12 20:10             ` [TUHS] Fwd: " Rich Morin
2020-08-23  8:58           ` Tom Ivar Helbekkmo via TUHS [this message]
2020-07-23  4:13     ` [TUHS] AT&T Research scj
2020-07-23  6:02       ` [TUHS] Technical decisions based on political considerations [was Re: AT&T Research] arnold
2020-07-23 14:42         ` Larry McVoy

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=m27dtpu4b8.fsf@thuvia.hamartun.priv.no \
    --to=tuhs@minnie.tuhs.org \
    --cc=TUHS@tuhs.org \
    --cc=coff@tuhs.org \
    --cc=fuz@fuz.su \
    --cc=tih@hamartun.priv.no \
    /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).