Greetings all,
I screwed up by selecting the wrong folder for a module path and I can no longer launch awe_designer to fix it. The bad path appears to be well hidden in a cache somewhere as deleting assorted .ini files, grepping for the bad path etc. completely deleting the folders wherein awe_designer_pro is installed etc. have been fruitless. Somehow this error is persistent. The error looks like:
>> awe_init
Error using add_module_path
The directory C:\SVN\<a bunch of irrelevant path stuff>\awe\matlab does not exist
Error in load_persisted_settings
Error in awe_globals
Error in awe_init
Can anyone suggest where I should look to remove the offending errant path? By the way, and somewhat ironically I suppose, the path that causes the error does, in fact, exist...
Steve.
4:21pm
Some additional interesting information. The awe_designer_pro installation is within an SVN branch which allows me to easily delete the whole branch, which includes both the awe_designer_pro installation and the folders etc. on the module path for which designer objects so strenuously as not existing (even though it does) that it won't start. If I recheckout the branch into the same directory in which it formerly resided, the error recurs.
If, however, I recheckout the branch into a new location (so it does not reside on the same path as it formerly did) the problem does *not* recur and designer loads normally.
While allowing me to proceed with short term testing, this work around does not resolve the longer term issue of there being bad path data cached somewhere that needs to be managed. Any help in locating it would be greatly appreciated!
Thanks, Steve.
5:18pm
The cache is somewhere in: C:\Users\<user name>\AppData\Roaming\AudioWeaver directory. Deleting this directory and rebooting fixed it. I didn't try just rebooting so maybe that would have worked. Also note that a number of other AWE related files were deleted along the way which may also have been required but were not, on their own, sufficient.
7:43pm
Hey Steve,
Sorry for not getting back to you sooner. The persisted settings file is in C:\Users\<user>\AppData\Roaming\AudioWeaver\PersistedSettings_v2.mat. Deleting just this file would have reset your module path and you could have continued.
As for the reason for the error, it reminds of a bug we found previously where a non-standard character (in this case a single-quote) in the path of recently opened files was causing similar but less fatal problems with Designer. Does your path have any non-standard characters in it that could be choking up Designer? The bug I'm referring to should be fixed in the 6.17.05 edition, but you may have found an additional vulnerability.
Thanks
-Axel
9:42am
Hi Axel,
Thanks for the reply and the new information. There were no special characters in the path and the path existed (even though I didn't click on the desired folder, I did click on a real one...) so the failure seems quite odd...
Steve.