The forum

I guess it depends on Sims 4.  I know Origin uses QT but does Sims 4 use QT

If not, then the patch won't fix anything.  The patch was originally use to fix Origin so it would download games properly.

I doubt sims uses QT. EA has their own engine for it, I would imagine (probably starting after they bought Maxis.). 

I am going to try deleting and reinstalling the vd using wine 1.7.34 instead of 1.7.33. As we all know sometimes deleting and starting over from square one is sometimes neccisary to get things working. - That dosn't look spelled right. Unfortunatly spell check dosn't seem to be working and I just got up today,- Mouno update manager just popped up so I will check that first.

Yeah. I do that too. Fresh virtual drives are always the best when testing. 

Its a bit discuraging when you have delete so manytimes but then that's the way with wine.I guess thats the way with compatiblity layers like wine.

When I'm testing I will will follow these steps:

1. new 32-bit virtual drive
2. Wine 1.6.2 (stable)
3. Wine Configuration:  windows xp
4. Wine Configuration:  virtual desktop:  1024x768
5. packages:  corefonts, d3dx9, tahoma
6. install game
7. PlayOnLinux Configure:  Graphics Tab - set Memory
8. Launch game with Debug

If it crashes, has artifacts or doesn't run at all... I will check WineHQ's for tips or search online.  Normally a game will require more libraries like vcrun, dotnet, gdiplus, msxml3, physx, etc

I will also try othe versions of Wine to see if the problem has been fixed.  Sometimes the game folder will have a redist directory with libraries or a support folder with libraries.  Then you will know which libraries the game requires.

Steam games have a vdf script that tells you which libraries will be installed at first launch.

After all of this, if the game still doesn't launch or work, I will try installing in a new virtual drive again.

That is last resort unless a library  or change breaks the game.

Here is what I have done so far: 1. Deleted TheSims4 VD. 2. Told POL to make a new VD with the following op[tions: a. 32 bit. b. wine 1.7.34. c configure wine - I set wine to win 7 -.3. Installed Origin. After loging in I quit Origin. POL failed to detect that I had finished installing Origin so I clicked cancle and used POL's config tool to make the Origin shorcut. 4. I copied the QT5 patch to my new Origin folder. 5. I opened a console with the POL config tool.  6. CDed into Origin Directory. 6. Ran the patch succesfuly. 7. launched Origin and told it to download The Sims 4. I am waiting for about %70 more and then I will see if it installes. I supect the installer will install DirectX since modern installers seem to install what they need. At least Steam for Linux dose. Even if it dosn't it should still install... Maybe. Lol

You probably should have posted your steps in the Origin thread as well.

 

You probably should have posted your steps in the Origin thread as well.

 

Quote from booman

 

Its a bit discuraging when you have delete so manytimes but then that's the way with wine.I guess thats the way with compatiblity layers like wine.

 

Quote from steve723

That is why you only really do that for testing. lol. Also why we write scripts, so that we don't have to take so many steps to do manual installs. Like, if we have a working set of steps to get it to work, then can be scripted to a few clicks, instead of sometimes upward of 50-60 steps for certain apps to get working. ;) 

Don't get me started Ronin 

No good. The Sims 4 installer failed again at the same place. Looks like even wine 1.7.34 can't run the install. It still fails to detect VCrun2013.

 

Don't get me started Ronin 

 

Quote from booman

Hahaha. I am teasing you, and you know that, sir. :D

 

 

No good. The Sims 4 installer failed again at the same place. Looks like even wine 1.7.34 can't run the install. It still fails to detect VCrun2013.

Hmm. Let me see if I can figure out what the reg keys are and see if we can trick it into thinking that it's installed. I wish I knew why it was doing that in the first place. lol. 

So, when I try to install the real vcrun2013 executable into a fresh 32-bit drive running 1.7.34, it always stops here, and then gives an error:

fixme:wuapi:automatic_updates_Pause 

So, it looks like it is trying to access Windows updates for some reason, and it is failing? That is a guess. 

Looks like this one will be a difficult one to solve.

Well, from the looks of it, vcrun2012/2013 will need a patch with Wine to fix that error. Like, if a program calls to those DLLs, what we have will work fine. If the program wants to actually install it's own copy of those DLLs, it will fail. I am actually trying a few things right now. I will update if I get anywhere. 

 

OK, so this is what it is doing when it fails. It is the cache error. The access denied thing is misleading, as it is denied because for some reason it loses it. You can see where it went to stash it's bundle, and then when it tries to retrieve it, it cannot. Mind again, this is from the actual vcrun2013 exe.

.
[0008:0009][2015-01-12T17:31:30]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{f65db027-aff3-4070-886a-0d87064aabb1}, options: 0x7, disable resume: No
[0008:0009][2015-01-12T17:31:36]i000: Caching bundle from: 'C:\users\ronin\Temp\{f65db027-aff3-4070-886a-0d87064aabb1}\.be\vcredist_x86.exe' to: 'C:\users\Public\Application Data\Package Cache\{f65db027-aff3-4070-886a-0d87064aabb1}\vcredist_x86.exe'
[0008:0009][2015-01-12T17:31:42]e000: Error 0x80070005: Failed to cache bundle from: 'C:\users\ronin\Temp\{f65db027-aff3-4070-886a-0d87064aabb1}\.be\vcredist_x86.exe' to 'C:\users\Public\Application Data\Package Cache\{f65db027-aff3-4070-886a-0d87064aabb1}\vcredist_x86.exe'
[0008:0009][2015-01-12T17:31:42]e000: Error 0x80070005: Failed to cache bundle from path: C:\users\ronin\Temp\{f65db027-aff3-4070-886a-0d87064aabb1}\.be\vcredist_x86.exe

So, we need to see why it is failing to remember where that is at. Maybe if I script in the variable to the actual POL script and make it available, it might not fail?

It's a permissions issue with the folder that it is creating. When I install it, I can will even manually create the folder, and whatch it change permissions with the program. I think I am on the right track. 

So, this folder, when vcrun2013 is installing, changes permissions to forbidden during the install. I tried to create the folder myself, but it still changed the permissions. I set them to basically YES TO EVERYTHING, and it still switched it over to that. The folder in question is:

/drive_c/users/Public/Application\ Data/Package\ Cache/{f65db027-aff3-4070-886a-0d87064aabb1}

This is, of course, within your virtual drive. This is the showstopper. It creates a folder with unwritable permissions, and then complains when it cannot write to it. If we can figure out how to stop it from changing the permissions (for instance, does anyone know of a way to change permissions for a folder and not let those permissions change, but still let the folder be writeable), that would likely let it install. That is at least the first step. 

Any ideas?

I can see others have discovered this being the issue, as well. There is apparently a patch floating around in the wine-compholio repo, but I am not sure which one it is. It is a call that is doing on the Windows API level that I don't think that we can mimic, so again, I think we are at the mercy of the talented C/C++ devs contributing to Wine. I swear, this seems like it would be an easy fix if I knew these languages. hahaha.