🚀 go-pugleaf

In article <16...@yenta.alb.nm.us> d...@yenta.alb.nm.us (David B. Thomas) writes:
>My Epson Equity 3 (IBM clone) at work makes little noises when doing processing.
>The noises are not coming from the speaker or the monitor, and when I adjust the
>CPU speed switch, the sounds speed up and slow down.  They are usually scratchy
>sounding, but under certain circumstances it whines or hums.  Perhaps a ceramic
>capacitor or resonator is piezo-ing...just a guess.

Changes in power demand can make switching power supplies make noises.
Iris workstations are notorious for this.
-- 
NFS:  all the nice semantics of MSDOS, | Henry Spencer at U of Toronto Zoology
and its performance and security too.  |  he...@zoo.toronto.edu   utzoo!henry

I have a program for my Commodore 64 the bangs the disk drive head into
the head stop at musical frequencies and plays "A Bicycle Built for Two."
I always thought that was neat, and it seems relevant.

-------------------------------------------------------------------------------
Jeff Axelrod                 | "If you chose not to decide, you still have made
                             |  a choice" -Neil Peart, Rush   /// 
ja2...@uxa.cso.uiuc.edu     |                              \XX/ AMIGAUSER
-------------------------------------------------------------------------------

In article <1990Jul12....@ux1.cso.uiuc.edu>, ja2...@uxa.cso.uiuc.edu (*** Jeff ****) writes:
> I have a program for my Commodore 64 the bangs the disk drive head into
> the head stop at musical frequencies and plays "A Bicycle Built for Two."
> I always thought that was neat, and it seems relevant.
> 
> -------------------------------------------------------------------------------
> Jeff Axelrod                 | "If you chose not to decide, you still have made
>                              |  a choice" -Neil Peart, Rush   /// 
> ja2...@uxa.cso.uiuc.edu     |                              \XX/ AMIGAUSER
> -------------------------------------------------------------------------------
I had a similar program for mine, the only difference being that the
final chord broke the drive.. :-(
-- 
Matti Nyk{nen
CS Student at Helsinki U, Finland
email: mnyk...@cc.helsinki.FI

The best opinions available; get them while they're hot!

In article <16...@yenta.alb.nm.us>, d...@yenta.alb.nm.us (David B. Thomas) writes:
> My Epson Equity 3 (IBM clone) at work makes little noises when doing processing.
> The noises are not coming from the speaker or the monitor, and when I adjust the
> CPU speed switch, the sounds speed up and slow down.

The only machine I ever heard rumors of the cause being traced down on (the
Digilog Microterm II), it turned out to be electrical noise being picked up
by the amplifier for the speaker.

It's actually quite nifty; you can get a good feel for what the machine's
doing just by listening. For example, you can tell whether your program's
stuck in an infinite loop or actually doing loops.

I have a friend that actually went out of his way to ensure that the
speaker amplifier in one of his new designs would have plenty of opportunity
to pick up noise to duplicate this; he ran the input wires all over just
for this reason.

===============================================================================
Roger Ivie

35 S 300 W
Logan, Ut.  84321
(801) 752-8633
===============================================================================

In article <16...@yenta.alb.nm.us> d...@yenta.alb.nm.us (David B. Thomas) writes:
>My Epson Equity 3 at work makes little noises when doing processing.
>
>I seem to remember hearing of a computer that was made to play Greensleves,
>as a side effect of going other processing.  Did the noise use to come from
>nearby AM radios?  The circuitry itself?

Back around 1976, when I was a student at LeTourneau College, we had an 
ancient (even for those days) IBM 1130.  One of the lab assistants, Harvey
Block (are you out there Harv?), got the bright idea of hooking a signal 
tracer to the least significant bit of the accumulator extension (well, 
actually the panel light for it.)  The result was a lot of interesting
noises whenever the machine was processing.  A couple days later, I went
down to the lab; Harvey caught me at the door and said "Watch this!".
The room was full of beginning FORTRAN students struggling with their 
programs.  Harvey quickly turned on the signal tracer, started his program,
and stood back as the computer played a very credible rendition of "Popcorn".
Needless to say, all other activity in the room ceased for a while.

Tim McGuire
mcg...@cs.tamu.edu

Anyone else have any good music stories, or adventures with the ol' 1130?

Tim McGuire (mcg...@cs.tamu.edu) writes:
+--
| Anyone else have any good music stories, or adventures
| with the ol' 1130?
+--

In the mid-seventies, IBM brought out an early desktop
computer called the 5100.  It had a one-line display with
room for about 24 characters.  A toggle switch selected
one of two languages, BASIC and APL.

The APL was appallingly slow---to generate a random
permutation of the first five natural numbers, and then
sort it, took several seconds---but it was very solid.

Years later I heard a rumor that explained how they could
generate a solid new APL implementation in such a short
time.  The 5100 used the IBM 1130 instruction set as its
internal micro-machine!  So its implementation had the
robustness that comes from many years of being tortured by
canny young programmers in small colleges all over the
country.
-- 
John Shipman/Zoological Data Processing/Socorro, NM/jo...@jupiter.nmt.edu
``Let's go outside and commiserate with nature.''  --Dave Farber

In article <1990Jul12.1...@zoo.toronto.edu> he...@zoo.toronto.edu (Henry Spencer) writes:
%
%Changes in power demand can make switching power supplies make noises.
%Iris workstations are notorious for this.
%-- 
%NFS:  all the nice semantics of MSDOS, | Henry Spencer at U of Toronto Zoology

   How about those  U.K.  produced  ICL minis which  had a speaker  hooked
   into the address bus (buffered/summed/amp'ed??) and constantly produced
   a horrendous series of cackles and whoops.

   Legend has it that `real' ops could tell exactly what the beasties were
   doing by just listening to this  cacophony (there were probably a  fair
   proportion of ops  carted off by  the little men  in white coats  after
   being subject to it for days at a time, too!!)
  ---------------------------------------------------------------------------
 |   John Little - gai...@Japan.Sun.COM  |  Sun Microsystems. Atsugi, Japan  |
  ---------------------------------------------------------------------------
              - A fool must now and then be right by chance -

We have a Versatec 8836-II Laser Plotter which has a number of little
motors in it (I'm not sure what they're for; separate rollers or
something?), and when it's plotting, it comes out with the most
amazing little whispers, like Hewey, Dewey and Lewey in Silent
Running.  Very musical (well I think so).

SL...@cc.usu.edu (Roger Ivie) writes:

>The only machine I ever heard rumors of the cause being traced down on (the
>Digilog Microterm II), it turned out to be electrical noise being picked up
>by the amplifier for the speaker.

Tonight I finally had the energy to remove the cover from the pc and poke
around.  Sure enough, the noise was coming from the speaker, but was not
affected by the volume control -- it's leaking into the speaker amp!

						David

In article <1990Jul14.2...@nmt.edu> jo...@nmt.edu (John Shipman) writes:
>Years later I heard a rumor that explained how they could
>generate a solid new APL implementation in such a short
>time.  The 5100 used the IBM 1130 instruction set as its
>internal micro-machine!  So its implementation had the
>robustness that comes from many years of being tortured by
>canny young programmers in small colleges all over the
>country.

I remember the APL implementation on the 1130.  You essentially had to use
the 1130 as a "personal computer".  It didn't make one very popular with the
FORTRAN crowd who were used to batch processing.  Anyone out there who 
actually used 1130 APL?

Tim McGuire
mcg...@cs.tamu.edu


---   .sig under construction

In article <66...@helios.TAMU.EDU>, mcg...@cs.tamu.edu (Tim McGuire) writes:
> I remember the APL implementation on the 1130.  You essentially had to use
> the 1130 as a "personal computer".  It didn't make one very popular with the
> FORTRAN crowd who were used to batch processing.  Anyone out there who 
> actually used 1130 APL?

Depends on what you meant by ``used''.  Do you remember the keyboard?
ARRGHHH!

That's better, I've calmed down.  Let me explain the keyboard situation.
APL requires a large (and unusual) character set.  The 1130 had a keyboard
stolen from an 029 keypunch.  (In fact, it even provided input in
card code.  But for some reason, they left the multipunch key off
on the 1130...)  The 029 didn't have nearly enough keys, hence the 1130
didn't, either.  So some brilliant soul assigned *3* meanings to each
key, and decreed two keys to be shift.  One shifted up, and the other
shifted sideways.  (The images come from the little decals you were
supposed to glue to the front of each key.)  If you hit a shift key
twice, it locked you in that mode.  Fortunately, the 1130 was reasonably-
well equipped with blinking lights, so the accumulator and extension
registers would indicate the current shift status of the keyboard.

That said, the rest of the APL system was really a waltzing bear sort
of thing.  I'm still amazed they crammed that much code into so little
space, even with the disk I/O they had to do for almost anything.  But
that made things run *very* slowly.  Still, it was better than the
drain-bamaged FORTRAN the machine had.

In article <1990Jul12....@ux1.cso.uiuc.edu> ja2...@uxa.cso.uiuc.edu (*** Jeff ****) writes:
>I have a program for my Commodore 64 the bangs the disk drive head into
>the head stop at musical frequencies and plays "A Bicycle Built for Two."

Hopefully you won't run this too often.  Probably the biggest problem
with the original 64 (besides having a poorly shielded video section) was
that the old 1541(?) drives were poorly ventilated, and if you let the
drive heat up enough, the head stop setscrew would loosen up and boom,
your stepper alignment lost its zero on the next boot.

-dave

--
Dave Hsu	 Sun Microsystems MS 14-40    (415) 336 5253    in a pinch:
h...@Eng.Sun.COM  2535 Garcia Avenue, Mountain View, CA 94043  h...@eng.umd.edu
"Are you familiar with Twiggly, the gnome who guards the entrance
 to the Cave of Knowledge?"		"Ah, yes yes.  Twiggly!"

In article <5...@exodus.Eng.Sun.COM> h...@hangfire.Eng.Sun.COM (Dave Hsu [Contractor]) writes:
-In article <1990Jul12.173410.7060@ux1.cso.uiuc.edu- ja2...@uxa.cso.uiuc.edu (*** Jeff ****) writes:
--I have a program for my Commodore 64 the bangs the disk drive head into
--the head stop at musical frequencies and plays "A Bicycle Built for Two."
-
-Hopefully you won't run this too often.  Probably the biggest problem
-with the original 64 (besides having a poorly shielded video section) was
-that the old 1541(?) drives were poorly ventilated, and if you let the
-drive heat up enough, the head stop setscrew would loosen up and boom,
-your stepper alignment lost its zero on the next boot.

In that case, open the 1541, loosen the two screws holding the stepper
and slowly twist it back and forth until it works.  I had to do this a
few times on mine :-)  By the way, never stack 1540 and older 1541 drives.
The bottom one can get so hot that its case will melt to the one above.
I once saw a stack of three 1540s that were fused together :-)
/mike

-Dave Hsu	 Sun Microsystems MS 14-40    (415) 336 5253    in a pinch:
-h...@Eng.Sun.COM  2535 Garcia Avenue, Mountain View, CA 94043  h...@eng.umd.edu

\|/ Michael L. Ardai     ar...@bu-pub.bu.edu   
--- ---------------------------------------------------------------
/|\ ...!sun!teda!maven.dnet!ardai (preferred)

In <65...@helios.TAMU.EDU> mcg...@cs.tamu.edu (Tim McGuire) writes:

>In article <16...@yenta.alb.nm.us> d...@yenta.alb.nm.us (David B. Thomas) writes:
>		...	got the bright idea of hooking a signal 
>tracer to the least significant bit of the accumulator extension (well, 
>actually the panel light for it.)  The result was a lot of interesting
>noises whenever the machine was processing.  

The first computer I ever learned to fix was an (ancient!) Burroughs
B-825(I think), used by the USAF as an early warning system.  This 
guy was a real MONSTER!! Power consumption was    65 KW/Hr !!!!
Each cabinet was 4'x4'x6-7'tall, and there were between 6 & 12 !~!!!

I remember that the memory cabinets were really sophisticated; they
 were dual memory units - each cabinet had 2  ....64Kb..... _CORE_	
memory units.   WoW! .:-)

Anyway, the main console had a speaker and amp in it; the input to 
the amp was from the LSB of the main accumulator (register, for you
youngsters out there!).  After some time, you could tell the 
approximate state of the machine by listening to the "tune" coming
from the console.


Years later, when I worked on various DEC PDP based equipment,
we would often take an FM radio into the computer room, tune it
up & down the dial until we found the CPU.  This actually turned
out to be a valuable troubleshooting tool, at times.



-- 
-------------------------------------------------------------------------------
Michael G. Hart   ha...@blackjack.dt.navy.mil /  mh...@dtrc.dt.navy.mil
DTRC/DoD			  |  "Wherever you go, there you are."- me
DISCLAIMER: If you want the Navy's opinion, talk to Secretary Cheney.
--
-------------------------------------------------------------------------------
Michael G. Hart   ha...@blackjack.dt.navy.mil /  mh...@dtrc.dt.navy.mil
DTRC/DoD			  |  "Wherever you go, there you are."- me
DISCLAIMER: If you want the Navy's opinion, talk to Secretary Cheney.

In article <66...@helios.TAMU.EDU> mcg...@cs.tamu.edu (Tim McGuire) writes:

| In article <1990Jul14.2...@nmt.edu> jo...@nmt.edu (John Shipman) writes:
| >Years later I heard a rumor that explained how they could
| >generate a solid new APL implementation in such a short
| >time.  The 5100 used the IBM 1130 instruction set as its
| >internal micro-machine!  So its implementation had the
| >robustness that comes from many years of being tortured by
| >canny young programmers in small colleges all over the
| >country.
| 
| I remember the APL implementation on the 1130.  You essentially had to use
| the 1130 as a "personal computer".  It didn't make one very popular with the
| FORTRAN crowd who were used to batch processing.  Anyone out there who 
| actually used 1130 APL?

Yep, I spent many an afternoon hacking away at the IBM 1130 we had at
the Baltimore Polytechnic Institute (public high school).  I was there
from fall 1971 to spring 1973, but I didn't take computers until my
second year.  While I did primilarly use Fortran in a batch card
environment, towards the end I did use APL and do all of the typical
'I can do this in one line of programming' that goes along with APL.

I remember once being left alone with instructions to shut the machine
down when I was done.  I did turn off the master power switch, only to
discover that you really had to shut off the periphials first
(everybody assumed that since I hung around, I knew how to shut things
down), and that I trashed the APL master disk.  As I recall, we got a
backup copy of the disk from a local community college.

--
Michael Meissner	email: meis...@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA

Do apple growers tell their kids money doesn't grow on bushes?

The prototype of the 5100 in the Smithsonian used an 1130 emulation; as this did not produce adequate results, production models used 360 emulation for APL instead. Both emulated the System/3 for BASIC.

On 5/5/2018 2:17 PM, Quadibloc wrote:
> The prototype of the 5100 in the Smithsonian used an 1130 emulation; as this did not produce adequate results, production models used 360 emulation for APL instead. Both emulated the System/3 for BASIC.
> 

I had access to APL\360 and the IBM 5100 in college.  There was at least 
one instance... when the two got different answers when evaluating the 
same expression.  How could that be... if the 5100 emulated APL\360???

-- 
numerist at aquaporin4 dot com

The 5100 ran a modified VS APL, not the earlier APL/360.

On Sat, 5 May 2018 14:28:35 -0700 (PDT), Quadibloc <jsa...@ecn.ab.ca>
wrote:

>The 5100 ran a modified VS APL, not the earlier APL/360.

And it depends on the details of the emulation.  There might have been
some compromises required.

On Saturday, May 5, 2018 at 3:28:37 PM UTC-6, Quadibloc wrote:
> The 5100 ran a modified VS APL, not the earlier APL/360.

It was APLSV.

On Saturday, May 5, 2018 at 5:19:00 PM UTC-4, Charles Richmond wrote:
> On 5/5/2018 2:17 PM, Quadibloc wrote:
> > The prototype of the 5100 in the Smithsonian used an 1130 emulation; as this did not produce adequate results, production models used 360 emulation for APL instead. Both emulated the System/3 for BASIC.
> > 
> 
> I had access to APL\360 and the IBM 5100 in college.  There was at least 
> one instance... when the two got different answers when evaluating the 
> same expression.  How could that be... if the 5100 emulated APL\360???

Care must be taken when using the words "emulation" vs. 
"simulation".  In IBM parlance, "simulation" meant that a
software program simulated another machine.  In the prep for 
S/360, IBM found that simulators ran rather slowly.  In contrast,
"emulator" referred to hardware features, such as microcode, that
mimicked another machine.  IBM found that microcode emulation ran
fast and was suitable for S/360 to act as older machines, a major
selling point.

Has anyone used a S/360 emulating a 7090 series machine, especially
with floating point work?  How did that work out?