PlanetZ forums - scopeusers.com

Hello,

Well, I finally got around to installing version 4. I made a clean install, so evrything from scratch and no prior versions of Pulsar were installed. Anyway to to test if things were up and running I loaded the Synths project. However, I got a couple of messages:

"Can't find dsp file hidamp lowpass-please check installation"
and another window came up saying:
"Find Merger Device" which I had to browse to.
Is This normal? Have I done something wrong with the installation? I followed the install instructions to the letter. So can someone please explain?
Also the installation instructions said I had to run the OXE files to install the plug ins I have bought over the years. However, I had access to what I needed without installing/running the Oxe files. Does that make any sense?
Finally, why should I install the latest ASPI drivers (which I did by the way, before installing Scope)? I have no intention of using Akai stuff.

Regards and thanks in advance for your response(s)

<font size=-1>[ This Message was edited by: Astral Fridge Magnet on 2004-05-30 12:15 ]</font>

For problems related to dsp files try:

start>run "cmd.exe" (without the quotes)
then "cd c:sfp" (or wherever you installed sfp4)
"attrib -s -h /s /d" (will reset any hidden/system files within the sfp folder & subfolders).

As for the ASPI layer update, I believe SFP uses ASPI to load AKAI cd's (and possibly just to browse cd file systems as well).

No idea about your midi merger issue....

Also did you install over yourold SFP directory or install to a new directory?

Try changing the file attributes of the DSP folder contents - remove any "read only" or "hidden" attributes.

Some optional devices require special DSP (and sometimes other) files, which the .oxe installer contains. So some of your plugins may be missing these, but that doesn't seem to be the problem you're describing.

WinXP uses the ASPI for more than SCSI.

/dave

<font size=-1>[ This Message was edited by: dbmac on 2004-05-30 12:35 ]</font>

Xp doesn't require aspi installs for scsi, I run scsi here

Hi again,

Valis, I didn't install over my old SFP directory. It was a clean install from scratch. I made a clean install of my setup and reinstalled everything fresh. So, should I have first installed version 3.1c? Is ASPI an essential install?

valis's first post should fix the problem...

Hi Valis,

Thanks very much and your help is very much appreciated. Your instructions worked. For the time being I don't have missing file errors anymore and everything seems fine now.
Though if it's not too big a question, why did it work? Why did the problem occur in the first place?

Regards

Honestly I'm not sure. I've had this problem since 2.04a (beta for win2k) but I've always run dual cpu machines (I do graphics stuff as well).

Back then noone else experienced this problem so I assumed it was creamware's install app doing stuff out of order on my dual cpu machine. I used to see a lot of this from apps that weren't properly threaded. For instance any Creative labs driver would skip on my dual cpu machines for ANY audio operation (winamp or media player playing mp3's etc) up until Win2k was out completely and it was announced that Xp was replacing the 98/me legacy (ie, Creative finally HAD to address the problem). In Creamware's case I had a lot of other problems related to my dual-cpu machine back then as well, and they did notice our complaints with the 3.0 release and fixed it in 3.1 (or 3.1a). I suspect they had to buy a machine to replicate the problem themselves.

In any case the only thing I can think of is Hyperthreading acting as 2 virtual cpu's and again messing with the order of execution of the install app. Otherwise ????? It affects different dsp files every time so it seems rather random.

I had this problem at startup after a brand new install:

"Can't find DSP file Midi Channel filter - please check installation"

after exiting Scope I run cmd.exe, and typed:
C:Program Filesscope4>attrib -s -h -r /s /d *.*

and it fixed the problem!