Application Details:
Version: | Update 8, Riders of Rohan |
License: | Free to use |
URL: | http://www.lotro.com/ |
Votes: | Marked as obsolete |
Latest Rating: | Gold |
Latest Wine Version Tested: | 1.5.18 |
Maintainers: About Maintainership
What works
Installation, patching, cinematics, character creation, game play, music and ambient sound.
What does not
Workarounds
What was not tested
voice chat
Hardware tested
Graphics:
Additional Comments
Used non-GUI launcher script from http://bmx-chemnitz.de/~mfr/LOTRO/lotrolauncher.script Installed in a directory without any spaces in path name (i.e. /home/me/.wine-lotro/GAME/Turbine/LOTRO)
Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
Current | Ubuntu 12.10 "Quantal" i386 (+ variants like Kubuntu) | Nov 24 2012 | 1.5.18 | Yes | Yes | Gold | Koray Ozcan | ||
Show | Arch Linux x86_64 | Sep 16 2012 | 1.5.12 | Yes | No | Garbage | Björn Bidar | ||
Show | Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu) | Oct 16 2012 | 1.4.1 | Yes | No | Garbage | Koray Ozcan | ||
Show | Linux Mint 13 "Maya" | Oct 17 2012 | 1.4 | Yes | No | Garbage | an anonymous user |
Bug # | Description | Status | Resolution | Other apps affected |
As of October 15th, 2012, with the release of Riders of Rohan, this game is broken on versions of wine prior 1.5.18 , resulting in this error:
wine: Unhandled page fault on write access to 0x00000034 at address 0x6d3fd2 (thread 0024)
If your distrubtion dosn't ship an actual wine version you need to build yourself.
For instructions on building wine, see below. However, note that this is a quite advanced task.
These Binaries are outdated use with care:
UPDATE: Prebuilt binaries for the following distributions can be
downloaded from the links below. Note that these are not packages
(.deb, .rpm, etc.), see install instructions below.
To install, extract the archive some place, like /home/username/local/wine-1.5.15-lotro. Example:
mkdir -p ${HOME}/local/wine-1.5.15-lotro cd ${HOME}/local/wine-1.5.15-lotro tar xf path/wine-1.5.15-1-x86_64.pkg.tar.xz
Now, start pylotro and go to Tools --> Options, check "Advanced Options" and enter /home/username/local/wine-1.5.15-lotro/bin/wine in "Wine Binary" text box. Obviously, replace "username" with your own.
This page is now considered Outdated. Please move onto Update 12
Please add the following informations to the test:
- GPU
- driver name + version
- kernel version
- desktop environment if needed
- distribution
Tweaking the game:
Setting the video memory size usually fixes most performance issues. However
there is a list of things you can do to try to kick the performance up
an extra notch. Of course these are just suggestions. They are all
optional.
Disable desktop 3D effects
The 3D desktop features can cause some performance issues in the game.
Logging out and changing your Desktop session, or disabling 3D desktop
effects can greatly increase game performance.
Choose a ‘Graphics Quality’ in Options->Graphics
It’s common for the auto detection to misdetect the card since there is a
wine api in the middle of everything. Select this manually to get the
quality you want. (I chose ‘very high’ for my 1gb Nvidia card)
Increase ‘Texture Cache Size’ in Options->Adv. Graphics
You can increase this to improve the game performance by increasing the
amount of system memory used for graphics resources. This can decrease
load times and in turn increase game performance.
Enable ‘Triple Buffering’ in Options->Adv. Graphics
For video cards with extra memory you can use this setting to slightly increase rendering performance.
Disable ‘Player Mesh Combining’ in Options->Adv. Graphics
This feature not only uses up more system memory, but also video memory.
Saving a little video memory can always help game performance.
Disable ‘Distant Imposters’ in Options->Adv. Graphics
This option simply allows trees and other objects to render over distant scenery. Can be disabled to increase game performance.
Enable OpenGL Render
Since December 2011 Lotro has an OpenGL Render you can use it bychanging "GraphicsCore" in "$WINEPREFIX/dosdevices/c:/users/$USER/My Documents/The Lord of the Rings Online/UserPreferences.ini" to "OpenGL".
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Björn Bidar on Saturday November 24th 2012, 7:46
by William Magill on Tuesday November 26th 2013, 18:39
Update 12: Helm's Deep
by Brandon Morris on Monday November 19th 2012, 23:37
Encounter #1:
Ok I've received this error a bunch of times before in the past. Most times it's because the game data location hasn't been set. However, as harddrive space is needed, I normally just delete the large game data files and leave the rest of the stuff in tact. The problem with this approach is it leaves enough game data that the game data error doesn't seem to occur (I'll have to check that just to confirm; it's my suspicion though), but not enough data to get rid of the No language files found error. So this can lead to some scratching their heads wondering what they are doing wrong when they know they've clearly spelled out the proper folder. It still IS a game data issues, just check the folder and make sure ALL the larger game data files are there, not just the folder structure and the 1k to 5mb files.
Encounter #2:
If you're like me and didn't want to bother building wine with the source (I've had catastrophes with successful builds now causing my wine server to not be in synch which leads to all sorts of problems) then you likely went with the binary version (Or your waiting for the next dev release to fix it, in which case, why are you reading this anyway? ;) ). The problem with this approach is, if you went with the bottom one, like I did, the one labeled: "x86_64/i686 (generic, some parts like wine64 are only useble with x86_64)" and you spell out all the settings in PyLotRO like I did, you'll find you wind up getting:
"[E13] Game Directory not found"
and
"[E02] No language files found."
errors. There seems to be a weird x64/x86 bug. Now I don't know how far spread it is, whether it only exists in this specific wine fork or whether it's PyLotRO's fault, etc. But what seems to be occurring is the binary version that you downloaded is the windows emulated (*ahem* layered *ahem*) version, and as far as the layer's windows environment is concerned it is a 64 bit os, and thus searches the paths of "Program Files" first (As it should), the problem is, it doesn't seem to fall back to "Program Files (x86)". I tested this because I was getting Settings Wizard to find the LotRO folder just fine (Problem was it was a partially deleted folder), and I kept getting E02 error. Once I renamed the folder I got both errors (Since it could no longer be found), so what I did was created a symlink of "Program Files (x86)"'s Turbine folder, and moved that symlink into "Program Files", I then whacked the settings wizard button again and had it find installations, and viola! it found it. This kinda confirms there does seem that PyLotRO's settings wizard is not checking the x86 folder, now whether that's due to wine's APIs not falling back to 32 bit folders or whether it's PyLotRO's fault I dunno.
I suspect because the PyLotRO version I'm using now, is the python version (There seems to be two versions, one executable based and one pure python based), that wine is not involved in the problem. But I cannot confirm that PyLotRO isn't using wine prior to launching the game. However, either way, it's relevant to working towards getting more people able to run LotRO (Though mods may disagree as it might turn out to be the case that Wine isn't involved at all -- in which case maybe this post is better for PlayOnLinux?).
by William Magill on Tuesday November 20th 2012, 10:35
One version is a "compiled" version in a Windows Package -- which DOES use WINE.
The other version is a pure Python "compiled" version which requires Linux Python, and, I do not believe, uses wine UNTIL it goes to launch the game engine itself.
The "compiled" Windows Package is the version which has been used with CrossOver to run LOTRO.
The Turbine Knowledge base list of .dat files expected by LOTRO (and DDO) can be found here::
support.turbine.com/ics/support/kbanswer.asp?deptID=24001&task=knowledge&questionID=283
by William Magill on Tuesday November 20th 2012, 10:37
Hopefully I'll have it back on line later today or tomorrow (11/21)
by Brandon Morris on Sunday November 25th 2012, 20:26
"wine client error:0: version mismatch 431/437.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?"
I know I've set the wineserver environment variable properly by echo'ing $WINESERVER before running pylotro from the cli, yet I get this error. From looking at the entries in top portion of this page, the latest 1.5.18 seems to be labeled as gold, so technically I shouldn't need the special build and so I've tried pylotro without setting the environment variable and without using the special build and just using the updated ppa version (The 1.5.18). Yet, I still get the error -- which is deeply confusing especially since I kept the special wine build (listed above) separate from my main/system wine install.
What's odd is it seems like when wine is run, it's not checking the env. variable. Either that OR the "Wine Program" field in pylotro's Game Settings menu doesn't do anything and pylotro is reverting to my system wine that then notices the env. variable and uses the special wineserver version causing the version synch-issue. But even without the env. variable set, and NOT specifying advanced settings in pylotro (so that the wine path setting can be manually specified), the error still crops up, despite the system wine install should be used for everything at that point.
Trying to look into the special wine build problem further, I've tried to manually run wineserver (it should just display a small help output of the various parameters you can pass to it) yet I'm finding when I run wineserver I get:
"bash: ./wineserver: No such file or directory"
even if I execute the command "./wineserver --help" I still get that error, yet if I look at the directory, the file is there along with all the other programs (wine, winecpp, wineg++, winegcc, etc.) and I can run those other programs and get output from them. This has me deeply troubled. Has anyone ran a diff on the source of 1.5.15 vs 1.5.15-lotro (specifically on the wineserver's cpp files)? Are we sure that what was uploaded is on the up and up? Only thing that keeps me from being overly paranoid is I ran strace on it and as far as bash is concerned, it does legitimately seem like bash can't find "./wineserver" when its sitting in your pwd.
by Björn Bidar on Sunday February 3rd 2013, 12:01
by Logan on Saturday April 6th 2013, 12:06
by Logan on Saturday April 6th 2013, 12:14
by William Magill on Sunday November 4th 2012, 18:29
See this thread:forums.lotro.com/showthread.php?486784-Thanks-Turbine-for-the-Mac-Client
And the announcement is buried at post #15 of this thread: forums.lotro.com/showthread.php?483496-Timeframe-Mac-Client&p=6505137#post6505137
And there is new Mac Technical Support Thread: forums.lotro.com/forumdisplay.php?710-MAC-Technical-Support
Note the Mac client is a full 16GB DMG file download!!! (and to quote Sapience -- no Pando, no Happy Cloud).
by Björn Bidar on Thursday November 1st 2012, 9:05
wine displays this at the end:
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf75a0ab8
wine client error:9:
write: Ungültiger Dateideskriptor
Someone else having the issue? is it maybe related to Bug #31979?
by Dif on Friday November 2nd 2012, 11:48
Right now I got the error while exiting the game and with the WINEDEBUG value to empty I a similar error:
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf759f31a
wine client error:9:
write: Bad file descriptor
by Björn Bidar on Friday November 2nd 2012, 11:58
Do you use Pulseaudio in OpenAL? Do you get similar errors i posted in the comment 'Out of Memory'
by Dif on Saturday November 3rd 2012, 14:05
by Satronix on Friday October 26th 2012, 6:29
home/satronix/lotro/bin/wine
I don't get the (Unhandled exception: page fault on write access to 0x00000034 in 32-bit code (0x006d3912)) error. However when i log into pyLotro, and enter my password, the Wine Output window says:
err:ole:CoUninitialize Mismatched CoUninitialize
*** Finished ***
Anyone know how to correct this?
by Satronix on Friday October 26th 2012, 6:31
by Kootee on Thursday November 8th 2012, 10:51
by Satronix on Friday October 26th 2012, 6:29
home/satronix/lotro/bin/wine
I don't get the (Unhandled exception: page fault on write access to 0x00000034 in 32-bit code (0x006d3912)) error. However when i log into pyLotro, and enter my password, the Wine Output window says:
err:ole:CoUninitialize Mismatched CoUninitialize
*** Finished ***
Anyone know how to correct this?
by Satronix on Friday October 26th 2012, 6:28
home/satronix/lotro/bin/wine
I don't get the (Unhandled exception: page fault on write access to 0x00000034 in 32-bit code (0x006d3912)) error. However when i log into pyLotro, and enter my password, the Wine Output window says:
err:ole:CoUninitialize Mismatched CoUninitialize
*** Finished ***
Anyone know how to correct this?
by Kootee on Thursday November 8th 2012, 10:52
by Kootee on Thursday November 8th 2012, 14:57
Tools -> Patch
After he has ended patching all worked like a harm.
by Satronix on Saturday November 10th 2012, 5:21
by Kootee on Saturday November 10th 2012, 5:54
If you want to try use my compiled wine (32 bit, compiled in Ubuntu 12.04): www.dropbox.com/s/jdmeq38b7cve7e6/wine-lotro.7z
by Satronix on Saturday November 10th 2012, 20:51
by Satronix on Monday November 12th 2012, 9:14
by Dif on Thursday October 25th 2012, 16:15
I often get either an "error:9: write: Bad file descriptor" or cases where the game freezes without errors.
I had the "error:9: write: Bad file descriptor" in the past (soon after Book 5 of Vol. III) and in that case I simply had to re-install the game and re-patch it, but now I get the error even a full re-install (re-downloaded the installer, set up a new wine prefix, etc.).
I have Gentoo 64 bit multilib with:
Kernel 3.5.7 (tested also previous versions)
Nvidia drivers 304.48 (tested also previous versions)
Wine - the patched version posted in this page.
Do you need any other info or test I can make?
by Björn Bidar on Thursday October 25th 2012, 16:22
by Dif on Friday October 26th 2012, 15:52
What should I do to get more output?
I tried to set PyLotro to use winedbg instead of wine, but after clicking "Login" I only get the following and it doesn't even launch the game (while normal wine launch the game and I can even log in a char and play for sometime before the hang):
WineDbg starting on pid 0022
0x7b85f773: movl %edi,0x4(%esp)
Wine-dbg>
by Apoc on Friday October 19th 2012, 19:42
by Björn Bidar on Friday October 19th 2012, 19:49
by Apoc on Friday October 19th 2012, 21:34
I then tried removing every version of gecko I had installed, and let wine re-install it manually. Still no luck.
What I did find though, is that if I load up the wine version of IE, and run lsof, I find it's accessing a heap of stuff to do with gecko (as expected). But doing the same thing with LOTRO open, I get nothing returned. It seems as if LOTRO is never even accessing gecko (which I guess would explain the complete blankness of the store). Not entirely sure where to go from here though.
by Chuck on Friday October 19th 2012, 19:49
by steelsnake on Thursday October 25th 2012, 1:08
There's a lot of output on the console about it:
[8:54:19251:ERROR:chrome_url_request_context.cc(94)] Cannot use V8 Proxy resolver in single process mode.
[8:64:24321:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 0
Whatever Turbine is doing, it's not good for people using Linux.
by Marko Friedemann on Thursday October 25th 2012, 10:01
I am not sure, but the error messages steelsnake posted hadn't been there before the maintenance on 10/24, but there was no client update.
Or was there and I missed it? Will report back.
by William Magill on Thursday October 25th 2012, 12:39
I started getting a "massive" (i.e. many more than the previous zero) number of proxy failure messages in the PyLotRO "console" window.
Hopefully this is merely a TTL issue and within a day or two the problem will resolve itself.
by William Magill on Thursday October 25th 2012, 12:41
by Marko Friedemann on Thursday October 25th 2012, 12:51
by Dave on Wednesday January 2nd 2013, 20:14
"winetricks vcrun2008 corefonts" fixed it for me.
by Michael Davenport on Wednesday January 2nd 2013, 23:03
by William Magill on Friday October 19th 2012, 18:45
1- Install MacPorts (visit macports.org to download the basic system.
2- build "wine-crossover" -- sudo port install wine-crossover
This will take a significant amount of time, however it is completely automated.
3- Install XQuartz (Double click on the X11.app file in /Applications/Utilities and follow the instructions.)
Once both are installed:
1- Launch XQuartz... double click on the app in /Applications/Utilities
Modify the following command line for your system:
1- is your userid on your system
2- CrossOver's default installation names the Bottle for LOTRO -- "The Lord of the Rings Online"
WINEPREFIX="/Users//Library/Application Support/CrossOver/Bottles/" wine ~/Library/Application\ Support/CrossOver/Bottles//drive_c/Program\ Files/PyLotRO/pylotro.exe
Note that this is a single line command. You will probably need to reconstruct it as each backslash "\" is before a single space which browsers will use to "wrap" the line
If when you launch Wine, it complains about needing an Xserver ... you did not launch XQuartz FIRST!
Other than that, just ignore the errors in your terminal window -- and enjoy the game -- AGAIN!
Don't forget to patch first !
Note that this only addresses the WINE bug which caused an immediate crash on launch from PyLotRO. (I.e. as soon as you entered your userid and password.)
by Michael Jones on Saturday October 20th 2012, 5:54
by Björn Bidar on Saturday October 20th 2012, 6:15
by Michael Jones on Saturday October 20th 2012, 10:29
/Users//Library/Application Support/CrossOver/Bottles
does not exist for me, so I had to change the above command to the following:
WINEPREFIX="/Users//Library/Application Support/Wine/Prefixes" wine /Users//Library/Application\ Support/Wine/Prefixes/LOTRO/drive_c/program\ files/PyLotRO/pylotro.exe
IMPORTANT: You must cd to the directory that pylotro.exe is found in before executing this command, eg
cd /Users//Library/Application\ Support/Wine/Prefixes/LOTRO/drive_c/program\ files/PyLotRO/
and you must use this command every time you want to play LOTRO. You can use a script to do this, but that's beyond me - I'm happy to just use the terminal to run the game. (Björn, you may want to reply to this and post the script you sent me in case others find it useful).
by William Magill on Saturday October 20th 2012, 13:16
All MacPorts does is simplify the installation and building of WINE. The executable is in the "normal" MacPorts location -- /opt/local/bin/wine -- which you would (theoretically) have in your path.
Your bottles are wherever you have located your bottles.
CrossOver simply provided a convenient mechanism to install the LOTRO client and add a number of Microsoft products to the bottle which are not part of the normal WINE environment. And it stored all its files in an "Apple-Way friendly" location.
XQuartz is simply X11 for OSX. While X11 used to be distributed directly by Apple, now they distribute a "pointer" which sends you to XQuartz to get the binary.
by Björn Bidar on Wednesday October 17th 2012, 16:19
in the virtual desktop?
Here is a screen what is left when loro gets minimized:
imageshack.us/photo/my-images/526/smallbox.png/
by Daniel Santos on Wednesday October 17th 2012, 18:51
by Björn Bidar on Thursday October 18th 2012, 4:14
by Björn Bidar on Wednesday October 17th 2012, 11:04
by Chuck on Wednesday October 17th 2012, 11:09
by Chuck on Wednesday October 17th 2012, 17:07
by William Magill on Wednesday October 17th 2012, 17:29
That's the "Selection Indicator" it's not really new -- just defaults changed... two options control it:
Options/UI Settings window:
Selection Indicator: "When checked, the selected creature or NPC will display a selection indicator."
and
Show Selection Indicator in combat only: "When checked, the selection indicator will only be shown when you're in combat. This preference is only available when the 'Selection Indicator' preference is on."
by Marko Friedemann on Thursday October 18th 2012, 11:10
It starts to lag really badly after a short time, leaking memory in the Gigabyte range (see the windows crash reports). It does this relatively quickly using the OpenGL renderer while it takes much much longer to happen with the D3D9 one.
So I switched back to be able to play.
by Björn Bidar on Monday October 15th 2012, 21:11
here is the file:docs.google.com/open?id=0B_FQtIHEHNn8YlFlU2p4UmVOVUU
*(www.sysprofile.de/id123113)
by Stefan Wolff on Tuesday October 16th 2012, 4:48
docs.google.com/open?id=0B_dkcsYE5yPfVTFUV0w5RnduY0U
by Daniel Santos on Wednesday October 17th 2012, 18:53
by Daniel Santos on Wednesday October 17th 2012, 19:23
If you would be willing to make a build like Stefan did, we would have Ubuntu & Arch Linux covered. The only other major distro to worry about then would be Debian. :)
by Erich Fischer on Monday October 15th 2012, 20:53
So, forgive me if this is a noob question, but I can't seem to get pyLOTRO to use a different wine. Note: I am NOT talking about a different prefix. That works great. How do I tell pyLOTRO to use the patched wine?
I tried creating a link in /usr/bin and having pyLOTRO run that program from the options -> wine-program, but I got a 'not enough arguments' error. I can't seem to find an argument to put in there to make it work though. Help would be very much appreciated.
by Björn Bidar on Monday October 15th 2012, 21:00
wine lies in folder "bin" in the prefix so the path of wine is "/home/bidar/.wine-ver/lotro/bin/wine" this is what entered in the box "Wine Binarie" in options.
by Daniel Santos on Monday October 15th 2012, 21:07
by Erich Fischer on Monday October 15th 2012, 21:18
by Björn Bidar on Monday October 15th 2012, 21:29
by Daniel Santos on Monday October 15th 2012, 21:36
by wireloose on Monday October 15th 2012, 17:18
bugs.winehq.org/show_bug.cgi?id=31979
by wireloose on Monday October 15th 2012, 17:24
by Daniel Santos on Monday October 15th 2012, 17:38
Is there any need for a Gentoo package? I suppose I can pop one of those together fairly quickly.
by Björn Bidar on Monday October 15th 2012, 17:42
by Björn Bidar on Monday October 15th 2012, 17:37
sudo apt-get build-dep wine
wget prdownloads.sourceforge.net/wine/wine-1.5.15.tar.bz2
wget bugs.winehq.org/attachment.cgi?id=42144 -O fix_lotro.patch
tar -xaf wine-1.5.15.tar.bz2 wine-1.5.15
cd wine-1.5.15
patch -Np1 < ../fix_lotro.patch
./configure --prefix=$HOME/.wine-ver/lotro
make && make install
# just give pylotro the wine ver by go to Tools --> Options --> tick "Advanced options" and enter the "/.wine-ver/lotro/bin/wine"
by wireloose on Monday October 15th 2012, 18:06
Thanks for the time and documentation, though.
by Björn Bidar on Monday October 15th 2012, 18:07
by wireloose on Monday October 15th 2012, 18:11
by Björn Bidar on Monday October 15th 2012, 18:13
by Daniel Santos on Monday October 15th 2012, 18:31
by Björn Bidar on Monday October 15th 2012, 18:41
by wireloose on Monday October 15th 2012, 18:47
by Björn Bidar on Monday October 15th 2012, 18:53
BTW; Add the head of the page there's an button to Wiki.
by wireloose on Monday October 15th 2012, 19:01
by Björn Bidar on Monday October 15th 2012, 19:05
by wireloose on Monday October 15th 2012, 19:25
And I didn't say you were ignorant. I said you were arrogant.
Daniel, I do appreciate your help, too, in case I forgot to say thanks earlier.
by Björn Bidar on Monday October 15th 2012, 19:33
by Daniel Santos on Monday October 15th 2012, 18:27
No! I'm just kidding! I didn't mean any of it!! It really is understandable because it's a very complicated world. However, I think they have finally made it as easy as running a simple command and letting it run for an hour or so while it downloads and installs all of the things that you need. I haven't used Ubuntu in a while, so I can't promise that's the case for 100% absolutely certain, but I think that it is.
So unless you don't want the hard drive space taken up or something, just give it a try. At the terminal type this:
sudo apt-get build-dep wine
.. then it'll ask you for your password. If that succeeds, you *should* (in theory) just be able to copy & paste every thing else into your terminal (go one line at a time however) and it will do it. The "make" part will probably take an hour at least. If you have a dual core processor, you can run "make -j2" and it'll be faster ("make -j4" if quad core, etc.)
So be adventurous!
by Björn Bidar on Monday October 15th 2012, 18:32
by wireloose on Monday October 15th 2012, 18:34
~/wine-1.5.15$ make && make install
make: *** No targets specified and no makefile found. Stop.
There is a makefile.in in the directory, and I'm not familiar with the extension, so I'm trying to read up on make documentation.
Generally I am very adventurous. The machine is used by my grandkid, hence the game, and it doesn't have a ton of disk. I knew it wouldn't have enough for the development setup. Thankfully I had another disk nearby to offload some stuff for the moment.
Thanks.
by wireloose on Monday October 15th 2012, 18:39
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
And yes, LOTRO does require the 32-bit version.
by Björn Bidar on Monday October 15th 2012, 18:44
by Marko Friedemann on Monday October 15th 2012, 19:27
I've managed to build it after fiddling around a lot and I wouldn't recommend it (it is actually missing a few features as well, so it's far from perfect).
by wireloose on Monday October 15th 2012, 19:32
by Björn Bidar on Monday October 15th 2012, 19:33
by Daniel Santos on Monday October 15th 2012, 19:42
What we really need are some wine 1.5.15 pre-builts with this patch cherry picked into it. Not everybody has the time, energy, disk space, information, patience and/or gumption to set up a build environment.
Also, I'm guessing that "apt-get build-dep wine" isn't as magical as we may have hoped for it to be!
by wireloose on Monday October 15th 2012, 19:46
ubuntuforums.org/showthread.php?t=1942266
by wireloose on Monday October 15th 2012, 19:51
This is what I got after following all the recommendations from the Ubuntu forum I linked:
Package ia32-libs-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
lib32z1-dev lib32bz2-dev
E: Package 'ia32-libs-dev' has no installation candidate
So I installed the two listed, and again the configure step fails with:
configure: error: X 32-bit development files not found. Wine will be built
without X support, which probably isn't what you want. You will need
to install 32-bit development packages of Xlib/Xfree86 at the very least.
Use the --without-x option if you really want this.
by Björn Bidar on Monday October 15th 2012, 19:47
by Daniel Santos on Monday October 15th 2012, 19:44
by Björn Bidar on Monday October 15th 2012, 20:55
here is the file:docs.google.com/open?id=0B_FQtIHEHNn8YlFlU2p4UmVOVUU
by Daniel Santos on Monday October 15th 2012, 21:17
by Björn Bidar on Monday October 15th 2012, 21:28
by Daniel Santos on Monday October 15th 2012, 21:48
And yes, the game runs fine on pretty much most of these. I have a Phenom, which isn't as fast for gaming, but it works fine. Personally, I always use -march=native, but when releasing binaries, we have to consider what CPUs other people have.
by Kevyn Dawe on Monday October 15th 2012, 22:41
by Marko Friedemann on Tuesday October 16th 2012, 3:40
Also, I followed Erich Pouech's excellent advice for the dependencies:
www.winehq.org/pipermail/wine-devel/2012-April/095364.html
Namely, after getting the main dependencies worked out (see above), I ran
CC="gcc-4.4 -m32" LDFLAGS="-m32 -L/lib32 -L/usr/lib32 -Wl,-rpath,/lib32 -Wl,-rpath,/usr/lib32" ./configure -v
As I said, it's missing a number of libs and it's far from perfect, png support is not there which means it doesn't show any textures for the mouse pointer, just its shape.
So, you see, I cannot really upload this, given it's status.
by Daniel Santos on Monday October 15th 2012, 18:09
#!/bin/bash
# Setup new WINEBASE
if [ -n "$WINEBASE" ]; then
export PATH=${WINEBASE}/bin:${PATH}
export LD_LIBRARY_PATH=$(
echo ${WINEBASE}/lib{,32,64}{,/wine} {,/usr}/lib{32,64} ${LD_LIBRARY_PATH} |
perl -pe 's/ +/:/g'
)
fi
So to use it for my local 1.5.14-wip install, I just call it like this:
WINEBASE=${HOME}/local/wine-1.5.14-wip ./setWineBase.sh
I'm still using an updated version of the old lotrolauncher.sh script (I should probably post it with my fixes for others).
by Björn Bidar on Monday October 15th 2012, 18:15
Wine Programm and enter the new wine binary patch here.
my prefix manager that use and wrote it supports it by setting WINEPATH or by -b .
by Björn Bidar on Monday October 15th 2012, 18:17
by Kootee on Thursday November 8th 2012, 0:32
by Branden on Thursday October 25th 2012, 6:36
Intel Sandy-Bridge or later CPU only
x86_64/i686 (generic, some parts like wine64 are only useble with x86_64)
by Björn Bidar on Monday October 15th 2012, 16:51
mmap() failed: Nicht genügend Hauptspeicher verfügbar
mmap() failed: Nicht genügend Hauptspeicher verfügbar
Assertion 'b' failed at pulsecore/memblock.c:454, function pa_memblock_acquire(). Aborting.
J4PWM99JR9P7: pthread_mutex_lock.c:326: __pthread_mutex_lock_full: Assertion `robust || (oldval & 0x40000000) == 0' failed.
My System: www.sysprofile.de/id123113
by Daniel Santos on Monday October 15th 2012, 17:11
by Björn Bidar on Monday October 15th 2012, 17:15
by Daniel Santos on Monday October 15th 2012, 18:19
My guess is that a stupid value is being passed to mmap for some reason and the return value isn't being checked. It's only when control reaches void* pa_memblock_acquire(pa_memblock *b) that an assert is performed and we discover that the parameter b is NULL. I would also guess that the assert from __pthread_mutex_lock_full is due to the failed assert in pa_memblock_acquire aborting the thread.
This may be worthy of a new bug report.
by Björn Bidar on Monday October 15th 2012, 18:26
This happens about every time, it's just faster when using OpenGL as render.
by Daniel Santos on Monday October 15th 2012, 19:38
dev.gentoo.org/~tetromino/distfiles/wine/winepulse-patches-1.5.15.tar.bz2
by Björn Bidar on Monday October 15th 2012, 19:41
by Daniel Santos on Monday October 15th 2012, 16:15
So note to maintainers, please use the "Update x.x.x" scheme for future versions, unless they change the damn thing again. Thanks!
by Björn Bidar on Monday October 15th 2012, 11:52
by Daniel Santos on Monday October 15th 2012, 12:10
by HuSSaR on Monday October 15th 2012, 14:41
--- wine-1.5.10.orig/dlls/user32/winpos.c 2012-07-31 21:08:12.000000000 +0200
+++ wine-1.5.10/dlls/user32/winpos.c 2012-09-01 14:43:47.000000000 +0200
@@ -251,8 +251,7 @@ BOOL WINAPI ClientToScreen( HWND hwnd, L
*/
BOOL WINAPI ScreenToClient( HWND hwnd, LPPOINT lppnt )
{
- MapWindowPoints( 0, hwnd, lppnt, 1 );
- return TRUE;
+ return MapWindowPoints( 0, hwnd, lppnt, 1 ) != 0;
}
With this patch bullroarer worked on beta. Haven't updated it yet so don't know if it still works
by Björn Bidar on Monday October 15th 2012, 14:44
by Marko Friedemann on Monday October 15th 2012, 15:03
by Björn Bidar on Monday October 15th 2012, 15:09
diff -Naur wine-1.5.15.orig/dlls/user32/winpos.c wine-1.5.15/dlls/user32/winpos.c
--- wine-1.5.15.orig/dlls/user32/winpos.c 2012-10-12 20:14:46.000000000 +0200
+++ wine-1.5.15/dlls/user32/winpos.c 2012-10-15 21:58:33.548855016 +0200
@@ -250,8 +250,7 @@
*/
BOOL WINAPI ScreenToClient( HWND hwnd, LPPOINT lppnt )
{
- MapWindowPoints( 0, hwnd, lppnt, 1 );
- return TRUE;
+ return MapWindowPoints( 0, hwnd, lppnt, 1 ) != 0;
}
by Björn Bidar on Monday October 15th 2012, 15:18
by Daniel Santos on Monday October 15th 2012, 15:19
by Eduard on Monday October 15th 2012, 15:28
by Björn Bidar on Monday October 15th 2012, 15:29
by William Magill on Monday October 15th 2012, 16:07
Hopefully they may find a way to do it.
However, the big problem will be the fact that Crossover is still at 1.4.1 -- so it may be a while.
by HuSSaR on Monday October 15th 2012, 16:15
by Daniel Santos on Monday October 15th 2012, 16:20
by William Magill on Monday October 15th 2012, 8:29
BTW, Riders of Rohan is NOT Volume 4, but still Volume III.
Volume III Book 7, 8 9, to be exact.
by Björn Bidar on Monday October 15th 2012, 8:38
by Daniel Santos on Monday October 15th 2012, 11:57
by Björn Bidar on Monday October 15th 2012, 12:11