2 réponses à ce sujet

[kskh2o]

Hello,

I installed the toolset on XP SP2, and had the whole BSOD, enless restrat etc happen.  Anyhow, I booted in safe mode, and uninstalled SQL from programs in control panels (I have windows installer ennabled in safe mode).

However,

Uninstalling SQL from bottom to top as stated in the wiki, does not actually remove SQL from system entirely.  I had to go into services and disbale the three associated services in order to stop getting an error at start.  Now I cannot find a way to remove those service entries from the services tab.

Anyway SQL is 'mostly uninstalled' but now there is no way to uninstall the toolset. Since the toolset installation never completes on this botched XP SP2 install, there never was an uninstall file created nor does the toolset appear in Programs and settings for you to remove it.

Now at this point I've upgraded to SP3, and before I go ahead and even try to install the new Toolset, I was wondering how I can remove (uninstall) the botched installation on my system (toolset 1.00) remove the broken SQL services which did not uninstall with the removal of SQL from programs and settings, and basically get back to before hacing even tried to install the toolset.

Thanks for any help

[BryanDerksen]

As far as the SQL server stuff, we're not really sure how to clean up the mess - it's not our program. You may be able to Google up some Microsoft documentation on the matter. For the toolset all of the registry keys are in HKEY_CURRENT_USER/Software/Bioware/Dragon Age/Toolset, and the same path under HKEY_LOCAL_MACHINE. You can just delete both of those "Toolset" registry folders. And of course delete the tools subdirectory under the Dragon Age game folder, if that's still there.



However, I suspect you won't actually need to do any cleanup at this point. We've had no problems when doing test installs overtop of existing installations without removing them first. If you want to be as tidy as possible without delving into the intricacies of Microsoft's Knowledge Base, perhaps you could try installing 1.00 overtop of the old installation and then immediately uninstalling it again?

[BryanDerksen]

We've had a fair number of positive reports from people who have tried installing MSSQL 2008 instead of 2005, you might want to check up on that as an alternative. Assuming 2005 does cause you additional grief with that .net thing.

Modifié par BryanDerksen, 12 décembre 2009 - 12:22 .