A stupid cache-overflow rookie mistake, help needed

  • Thread starter Thread starter Nylonbeast
  • Start date Start date
N

Nylonbeast

New member
First of all, Hi everybody, I'm new

I'll go straight to my problem: Earlier (way earlier today/last night) I was trying to make my Access Virus plug-in work on Cubase 5.12, and was messing around with the VSTplugin-path operation... for some reason I couldn't make Cubase found the correct files from the correct path, and then it happened - I got frustrated and decided to write bluntly "C:" as the path where that plug in can be found...
Sure Cubase did find the said .dll-file, along with the kazilliontrillion other non-related .dll files (system32 is full of them), which lead to a scenario in which Cubase is trying to call every single file on my computer a VST-plugin.

Naturally, I had to eventually uninstall the whole program and run registry cleaners and such, otherwise the program would just "remember" my burst of genius and try to read every .dll file on my computer upon launching the app...

Now here is the problem. Total uninstall along with reg clean etc won't help. The fresh install will still overflow to wondering how a photoshop brush is supposed to sound like... Here are the things I've tried:
- removed the personal VST-setting information files after uninstall from documents and settings/username/whatever...
- managed to launch cubase only by removing the whole medialibrary-file, which in turn barred me from redefining the path choice (as I found out that the choose-path box was grayed out in the app)...

So has anybody stumbled into a similiar situation?
Does anybody know where that stupid path choice is registered, and when found, can the path be redefined manually through notepad etc...?
And if indeed I somehow need to completely uninstall Cubase from my PC, what files am I missing that are screwing things up on the new install?

Thanks in advance!
 
Try opening regedit and look for this HKEY_LOCAL_MACHINE\SOFTWARE\VST\VSTPluginsPath

If that fails do a search in regedit for VSTPluginPath
 
Tetrafish: Thank you so much! That did the trick. Perfect!
 
Back
Top