Resource error. Please help! (images fixed)

I had to reinstall all my content today because after the reinstall of dazStudio, mentioned here but half my content went AWOL so I thought I would reinstall my content. Once I uninstalled it I renamed the my daz 3d library because I wanted to make sure everthing is clean, removed the renderosity stuff I bought, and reinstalled everything. However, I got this message and no content error.
This is my configuration
What am I doing wrong? Do I have to do a total fresh install or something? Or is it something so simple that I over looked it?
Edit. I found the issue, I didn't reinstall all the plugins. Once I checked the DIM settings and included plugins Daz returned to normal


Direectories.png
371 x 198 - 7K


resourse error.png
504 x 121 - 7K
Post edited by Xade on
Comments
Note that you might not be entirely out of the woods yet. The content location settings and content database files are not stored along with the program or content folders, and are preserved through an uninstall/reinstall. Did you delete those manually as well before beginning to remove your previous installation?
Another possible gotcha is that Smart Content/Categories/Products content views, which use the content database, will use that instead of actual content file locations when you browse through your content collection. If you've changed your content location, but D|S is still picking up the old content database, you might get some unexpected "can't find file" errors.