To do this, go to start, then run and type in "msconfig" and click the Startup tab, everything listed with a green check mark is running in the background and starts automatically when you power up the system.

Check for anything that might be ReWire associated, such as a ReWire tool from Propellerhead. It could also be anything in startup that is related to Audio or MIDI, anything that is already in communication with the output device could cause thing type of error.

Thats all good thinkning, but I've been using SAM 11 for a few months now and it only started happening this weekend.
Nothing has been added or taken away since May, when I did a fresh install of Windows. Maybe a reinstall of Sam 11 is on order ?

Sorry to hear about your problems.  After reading this, I was thinking along the same lines as John, but I'm not an expert.

Did this problem and the soundpool problem manifest themselves at the same time after working perfectly for several months?

If so, there may be a corrupted file in Samplitude.  A reload of Samplitude may be in order.  However, be aware you may have a limited number of reloads before your license becomes invalid.

I've heard MAGIX allows only three reloads.  I don't know if this applies to all MAGIX products, but it's something to keep in mind.

Unstable software and limited reloads.  It sounds like a win-win for MAGIX.

Hi Procyon

yes tehy did happen all   of a sudden
I have done the check up program with Magix support and am waiting for guidance
The pool worked again amazingly, but not long after I built a quickie the error came around again. I agree the audio should all be on my audio drive, but I dont remember havibg a choice in locations for teh soundpools

Anyway thanks for teh help
good stuff