Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!aero-c!gumby.dsd.trw.com!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms
Subject: Re: FMSOUND 1.0
Message-ID: <1063@venice.SEDD.TRW.COM>
Date: 23 Apr 91 16:14:24 GMT
References: <1991Apr12.165636.9586@isc.rit.edu> <50888802@bfmny0.BFM.COM> <1059@venice.SEDD.TRW.COM> <1991Apr19.195522.14684@leland.Stanford.EDU>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 21

In article <1991Apr19.195522.14684@leland.Stanford.EDU> aaron@jessica.stanford.edu (Aaron Wallace) writes:
>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

>Sounder does it on purpose.  A forthcoming bug fix *may* help fix this problem
>Aaron Wallace

Uh, nope.  I meant to observe that a number of programs, including vanilla
Windows, sounder, and others, seem to cause the system clock to advance --
after these programs have exited -- at many times the normal rate.

This does not seem to affect the CMOS clock, just the rate at which DOS
advances time.

I understand that the fm guys have tracked down their problem with this, 
and that a version 1.01 will apparently be released.

-- 
Barry Press                                 Internet: press@venice.sedd.trw.com