Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jb10320
From: jb10320@uxa.cso.uiuc.edu (Jawaid Bazyar)
Newsgroups: comp.sys.apple
Subject: Re: Kermit docs in PS format
Message-ID: <1989Oct26.162341.23388@ux1.cso.uiuc.edu>
Date: 26 Oct 89 16:23:41 GMT
References: <8910251607.aa25548@SMOKE.BRL.MIL>
Sender: paul@ux1.cso.uiuc.edu (Paul Pomes)
Reply-To: jb10320@uxa.cso.uiuc.edu (Jawaid Bazyar)
Organization: University of Illinois at Urbana-Champaign
Lines: 16


   I've been using SysBeep() in a program of mine, and bad things happen.
Namely, something (i.e. SysBeep, or BELL) is killing interrupts for the entire
duration of the beep (about 1/2 second or so).  It's rather annoying- it's no
big deal to write my own beep routine (or steal the one from the APW manual!)
but IMHO SysBeep doesn't need to lock out interrupts.  Does anyone from Apple
have a rationalization for this?

--
===============================================================================
jawaid bazyar    jb10320@uxa.cso.uiuc.edu  Junior/Computer Engineering UIUC

Seepage from deep,black,brittle experiments which failed and transformations too
hard to find. "I was overcome and turned to Red." Duster's dust became the sale.
Lucifer the light. A restless motion came to move and then subside. In endless
knocking at the door- it's time. TYRANNY & MVTATION. TYRANNY & MVTATION.