Ghadzoeux

Join Date 02/2008

SoaSE and Entrenchment location on HD

or why some doesn't work

I experienced the crashing issues with both games after the new updates (1.13 and beta 2) and I also had the uninstall error (XML 28,8).

I decided to manually delete all folders, reinstall Impulse and so on.

Then I launched Entrenchment installation from Impulse, then it would ask to install SoaSE before so I did.

Now I only have one icon (Entrenchment) in Impulse and when I launch it I have a error requesting fmod.dll so I investigated further. And look what I found :

Original SoaSE is located here :

C:\Program Files\Stardock Games\Sins of a Solar Empire

(of course, if I run the exe from I have the vanilla game working perfectly)

and Entrenchment is here :

C:\Program Files\Stardock\TotalGaming\Sins of a Solar Empire\Stardock Games\Sins of a Solar Empire

But I remember that before the destroying patches, Ent. was located inside SoaSE folders and that's why he's now requesting dll files that are not in the expected folder.

So why Impulse did this mess? And how can I get all games running?

technical

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

kryo

Join Date 05/2003

+458

A number of people have reported these installation issues, and they are being looked into. Entrenchment should install on top of Sins in the same location.

Successfully updated karma reason!

So if I move the ent. files the same they used to be in SoaSE folder, Ent. should work?

Successfully updated karma reason!

This is interesting!! I had copied the 1.12 files over to my second hd before updating, but found after the update that both the new Entrenchment Beta 2 and the 1.12 on the other drive both launched Entrenchment. I couldnt figure out why, but if you are correct then both launchers load Sins and then Entrenchment (i'm guessing) no matter where they are launched from, and it is the exe files that launch each version.

I have to re-load the beta, but if you are correct then i should be able to launch 1.12 from d: using the exe file, not the launcher, and of course using the launcher, get to Entrenchment!! Thank you for helping me figure this out!!!

-Teal

p.s. I'll let you know what happens.

Successfully updated karma reason!

Found a solution that actually works for me :

I uninstalled Entrenchment

I copied the entire vanilla folder from :

C:\Program Files\Stardock Games\Sins of a Solar Empire (where it was installed)

to:

C:\Program Files\Stardock\TotalGaming\Sins of a Solar Empire

(two folders above the location of entrenchment)

I re-installed Entrenchment and now when I launch it, it works and it no longer creates sub-folders like these I had :

C:\Program Files\Stardock\TotalGaming\Sins of a Solar Empire\Stardock Games\Sins of a Solar Empire

If it can help others.

Successfully updated karma reason!

I find this whole thread interesting. "Official" add-ons made by Stardock / Iron / etc. are housed in the directory in which it was installed in. However, all mods are placed into the User's Account personal file. It would have made more sense (as far as keeping with the previous way that "mods" were added to the game) to have Entrenchment installed into the User's Account file.

Personally, I prefer installing Entrenchment to the main install folder. I don't use my C: drive for anything but Windows and other primary programs (Adobe, Office, etc) and I install and keep all my games on a separate drive. Thus my C: drive fills fairly quickly on it's own WITHOUT the help of having to install mods onto my C: drive.

Think of it like BF2; a mod directory within the installation directory houses ALL mods and allows for any user to use the mods. Plus, (I haven't tried this yet) doesn't this method of installing mods to a certain User Account limit who is able to play the mod and thus must be installed in several different User's Account to play?

Sorry for the slight hijack in the thread and where it was headed but I think this post stays true to the title.

Successfully updated karma reason!