Computer Old Farts Forum
 help / color / mirror / Atom feed
Subject: [COFF] [TUHS] Monitoring by loudspeaker (was: BTL pranks)
Date: Sun, 12 Jul 2020 11:58:11 +0000	[thread overview]
Message-ID: <738ab925-586b-4921-b891-a4ec20348d4c@localhost> (raw)
In-Reply-To: <202007120222.06C2MtdJ140032@tahoe.cs.Dartmouth.EDU>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

(This should probably be on COFF because I don't think this has much
to do with UNIX.)


On 11 Jul 2020 22:22 -0400, from doug at cs.dartmouth.edu (Doug McIlroy):
> a loudspeaker hooked to the low-order bit of the accumulator played
> gentle white noise in the background. The noise would turn into a
> shriek when the computer got into a tight loop,

How did that work? I can see how tying the low-order bit of the
accumulator to a loudspeaker would generate white noise as the
computer is doing work; but I fail to see how doing so would even
somewhat reliably generate a shrieking sound when the computer is in a
tight loop. Please, enlighten me. :-)

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”



       reply	other threads:[~2020-07-12 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200711203020.GA1884@minnie.tuhs.org>
     [not found] ` <202007120222.06C2MtdJ140032@tahoe.cs.Dartmouth.EDU>
2020-07-12 11:58   `  [this message]
2020-07-12 13:25     ` crossd
2020-07-12 14:58     ` fuz
2020-08-23  8:58       ` [COFF] Monitoring by loudspeaker tih

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=738ab925-586b-4921-b891-a4ec20348d4c@localhost \
    --to=coff@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).