Path: utzoo!attcan!uunet!pyrdc!netsys!ames!ncar!cruff
From: cruff@ncar.ucar.edu (Craig Ruff)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Bug in SysBeep?
Message-ID: <665@ncar.ucar.edu>
Date: 5 Sep 88 14:22:54 GMT
References: <664@ncar.ucar.edu> <13898@agate.BERKELEY.EDU>
Reply-To: cruff@handies.UCAR.EDU (Craig Ruff)
Organization: Scientific Computing Division/NCAR, Boulder CO
Lines: 14

In article <13898@agate.BERKELEY.EDU> lippin@math.berkeley.edu writes:
>Recently cruff@ncar.UCAR.EDU (Craig Ruff) wrote:
>>I think I have found a bug in SysBeep.  Setup:
>
>Is thePort the window manager port?

Thanks for the info.  I hadn't thought about which port was being used.
The software that is mucking with the window manager's port is the
Aztec C console driver, which doesn't get a new window before doing
so.  I can fix it so it does something reasonable now.
-- 
Craig Ruff      NCAR                         INTERNET: cruff@ncar.UCAR.EDU
(303) 497-1211  P.O. Box 3000                   CSNET: cruff@ncar.CSNET
		Boulder, CO  80307               UUCP: cruff@ncar.UUCP