PlanetZ forums - scopeusers.com

I have used Creamware stuff for some time now and although I have seen many smaller installation problems come and go, I have not seen this before.

Sometimes when I am loading devices (Prism, SB404, Mod2 patches etc.) SFP hangs. SFP continues to be able to respond to midi and external audio and produce sound, but it sucks up all more or less all CPU and is not responding to mouse or keyboard. It cannot be stopped by other means than ending it roughly from the Task Manager.

This does not happen often - but in line with our friend Murphy's observations it really likes to show its ugly face on those occasions where I haven't saved my work for some time...

This problem did surface when I moved to new hardware. My Creamware stuff (Pulsar 2 + PowerPulsar) is now sitting in a P4 2.4, P4PE motherboard (with the SoundMax, SATA & Ethernet options) , 768MB. The PC is running Win XP SP1. The problem has occurred without any other software loaded.

I have reinstalled my 3.1c from the full packages at CW. However, I have not reinstalled my machine from scratch, although I am thinking of doing that soon in case there are no other suggestions.

thanks for listening.

I've done several reinstalls and it still happens.

Modular shells (especially ModIII) are the most prone to making this occur, so always save before loading Modular.

With regular devices there are 2 things I've seen.

First off if you often leave your machine idle for long periods of time go into your control panel, "Power Options" and disable System Standby (I also disable turn off harddisks myself).

Now go into the "Sounds and Audio Devices" control panel and go to the 'Hardware' tab, double click on (one of) you board(s) and you'll get the properties window. Go to the 'Settings' tab and under 'Powermanagement' at the bottom uncheck 'reset board if idle'.

For my last few installs this worked. For my new install its not working properly for some weird reason, so now I'm simply in the habit of closing & restarting SFP.exe if my machine has been idle for more than an hour or so.

Thanks for the reply, it sounds like a possible cause to me. I will definitely try it out.