Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!unix.cis.pittsburgh.edu!ejkst
From: ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy)
Newsgroups: comp.sys.amiga
Subject: Re: Installbeep ideas
Message-ID: <18809@unix.cis.pittsburgh.edu>
Date: 21 Jul 89 03:31:32 GMT
References: <19643@louie.udel.EDU> <1053@taurus.BITNET>
Reply-To: ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy)
Organization: Univ. of Pittsburgh, Comp & Info Services
Lines: 29

In article <1053@taurus.BITNET> asaph%math.tau.ac.il@CUNYVM.CUNY.EDU (Zemach Asaph) writes:

>installbeep has a bug. It crashes the machine when too many sounds are queued
>up to be played. To cause this bug, simply force to produce alot more sounds

I haven't seen this.  When I try that, the extra beeps are produced as
screen flashes.

>Other then this, it is a fun program, as for the poster's suggestions I have

Fun?  I think it's very useful.  I'm a touch typist, as are many other
people here.  I'm not always looking at the screen to see the "beep".

>only this to say - a with all small, fun, utility programs serious thought
>must be given to commparing usefulness to codesize. IMHO, a utility like
>this that takes more then ~10k is just too big to enjoy, as anything other

Well, I'm open to suggestions.  I haven't seen anything that takes less
room but does the same job.  (A simple beep is okay, in fact maybe
better than a digitized sample.  Right now I'm using the "boink" sound
from Amicus 10, but that gets old fast.)

>then a run-once oddity.

Run-once.  In my startup-sequence.

-- 
Eric Kennedy
ejkst@cisunx.UUCP