I have experienced a similar problem, but I
do not have to reboot to clear it, I only
have to quit and restart Squeak.

When I start Squeak, the first invocation of
playSound(??? doing this from memory) works.
After that all I get is a message saying
something about the device drive not being ready.

The message string that is displayed is not
present in the image i.e. full code scan = negative,
so I deduce the message is coming from outside.

Also the message is presented twice for each invocation
of the method.

Code analysis leads me to believe that the
problem is in the primitives - there are two.
One is called and if it fails the other is called.
That is why I get two messages, they both fail.

I am not using sound functionality right now, but
as  I use Morphic more it becomes annoying.

If anyone needs a detailed write up let me know
and I will recreate the problem and my analysis
and send it to you.

Please excuse my lack of correct reference, I
am at work and do not have an image handy, but
I thought the additional info may be of help.


John-Reed Maffeo


> -----Original Message-----
> From: squeak [mailto:squeak at vextquizz.netscapeonline.co.uk]
> Sent: Tuesday, January 22, 2002 12:34 AM
> To: squeak-dev
> Cc: squeak
> Subject: Squeak hogs sound driver on NT (repost)
> 
> 
> sometimes, running a sound app in Squeak (such as in "Fun with Music")
> seems to lock up the sound driver so that sounds cannot be used from
> elsewhere in windows, or even from Squeak itself. - logging out and on
> again is not enough; I have
> to reboot.
> 
> Is this a known problem with a known solution? e.g. restarting an NT
> service ?
> 
> (this is a repost - the first one seems to have got lost)
> 
> Greg.
> 
>