"Can't find DSP file . . . check installation" Wha
-
- Posts: 9
- Joined: Thu Dec 14, 2006 10:19 pm
"Can't find DSP file . . . check installation" Wha
Hello,
I recently reinstalled Window Xp and Scope 4.5 and I keep getting different "Can't find DSP files" messages, like "Can't find DSP file effects package 2 check installation" and others of the same nature. I have the key for efffect 2 and all of the other modules scope says it can't find. I have never had this problem with the prevoius installs. Does any one have an idea of what to do, or what the problem is?
Thanks
Matt
I recently reinstalled Window Xp and Scope 4.5 and I keep getting different "Can't find DSP files" messages, like "Can't find DSP file effects package 2 check installation" and others of the same nature. I have the key for efffect 2 and all of the other modules scope says it can't find. I have never had this problem with the prevoius installs. Does any one have an idea of what to do, or what the problem is?
Thanks
Matt
it happens sometimes with the downloaded version of the installer. it is from those dsp files being wrongly marked "read only". a search will find threads about it. i usually install the downloaded version from the desktop and never see that problem.
you can unistall and try to reinstall from the desktop or factory cd, or you can delete the dsp file and copy the files from the install disk, or you can select the files, choose properties and uncheck the checkbox. if you do the search, there's also a short script you can try.
you can unistall and try to reinstall from the desktop or factory cd, or you can delete the dsp file and copy the files from the install disk, or you can select the files, choose properties and uncheck the checkbox. if you do the search, there's also a short script you can try.
I had such thing yesterday, too. I already tried (a year or so before, when this happened for the first time) to re-attrib the files, since I noticed that they were read-only. I have this problem now with third-party plugins, which are not included in the scope 4.5 distribution, only as nokeys.oxe (and maybe later as personalized oxe when mypage is back upgaryb wrote: you can unistall and try to reinstall from the desktop or factory cd, or you can delete the dsp file and copy the files from the install disk, or you can select the files, choose properties and uncheck the checkbox. if you do the search, there's also a short script you can try.

the attributes are correct, btw, that's what made me think. there is just that popup, the device itself loads. is there a way to verify whether the device works as intended and the popup is just erraneous, or if parts of it are maybe not working?
yes, I will contact the developer, but maybe you have an idea...
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.
garyb,garyb wrote:a good install never does this.
i'd just replace the files.
i would unzip them again onto the desktop and work from there.
maybe I didn't make that clear enough...
I just have the nokeys.oxe files, and no source to unzip from (unless you can tell me a way how to uncloak an oxe file). since this mentioned oxe is 3rd party, the dsp (and other) files are not part of the scope 4.5 install package. the only way for "refreshing" the install is running the oxes again. the dsp files are already in place, they are named correctly (the name that is reported to be missing), and they have only an archive flag (like any other dsp file in the folder

maybe you have still a hint for me...
tgstgs,
I run win2k (with the latest servicepack applied long ago, when there was still official support for it

-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.
don't have to do that anymore. well, I restarted scope several times, but it kept on demanding for the dsp files. the next day (I had the machine switched off) everything was fine (and is still).garyb wrote:you may neeed to contact the developer.
in the mean time, try removing the offending files and rerun the oxe.
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.
in that context I consider them identical - I was just lazy typing...kylie wrote:...if ever, then it's been there with 2000 already, because I don't run XP
I somehow suspect the av scanner (maybe I had on-demand scan enabled this time...)

but while the AV assumption is true, it cannot be the (only) source, because I don't run that kind of software, but had the very same 'missing bla bla' when I had Scope on Win2K.
Currently it's on Win98 (still) and I have seen this message not a single time, as I never got the infamous midi buffer overflows (well, maybe I got them, but they didn't crash the box).
anyway, for some software's compatibility sake I'll do a Win2k install soon - the last one recently was an entire failure as the HD died right after the install...

cheers, Tom
Usually (in my experience) when the files are flagged 'read only' they're also flagged 'system', which is not an attribute you can alter without using command line tools (or 3rd party tools I guess). It does seem to be an issue with the installer, which (like scope) predates WIn2k/XP and occasionally exhibits this 'bug'.
2k and xp are different, though similar creatures. i think xp is definitely preferable...
xp does have a couple of bugs regarding the installer and midi buffers compared to 98, but xp sure does set up into a stable machine way faster and easier. fiddling and tricks are not so needed to get good performance.
xp does have a couple of bugs regarding the installer and midi buffers compared to 98, but xp sure does set up into a stable machine way faster and easier. fiddling and tricks are not so needed to get good performance.
it was probably a little bit of all that. maybe 2000 does something different during the install. I don' t mind if this is history after a reboot. it just annoys me that the result is different every time. some plugs install without any glitches, some don't.astroman wrote: but while the AV assumption is true, it cannot be the (only) source, because I don't run that kind of software, but had the very same 'missing bla bla' when I had Scope on Win2K.
do I have to take av into consideration, or not...?!
but in general it's quite stable. I don't see a special reason to get X(tra) P(roblems), apart from getting it upgraded every now and then. if I have to do a re-install (after more than 4 years), I might consider it, though, because of that reason.
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.