14 réponses à ce sujet

[Sunjammer]

Since some users encountered problems with installing/using the toolset with Windows 8 and Windows 8.1, I thought it might be useful to start a thread to collate information about how the toolset gets own with Microsoft's latest offering.

 

Have you installed Windows 10? Was it a clean install or an upgrade (and if so from which version)? Did you install the Dragon Age Toolset or was it already installed? Does the toolset run, how does it perform, any issues, etc?

 

For my part I've just installed Windows 10 on my laptop. My laptop was Windows 8 and I had installed the toolset when I got it with just a couple of minor issues (discussed/linked in the Windows 8.1 thread) and I'd been using it for months without a problem (other than my general dislike of the Windows 8 UI). I hadn't been able to update to Windows 8.1 because Microsoft took exception to the fact I'd moved my Users folder to my D:\ drive!

 

When Microsoft announced Windows 10 free upgrade (or Start Menu Emancipation Project), I bit the bullet and restore the laptop to factory settings, updated all the way to Windows 8.1 and reinstalled the toolset. In doing so I did get a couple of compatibily warning with regards to SQL Server 2005 Express but I was given the option to continue on regardless. The install was completed and the toolset started without incident. Admittedly I haven't done much more than start the toolset and open a couple of resources so I suspect I would still have to resolve the same issues I'd encountered under Windows 8 with regards backing up/restoring the database, etc.

 

This evening I updated to Windows 10 Home (I had to do it manually as Windows Update kept failing) and everything has appears to have gone smoothly. I booted up the toolset and, after an agonising few seconds, it opened without incident. Again in the interests of full disclosure I only started it and opened a couple of resources (no, of course one of them wasn't a script, honest!). If I encounter any issues when I have a reason to start creating additional databases or using backup/restore database I'll post an update.

 

TL;DR: Toolset installed under Windows 8.1 appears to work under Windows 10!

[berelinde]

Thanks for posting this. I was planning on biting the bullet and upgrading this weekend.

[Truckee_Earl]

My experience:  

 

I went from Windows 7 to Windows 10 with a dual-boot (easily doubled the time necessary to install Windows 10).  No benefit to dual boot, I went back and forth for the first day and haven't been back in Win 7 since.

 

I was and am running the toolset in MS SQL Server 2012, no problems.  I had  gone to Server 2012 back in 2014 because of the file size limitation in Server 2005.  The management tools in 2012, (in particular the backup and restore process) are another really good reason to upgrade to a newer version of SQL Server.

 

Hope everyone else has a good experience also!

[alexanderfc]

This has made me feel slightly better, I'm a little nervous about upgrading!

[Sunjammer]

I've now also updated my Windows 7 PC to Windows 10 Pro. The only hiccup (can't even call it an issue) I encountered is that Windows didn't start the SQL Server (BWDATOOLSET) service so I got the old the "Unable to connect to database" error when I tried to start the toolset for the first time. If anyone isn't sure how to fix that issue refer to this section in the wiki.

[Truckee_Earl]

Just checking back in, still no problems to report with Win 10, all my tools working as expected, getting close to a new release of my mod.

 

Sunjammer (once again) has the best advice, but I've been a fan for a few years.!

[olnorton]

What's actually involved in updating SQL Server 2005?
I'm on Win 10 & got the warning, but the toolset seems to be working fine.
I click on the update link & it said first read this 400+ page pdf.

[Cobra's_back]

What's actually involved in updating SQL Server 2005?
I'm on Win 10 & got the warning, but the toolset seems to be working fine.
I click on the update link & it said first read this 400+ page pdf.

I like to know this one as well. I played DAO a long time ago on another computer. I wanted to play it on my window 10 computer but was a little afraid to do it.

[Sunjammer]

I suspect it depends on which version you want to update to.

 

I recall that people have had it working with 2008 so I did a bit of digging and there is some references (e.g. http://forum.bioware...8-standard-x64/) to it working with both 2008 Express and 2008 R2. The secret appears to be to restore it from backup (which BioWare very decently provided for us) which sets the 2005 compatibility (Type 90) mode. I found this walk-through (https://jerbecca.wor...l-express-2008/) someone has created (which I'll need to port over wiki for safekeeping).
 
Not sure if anyone has tried any of the newer versions of SQL Server but all of the versions since 2008 have had this compatibility level (https://msdn.microso...y/bb510680.aspx) so the same approach might work on 2012 or 2014.

[olnorton]

Thanks Sunjammer, I've had no problems running the toolset in Win 10 with SQL Server 2005, but if I do, or if I get really bored, I might uninstall the toolset & try the update.

[Truckee_Earl]

On my PC The latest release (1511?) of Win 10 is causing problems with the Toolset, but the database (SQL Server 2014) seems fine.  The problems with the toolset involve the visibility of placeables in an area.  So I have switched back to Win 7 (dual boot) and am continuing on

[Kardias]

I suspect it depends on which version you want to update to.

 

I recall that people have had it working with 2008 so I did a bit of digging and there is some references (e.g. http://forum.bioware...8-standard-x64/) to it working with both 2008 Express and 2008 R2. The secret appears to be to restore it from backup (which BioWare very decently provided for us) which sets the 2005 compatibility (Type 90) mode. I found this walk-through (https://jerbecca.wor...l-express-2008/) someone has created (which I'll need to port over wiki for safekeeping).
 
Not sure if anyone has tried any of the newer versions of SQL Server but all of the versions since 2008 have had this compatibility level (https://msdn.microso...y/bb510680.aspx) so the same approach might work on 2012 or 2014.

Just wanted to confirm that this method will work on 2014. Just make sure you set permissions on SQLEXPRESS to local machine, or you will get an access denied error. Also, you can do this through the gui as well if you don't like command lines. It is pretty straight forward. You just have to add new database by right clicking the database hierarchy, and go ahead and name it bw_dragonage_content. Then just use the restore database option when you right click again and point it to the backup copy of the bw_dragonage_content.bak file on your machine, make sure and check overwrite in options and set SQLEXPRESS permission with sql configuration manager. You create the databases with sql express management. I was able to get it working through the gui just fine. 

[rizzdog]

Hi Everyone --

 

I've encountered the dreaded "Unable to connect to database" error when opening up the toolset. The toolset was working on Windows 8 and the problem seems to be when I upgraded to Windows 10. The toolset installs although I get a warning message during installation that MSQL 2005 is not compatible with Windows 10. 

 

I have consulted the troubleshooting guide -- the database server is running, SQL appears to install (although the path and folder names are slightly different than the troubleshoot guide) and the database has restored. At this point, I am trying to use the ConfigureTool to determine if the toolset is pointing to the correct database but I am uncertain how to proceed. In particular, I am uncertain where I am supposed to copy the correct string from the ConfigureTool and when to run the command line (basically steps 1 & 2 from the troubleshoot guide). 

 

Any clarification on how to confirm that the toolset is pointing to the database or any other suggestions would be most appreciated. 

[rizzdog]

What????? I reinstalled the toolset for the nth time yesterday and today, I was able to open it without configuring or changing anything. Crazy. 

[Thandal N'Lyman]

Haven't had any problems installing/using the Toolset since the initial install under Vista (now running WIn10/Build 1511.)

 

Well, except for needing the LAA hak to load my large .das files.