Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uwm.edu!bionet!agate!stanford.edu!leland.Stanford.EDU!jessica.stanford.edu!aaron
From: aaron@jessica.stanford.edu (Aaron Wallace)
Newsgroups: comp.windows.ms
Subject: Re: FMSOUND 1.0
Message-ID: <1991Apr19.195522.14684@leland.Stanford.EDU>
Date: 19 Apr 91 19:55:22 GMT
References: <1991Apr12.165636.9586@isc.rit.edu> <50888802@bfmny0.BFM.COM> <1059@venice.SEDD.TRW.COM>
Sender: Aaron Wallace
Organization: Academic Information Resources
Lines: 14

In article <1059@venice.SEDD.TRW.COM> press@venice.sedd.trw.com (Barry Press) writes:
[Stuff about the system clock freezing...]

>I've had a lot of programs do this, not the least of which is sounder.  I
>also notice that one of my computers is more susceptible to the problem than
>the other.  I dont' know the real cause, but I suspect it's some interaction
>between device drivers and Windows.  For that matter, I think I saw it once
>with nothing "non-standard" having happened.

Sounder does it on purpose.  A forthcoming bug fix *may* help fix this problem
by bumping the BIOS time after the sound is played...   It's nothing to do with
device driver interaction, at least in Sounder's case.

Aaron Wallace