Sims 3 and Microsoft.VC80.CRT

[Enverex]

I had the Sims 3 working up until the town load section and was about to test something for Jeffz when something (I honestly don't know what) caused some breakage to do with the MS C++ libraries.

Now when I try and run the game I get:

Code: Select all

ben@xenith:~/Wine/Games/Sims3/Game/Bin$ wine TS3.exe
fixme:ntoskrnl:KeInitializeTimerEx stub: 0x110f80 0
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762)
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\windows\\system32\\MSVCP80.dll") not found
err:module:import_dll Library MSVCP80.dll (which is needed by L"C:\\Games\\Sims3\\Game\\Bin\\TS3.exe") not found
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\Games\\Sims3\\Game\\Bin\\TS3.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Games\\Sims3\\Game\\Bin\\TS3.exe" failed, status c0000135

Installing the vcrun2005, vcrun2005sp1, vcrun6 packages (via 'winetricks') had no effect. Any ideas what causes this and how to fix it?

"rm -rf ~/.wine" isn't an option as I have a lot installed and always wiping Wine for issues that can occur frequently isn't really a sensible option anyway.

[Alex]

I was looking for some infos on The Sims with wine and Google showed me your post.

A dll is a file that contains shared fonctions and programs (and so games) need some of them.
You may have noticed they have long version number.

So if a game need an exact version of a dll, it is specified in a manifest.

Here, The Sims needs 3 libraries v8.0.50727.762.

By googling a bit, I found this.

Copy them to system32/ should solve your problem.

[vitamin]

Copy them to system32/ should solve your problem.

Nope, they will refuse to load from there. DO NOT recommend something you do not understand.

[Alex]

Well, on this kind of situation, I always remove ~/.wine and then I install again my program.

When I was on windows and a program lacked some dlls, I googled their name and I downloaded them.
I added them on the directory where the binary was and all was ok.


Now, I have a GTK+ project for my school and we are using VS07.
I wanted to work on this at home so I packed all needed .lib and .dll and I created a dll/ directory inside my project folder.

When I launched Debug, VS didn't find the dll and so I looked for infos on how windows handles dll.

And I read (on msdn) that he looked at '.' then PATH then others dirs.
So I added PATH=$PATH:dll/ on the project properties and now all is ok.

--
But I guess wine behaves differently.

I thought about all guys coming from Google frustrated with no answer.

So if you have the correct answer, just give it.

[Cr0k]

When I add specifics .ddl to my ~/.wine directory, I put in in the system folder, and it solves my problems.. I'm not sure, but maybe? The Sims 3 works a bit on my system (Arch x86_64, wine 1.1.43)

[Alex]

Here is the link I read.

I think it may be considered as a bug if wine does not follow this.

[vitamin]

So I added PATH=$PATH:dll/ on the project properties and now all is ok.

This should also work in Wine. But you can not copy msvc runtime dlls into system32 directory - they will refuse to load from there.

It's a special "feature" MS put in place to get around dll-hell. They just created a slightly different sxs-hell. Where you can have multiple versions of the same dll, and applications would find their specific version. Of course this means that old dll with bugs can't easily be upgraded.

[DanKegel]

I had the Sims 3 working up until the town load section

It works pretty well for me, just had to do winetricks d3dx9

and was about to test something for Jeffz when something (I honestly don't know what) caused some breakage to do with the MS C++ libraries.
"rm -rf ~/.wine" isn't an option as I have a lot installed and always wiping Wine for issues that can occur frequently isn't really a sensible option anyway.

Sadly, we're not very good at repairing broken windows directories
(and neither is real windows).

The best I can suggest is to become comfortable with using
multiple wineprefixes; that way you can reinstall any app whose
wineprefix accidentally becomes corrupted.