If your data directory was set to a share that no longer exists, just set it to where your data currently resides. You can do that through the launcher.Unfortunately, I seem to have struck a problem with the software, which was running perfectly well earlier this week. I think the problem is that I had my data directory set to a local SMB share; earlier this week I moved that share to a new address and now... well, now I can't get any of the four programs to launch (launcher, CharGen, GM Tools, Data Editor). I use the Manual Install, so I deleted the program directory and re-installed (I'm running 1.6.0). No dice. I hunted down the cache and other config files in Users\<my username>\AppData and deleted them, hoping that doing so would force the program to re-create them from scratch, again, no joy. I've included the error message I get from trying to launch the Launcher program below, and the system is Windows 7.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: SWCharGenLauncher.exe
Problem Signature 02: 1.6.0.0
Problem Signature 03: 5673604f
Problem Signature 04: mscorlib
Problem Signature 05: 4.6.100.0
Problem Signature 06: 55bc05fc
Problem Signature 07: 157e
Problem Signature 08: 219
Problem Signature 09: System.IO.IOException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Question, what do I need to delete from my computer to completely remove the software, so that can do a true clean install? The program files, obviously, and anything under AppData - are there any other rogue configuration files I need to delete that might still have a hint of the old SMB share address? Any registry entries?
Sorry, can't cut down quotes easily on my phone... Anyway, unfortunately, I can't load the Launcher at all - the error message in the spoiler above is from trying to start the Launcher, although launching the individual programs gives a similar error message.
I latched on to the change of folder share because it's the obvious change I've made since I last used the program, but if the Launcher isn't looking and crashing when it can't find it (which is my working hypothesis), I need to start thinking further afield.
Edited by NGnear