Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: HELP: INSTALLBEEP+BASIC
Message-ID: <2233@lpami.wimsey.bc.ca>
Date: 16 Nov 90 20:05:54 GMT
Lines: 28
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <36573@nigel.ee.udel.edu>, new@ee.udel.edu (Darren New) writes:
>In article <36506@nigel.ee.udel.edu> NJ_GOKEM%FANDM.BITNET@pucc.princeton.edu writes:
>>What can I do to get rid of this stupid CRASH!!!
>>(Is it possible to deactivat installbeep, or give it a low-low priority orso?)
>
>I've found that multiple beeps at once or a beep while some other program
>is beeping can wedge my machine when I'm running InstallBeep. My only 
>solution was to remove InstallBeep.  The problem occurs when BASIC and
>something else both beep at the same time, yes?          -- Darren

I ran across this ages ago when I wrote 'setbeep'. My error was in opening the
device in the main program, and then using it in the SetFunction()ed routine,
assuming that only one beep would happen at a time. Unfortunately, the call to
DisplayBeep that I intercepted can be called from anywhere, causing the program
to try to use the device twice, resulting in a GURU.

AmigaBasic, I found out, calls DisplayBeep twice in rapid succession, showing
the proble consistently.

-larry

--
The only things to survive a nuclear war will be cockroaches and IBM PCs.
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+