open All Channels
seplocked Linux
blankseplocked New SISI patcher ***SOLVED
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: [1] 2

Author Topic

Mes Ren
No Trademark
Posted - 2009.02.13 22:56:00 - [1]
 

Edited by: Mes Ren on 14/02/2009 04:17:45

Has anyone been able to get this patcher + RTP file to work with the new SISI build? I haven't yet been able to get it to work successfully. The details say it failed to run some file it's putting in a temp file, then deletes the RTP file as it fails.

*** SOLVED

To fix this problem, I copied the WINSxS folder from my old WinXP installation (still have it sitting on a partitin, never have gotten around to clearing it off) and replace the winsxs folder with it in wine (actually renamed that folder on wine first so I could go back if it didn't work). Seems the problem is that we don't have the correct information in the WINSxS to direct the program to the appropriate .dll's. I haven't yet figured out what is needed out of my WINSxS to make it work though, i'll keep checking, or if someone who knows more about this than I do can fine tune this faster, please do.

Further Edit -- Solution

Ok, did some further testing -- no need for a previous WinXP installation. In your bin subfolder of your eve folder there is a folder called: 'Microsoft.VC80.CRT'.

You need to take the 'Microsoft.VC80.CRT.manifest' file in this folder and copy it to your '~/.wine/drive_c/windows/winsxs/manifests' folder. Then you need to rename this file to: 'x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.manifest'.

You then need to copy the 'Microsoft.VC80.CRT' folder to the '~/.wine/drive_c/windows/winsxs' folder. After this, you need to delete the 'Microsoft.VC80.CRT.manifest' file out of the '~/.wine/drive_c/windows/winsxs/Mircosoft.VC80.CRT' folder. Finally, you need to rename the '~/.wine/drive_c/windows/winsxs/Mircosoft.VC80.CRT' to '~/.wine/drive_c/windows/winsxs/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700'.

It is very possible that the only thing that needs to happen as far as renaming files is that "x86_" needs to be added to the front of the file and folder, but I know you can't simply put them in the appropriate places and not rename them. If someone wants to test this, that would be great. Also, if someone wants to put together some better instructions for people to be able to accomplish this task, lots of other people may appreciate it.

deathlords
Posted - 2009.02.13 23:23:00 - [2]
 

The new Sisi patch is complete BS from wine standpoint.

1. It *DELETED* the patch I downloaded manually - that's just total crap. *Poof* 2 hour download. Best next time to download it to a non-accessible directory, hard link it to sisi directory and probably make sure chmod to read-only.

2. It failed to patch.

3. Error message was something "An error has occurred".

4. Then it tells me to "manually patch".

deathlords
Posted - 2009.02.13 23:35:00 - [3]
 

Edited by: deathlords on 13/02/2009 23:37:02
Edited by: deathlords on 13/02/2009 23:36:44
It seems it is missing MSVCR80.DLL. So, windows users without Visual Studio 2005 runtime are probably out of luck as well.

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\windows\\temp\\nsue4.tmp\\ApplyRTPatch.dll") not found
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\windows\\temp\\nsue4.tmp\\ApplyRTPatch.dll") not found

So, I guess we'll have to see if installing MSVCR80 fixes the problem.


Link to the redistributable:

http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en

Ravow
Minmatar
Cosmic Encounter
Mayhem.
Posted - 2009.02.13 23:47:00 - [4]
 

Edited by: Ravow on 13/02/2009 23:56:26
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"

According to the net, we will need dotnet 2.0....thank CCP Evil or Very Mad The patcher work for more than 5 years and now they want .net infected stuff :(

Mes Ren
No Trademark
Posted - 2009.02.14 00:20:00 - [5]
 

Been doing some homework on this, the required .dll's are in the eve folder already in the Bin subfolder. I'm trying to figure out how to make the patcher recognize this.

Ravow
Minmatar
Cosmic Encounter
Mayhem.
Posted - 2009.02.14 01:59:00 - [6]
 

Perfect!

The patcher download the patch!
So I will add this manipulation to my script!

Merende Macaco
Posted - 2009.02.14 02:00:00 - [7]
 

Edited by: Merende Macaco on 14/02/2009 02:02:21
Thanks, your fix did the trick here as well. Now to see if they seeded the gallente defence subsystems...

Oooh shiny new logon screen

Sevarus James
Minmatar
Meridian Dynamics
Posted - 2009.02.14 02:07:00 - [8]
 

Edited by: Sevarus James on 14/02/2009 02:45:03
Gonna wait until my compile of wine 1.1.15 is complete. (its doin' make /make depend as I type this.)

Gotta say, CCP LOVES frackin' around with us don't they? lol.

If 1.1.15 doesn't solve patch, will use your hack.

BITS...MS shoulda' called it "bits/n/pieces" if you ask me. sigh.Rolling Eyes

update: wine 1.1.15 fails with this:
~/Desktop$ wine evepremiumpatch77718-79298_test.exe
fixme:ntoskrnl:KeInitializeSpinLock stub: 0x4577a4
fixme:shell:SHAutoComplete SHAutoComplete stub
fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\windows\\temp\\nsp2cd.tmp\\ApplyRTPatch.dll") not found
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT"
err:module:import_dll Library MSVCR80.dll (which is needed by L"C:\\windows\\temp\\nsp2cd.tmp\\NSISBITS.dll") not found

So, it looks like the work around is it even on 1.1.15. Of course SISI is down again, so will futz with it again tomorrow.

Mes Ren
No Trademark
Posted - 2009.02.14 04:13:00 - [9]
 

Edited by: Mes Ren on 14/02/2009 04:59:33
It turns out that Windows has a ton of problems with these files due to their poor implementation of libraries. Basically though, when you install EVE, somewhere along the way they are that folder is supposed to get copied to the winsxs directory in a similar maner to what is outlined (I'm still pretty sure we don't need all the numbers and stuff, just the x86_). On my old WinXP partition (haven't used it in over a year) that directory was created from the EVE directory, under wine it's not creating it and I don't know why. I'm not sure if it is an issue with wine or and issue with EVE.

I don't play any other games under wine (.dll files and manifests like this are common with modern 3d games) so I can't check, but if anyone is playing some other games under wine check to see if there are any other directories in your winsxs folder other that manifest. If we find other games that are installing these files in the winsxs folder, then we know it's an issue with EVE. If we can't find any, then it is probably an issue with wine.

** Update

Seems there is a number of Windows people starting the have a similar issues that we are, which is leading me to believe that CCP skipped a step some place in making sure that that these .dll's were registered correctly. Still waiting to for someone who plays other games to check their winsxs folder.

Sevarus James
Minmatar
Meridian Dynamics
Posted - 2009.02.14 05:16:00 - [10]
 

Confirmation from a windows user that your fix works there as well:

Game dev forum

deathlords
Posted - 2009.02.14 16:51:00 - [11]
 

Edited by: deathlords on 14/02/2009 16:53:05
Sorry, but that solution, while it may work, is really nasty.

The solution is simply to install the vistual C++ runtime. The problem is the .exe file fails under wine.

So, solution is to install *any* MSI that includes the runtime. That will install the SxS. But if you do it by hand, you are possibly breaking stuff thanks to the way SxS DLLs work.

I'm not going to make a special MSI with just "hello world" for this incarnation of the patcher to work. But if they actually release with a broken patcher (it will fail on lots of windows computers), I'll make that MSI file for wine users.

Cheers,
DL

PS. Yes, there is A LOT of directories you are missing. And lots of registry keys too. That's why only supported installation of this SxS is through Windows Installer.


rig0r
The Gravedigger Company
Posted - 2009.02.14 16:56:00 - [12]
 

Easy mode:

# wget http://www.kegel.com/wine/winetricks
# sh winetricks vcrun2005sp1

Did the trick for me. Apparently it really needs the SP1 version, the earlier version (vcrun2005) did not work.

Mes Ren
No Trademark
Posted - 2009.02.14 17:39:00 - [13]
 

Originally by: deathlords
Edited by: deathlords on 14/02/2009 16:53:05
Sorry, but that solution, while it may work, is really nasty.

The solution is simply to install the vistual C++ runtime. The problem is the .exe file fails under wine.

So, solution is to install *any* MSI that includes the runtime. That will install the SxS. But if you do it by hand, you are possibly breaking stuff thanks to the way SxS DLLs work.

I'm not going to make a special MSI with just "hello world" for this incarnation of the patcher to work. But if they actually release with a broken patcher (it will fail on lots of windows computers), I'll make that MSI file for wine users.

Cheers,
DL

PS. Yes, there is A LOT of directories you are missing. And lots of registry keys too. That's why only supported installation of this SxS is through Windows Installer.




That solution is exactly what happened on my original EVE installation from WinXP a year+ ago. Somewhere along the way, EVE stopped installing those files (which they include with the game) OR wine is not installing them correctly. From the sounds of all the other windows people having issues, it is EVE that is broken and will hopefully get fixed. Incidently, Microsoft's implementation of this crap is horrible. I had the exact same files (different revisions) installed by various different games all with their own identified folders. As far as how windows idnetifies this files, it is all done by the manifest file which is provided by each individual game.

linkeleo
Fairlight Corp
Rooks and Kings
Posted - 2009.02.14 18:42:00 - [14]
 

sack whoever did this and give their job to a blind monkey

ckr
Posted - 2009.02.14 21:19:00 - [15]
 

Originally by: rig0r
Apparently it really needs the SP1 version, the earlier version (vcrun2005) did not work.


Yep. That vcrun link above was to a pre-SP1 download and did not work.

The SP1 version does work. Got it here:

http://www.microsoft.com/downloads/info.aspx?na=47&p=2&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=32bc1bee-a3f9-4c13-9c99-220b62a191ee&u=details.aspx%3ffamilyid%3d200B2FD9-AE1A-4A14-984D-389C36F85647%26displaylang%3den

Zaraa
United Forces
Posted - 2009.02.15 00:20:00 - [16]
 

Edited by: Zaraa on 15/02/2009 00:22:07
Edited by: Zaraa on 15/02/2009 00:21:52
I know this thread have been marked as solved but I solved this problem myself a diffrent way, so here it goes.

I used winetricks to change OS to winxp (to force sp1) and install vcrun2005sp1.
wget http://www.kegel.com/wine/winetricks
sh winetricks winxp vcrun2005sp1

winetricks will download and install all needed for solveing this problem (and others), so check it out if you haven't seen it before!

Sevarus James
Minmatar
Meridian Dynamics
Posted - 2009.02.15 03:44:00 - [17]
 

Edited by: Sevarus James on 15/02/2009 03:44:17
Originally by: ckr
Originally by: rig0r
Apparently it really needs the SP1 version, the earlier version (vcrun2005) did not work.


Yep. That vcrun link above was to a pre-SP1 download and did not work.

The SP1 version does work. Got it here:

http://www.microsoft.com/downloads/info.aspx?na=47&p=2&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=32bc1bee-a3f9-4c13-9c99-220b62a191ee&u=details.aspx%3ffamilyid%3d200B2FD9-AE1A-4A14-984D-389C36F85647%26displaylang%3den


Yep, that solved this issue here. Awesome stuff folks! What's interesting is the feedback in game dev section or lack thereof from CCP regarding this as its an installer issue, not a "wine" issue.

If they want to look at 'why' we dumped their official client, here is yet another example...no communication tween them and our community. As we can't BUG REPORT because we're immediately filtered due to platform, this is the only way for us to let em' know.
sigh.

Fen Quai
Posted - 2009.02.15 04:13:00 - [18]
 

Excellent stuff. That last Visual C++ redist did it!
Tried the rename and copy stuff earlier, but to no avail. Other Visual C++ installer was no good either.
Thanks for the tech tackling guys.

Woo Mi
Posted - 2009.02.16 20:07:00 - [19]
 

Ok, the winetricks trick did the trick, the updater now seems to work.
However, it doesn't see the .rtp file I already downloaded by hand.
Can I force it to use the .rtp file, or should I just be patient and wait for it to download from bits? 2 hours?

deathlords
Posted - 2009.02.17 05:00:00 - [20]
 

It is the patcher issue, not Eve installer issue.

Eve installer doesn't install the runtime as a central SxS (side by side DLL - like versioned API or kind of like sonames on Linux). They don't do that because they are now using the simpler method of distributing it in the installation directory as a XCopy installation of the runtime.

That works just perfectly, until the patcher. The patcher does the following:

1. unpacks the RTP file into a temporary directory
2. tries to run the actual patching API call (looks like a DLL)
3. the XCopy installation requires the runtime to be in same directory as the executable, so the one distributed with EVE is never found.

CCP knows about the problem and will fix it. They will have to distribute the runtime with the patch or copy it from the installation to the temp. location of the patcher, before it is run. That's just few lines of code to worry about - nothing overly technical.

CCP does not install the runtime anymore because the only supported way of installing the runtime is though Windows Installer (the MSI files). Other installations are not supported, with the exception of the Microsoft boostrapper that also uses the Windows Installer.

As you have noticed, CCP doesn't use MSI. So they are stuck with XCopy method of distribution.

So, the patcher issue is just a simple omission. Windows users will also be affected by this bug. Pre-Vista doesn't have this runtime installed by default.

Installing the SxS runtime into system32 directory is not supported by Microsoft and is probably not a good idea to do under Wine as well. Yes, the redistributable runtime for VS2005 SP1 is the way to go.

winetricks just downloads the redistributable and installs it for you.

Aside: If you loath SxS and the way the runtimes work with VS2005 and 2008, you are not alone. But it is still better than the DLL Hell of the past! That problem at least is solved.

Woo Mi
Posted - 2009.02.17 19:55:00 - [21]
 

Ok, tried again and let the patcher run a long time. It seemed to crash at the end, but I am into singularity and got the intro movie.
Now I'll just read up on the test server before I do something inappropriateCool

Gilbert T
Gallente
Gladiators of Rage
Posted - 2009.02.24 22:10:00 - [22]
 

Edited by: Gilbert T on 24/02/2009 22:11:00
the program just puts a flickering 'downloading' window on the screen which appears to be doing nothing, and doesn't respond to any clicks or anything...

I have no way to know whether it is working or not.

Miraqu
Caldari
Posted - 2009.02.24 22:19:00 - [23]
 

I have the same flickering window. The patch prior to this one worked good. Still complained about a dx-error but aside from that I was still able to start the testclient.

As soon as this state starts, the cpu usage drops to zero and I can't detect any internet activity much less downloading a 28mb patch.


Sevarus James
Minmatar
Meridian Dynamics
Posted - 2009.02.24 22:30:00 - [24]
 

Edited by: Sevarus James on 24/02/2009 22:30:30
Originally by: Miraqu
I have the same flickering window. The patch prior to this one worked good. Still complained about a dx-error but aside from that I was still able to start the testclient.

As soon as this state starts, the cpu usage drops to zero and I can't detect any internet activity much less downloading a 28mb patch.




Please see this thread for the work around.


Mes Ren
No Trademark
Posted - 2009.02.25 00:54:00 - [25]
 

Edited by: Mes Ren on 25/02/2009 00:57:58
Originally by: Gilbert T
Edited by: Gilbert T on 24/02/2009 22:11:00
the program just puts a flickering 'downloading' window on the screen which appears to be doing nothing, and doesn't respond to any clicks or anything...

I have no way to know whether it is working or not.


Mine does the same, though I figured out that if I change the focus from the patcher window to something else, and then go back, the information has updated to current at the moment the patcher window gained focus again.

Woops, spoke too soon, finally froze at 391MB. Time for manual patch.

Viktor Rasmussen
Gallente
Eagle's Club
Posted - 2009.02.27 12:13:00 - [26]
 

Just want to say that you guys doing a GREAT job supporting other linux users! A job CCP should do! however - with the help of this topic I was able to patch my client to the actual sisi version with two steps.

Good word!

Woo Mi
Posted - 2009.02.27 13:13:00 - [27]
 

Ok, incremental patching doesn't seem to work.
Just downloading the patcher gives the flickering screen.
By hand downloading not the latest rtp file (81170) again leads to incremental patchSad

I finally got it to work by:
- copying my tranquility folder again
- doing the winetricks trick
- downloading the latest patcher
- downloading the latest rtp file: 81762 rtp file
At this point running the patcher leads directly to patching and not to the flickering download mess and I got a working sisi again.

Viktor Rasmussen
Gallente
Eagle's Club
Posted - 2009.02.27 13:31:00 - [28]
 

Well, I was lucky with that trick. I could upgrade to the latest patch.

However, the game is now stuck in the splash screen. I never see the login screen :)
But it seems that I'm not alone with this problem -> http://www.eveonline.com/ingameboard.asp?a=topic&threadID=998251&page=3

Woo Mi
Posted - 2009.02.28 13:37:00 - [29]
 

Ok, another incremental upgrade and another flickering failure.
I'll do yet another full install next weekend. Maybe I'll get lucky and skip a few updates. I just hope this problem disappears before apocrypha goes live, as a full install with each update is a painCrying or Very sad

Aurix Lexico
Slacker Industries
The Boat Violencing Initiative
Posted - 2009.02.28 14:17:00 - [30]
 

I just download the incremental patch + rtp file, then patch like that.


Pages: [1] 2

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only