Lord of the Rings Online

Why make a new app version for every minor update? Id woud be better if we just make a version for every major update or for every new addon.

The current version of LOTRO is -
Update 12: Helm's Deep

Just adding this comment, with a couple of things I've encountered, in hopes it helps someone else with this problem. Mods, please feel free to trim this post if you feel the need. It's kinda late for me, and thus I ramble, but I wanted to put this up while the drive to do so was still present :)

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?).

Alan can correct me if I'm wrong here, but I believe that there are TWO separate versions of PyLotRO existent.

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

BTW, my server "mcgillsoceity.org" is currently in the shop getting its disk drive replaced.
Hopefully I'll have it back on line later today or tomorrow (11/21)

One bizarre thing I keep running into is setting the WINESERVER environment variable doesn't seem to do anything. When I run pylotro and try to log into the game, I get the typical error you get when wine is a different version than wineserver:

"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.

Set Wine in to the wine version and kill your old wineserver before running.

Okay, so I'm trying to figure out how to get it to work on mine. I was experiencing the E13 AND E02 errors. Before I tried anything else, I went into Tools > Options and set the game directory to "C:/Program Files (x86)/PyLotRO" and that fixed the E13 error - but I'm still getting the E02. When I go to the settings wizard and click "Find Games," nothing happens. Does anyone know what I need to be doing differently?

I should mention that I tried putting a symlink of the PyLotRO folder from Program Files (x86) into Program Files, and the same thing is still happening.

I wound up selling my house and moving the 1st so I missed the announcement.

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).

I set WINEDEBUG to "" to get some output to report a bug (see some comments below), but instead that the game runs it freazes short after login with my character.
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?

First, I don't know if it matters, but since I switched the rendering engine from DX9 to OpenGL I am getting the freezes and the errors way much less frequent.

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

I think its related in some way but I don't know it in detail.
Do you use Pulseaudio in OpenAL? Do you get similar errors i posted in the comment 'Out of Memory'

Nope, no PulseAudio (gave it up a long time ago as it always gave me problems with various apps on both Kubuntu and Gentoo) just ALSA and not Out of Memory errors.

I've applied the patch and added the path in "wine program:" as

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?

Sorry for multi-posting... connection error.

I have the same problem

I've applied the patch and added the path in "wine program:" as

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?

I've applied the patch and added the path in "wine program:" as

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?

Have you found any soltion?

Ok, it was simple, just you need to use from the menu of PyLotro:
Tools -> Patch
After he has ended patching all worked like a harm.

Tried it, dosen't seem to help, I get no files for updating. error still prevails.

So it is surely not problem of "err:ole:CoUninitialize Mismatched CoUninitialize" - because I get it too, and game is working without any problems.
If you want to try use my compiled wine (32 bit, compiled in Ubuntu 12.04): www.dropbox.com/s/jdmeq38b7cve7e6/wine-lotro.7z

Thanks, I'll try it and see.

No, It dosen't seem to work, still getting the error (CoUninitialize Mismatched).

Hi all,
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?

Please add more wine output, i think its related to something I posted earlyer.

The problem is that I don't get any output beside "error:9: write: Bad file descriptor" and sometime not even that.

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>

Is anyone else getting a blank box when they click on the LOTRO store? I can see the background of the store, but no actual content loads. I've been getting that since before the release of Rohan, and no-one else seems to be mentioning it, so I'm guessing it's just me. I tried a new wineprefix (copied the install folder over though) and it still seems to be happening. It's not exactly game-stopping at the moment, but it's going to cause issues down the line at some point.

It don't have the issue, but it may be caused by your wine_gecko installation?

That was my first thought aswell. However using same version of wine to run the wine version of Internet Explorer seemed to work fine, and a re-install of the wine-gecko package didn't help.

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.

The store works for me. Ubuntu 12.04 under play on Linux with fix from above and opengl.

This appears to be related to proxy changes. The client seems to query proxy autoconfig, which fails. Setting a proxy manually in the ini file doesn't seem to fix it either.

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.

Yeah, having the problem since yesterday also.

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.

It looks like the 10/24 "changes" had to do with Turbine's internal network. (DDO folks are reporting issues also.)

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.

I should Add, I'm running the MacPorts "Patched" CrossOver Wine version (1.4.1) on OS X 10.8.2

Well, there was no patch yesterday, just maintenance. Maybe there are two code-paths in the client and the server config triggers one of them. Steelsnake, what patch are you referring to in the lotro forum? The one for WinHttpProxyGetUrl that was posted to the ml in november?

I was getting a blank white box (no store background as others have posted about)

"winetricks vcrun2008 corefonts" fixed it for me.

This page is considered out of date since December 17th, 2012.

The following instructions apply to Snow Leopard, Lion and Mountain Lion, and assume you have a pre-existing Bottle from CrossOver with LOTRO installed. Yes, you will need to use the Terminal window.

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.)

Is there a way to do this for people who don't use crossover (just wine)?

Its for everyone cause you build wine by your self.

It works! I don't have CrossOver installed on my mac, so the directory
/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).

WINE is WINE, so if you normally use plain wine, just treat it like your regular WINE installation.

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.

Has someone the issue that sometimes lotro gets minimized to a small box
in the virtual desktop?

Here is a screen what is left when loro gets minimized:
imageshack.us/photo/my-images/526/smallbox.png/

I've had odd resizing behavior until I unchecked "Allow the window manager to decorate the windows" in winecfg. I still have "Allow the window manager to control the windows" checked however.

This was in an virtual desktop so the issue is elsewhere.

Someone tested the OpenGL render and how it has improved?

I used playonlinux with your wine build last night. I can confirm it does work, I didn't notice if the text issue was fixed or not. Some of my floating text from exp did seem too large and appeared at my feet. I'll try and make some screen shots tonight.

i checked and the text overlay issue before riders of rohan under opengl do not appear now. i'm only running around bree land as a lore-master and things seem normal except for the new graphic adds like a green arrow above what i'm targeting and red arrow for an add/link for a 2nd target attacking me.

>"new graphic adds like a green arrow above what i'm targeting and red arrow for an add/link for a 2nd target attacking me."

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."

I at least cannot play with the OpenGL renderer anymore.
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.

I uploaded my wine build, that I build system* with -march=native and -mtune=native with an i7 2600k so it wont run on old machines.

here is the file:docs.google.com/open?id=0B_FQtIHEHNn8YlFlU2p4UmVOVUU

*(www.sysprofile.de/id123113)

Here's a patched package for Arch Linux x86_64. It's compiled with -march=x86-64 -mtune=generic, so it should work with any CPU.

docs.google.com/open?id=0B_dkcsYE5yPfVTFUV0w5RnduY0U

Thanks guys!

Hey Björn,

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. :)

So I have been using my default wine for LOTRO with no problem, until RoR of course. Reading the bug report and the forum, it sounds like the patch fixes the issue. Now, I have gotten 1.5.15 from git, and applied the patch and compiled it. However, I have lots of programs which run great on the unpatched wine, and don't want to over write it with this just to play LOTRO.

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.

give the application absolut path fo example my prefix for the patched wine for lotro is: "/home/bidar/.wine-ver/lotro"
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.

Yeah, the reason that doesn't work is that the wine launcher is a pretty small part of wine and it will still pick up all of the libs from /usr. Alternately, you can use my setWineBase.sh script posted below prior to launching (I don't use pylotro), but if Björn's solution works for you it is better to use that.

Thank. That fixed THAT issue. So, I would like to tentatively report success. I used my 64 bit patched wine and got a number of new errors. I also saw in the bug report that the LOTRO client is actually 32 bit, so I built a 32 bit one in my chroot (I have experience with it from LoL) and instead of a list of errors I got the start up screen and then the 'Client out of date' error. I am currently patching and will report back if it does work.

I got the 'cant patch' error too, after this the game should run flawless.

Oh yeah! I forgot to mention that I had that too. I had to interrupt the patch, and start over. Apparently, one run of the patcher wasn't done letting go of the patchclient.dll before the next one tried to replace it or some such (because it was updating the patch dll).

I'm running Ubuntu 12.04.1 LTS w/ WINE 1.5.15. I don't have a dev environment. Wondering if anyone out there is building a patched version of 1.5.15 with this patch included? (Same one discussed just previously.)
bugs.winehq.org/show_bug.cgi?id=31979

I should say that I also posted on the Ubuntu forums asking about how to get the patch incorporated.

Hey, actually my gf has an Ubuntu machine, but it hasn't been updated in a long time. If she doesn't mind me running the update (and discovering what breaks), then maybe I can try to put one together. I suppose I should build a debian one as well (my laptop is Debian).

Is there any need for a Gentoo package? I suppose I can pop one of those together fairly quickly.

Cause its better to have seperate versions from the default installed for application specific patched wine version, they are no extra packages needed, even if you build a package it should be not hard ( in arch its easy, just get the stock wine pkgbuild and add the patch to it and build it).

Just download the depency to build with apt-get build-dep wine, download the sources patch it, create an folder for thw custom wine version in your $HOME folder (for example .wine-ver) run configure with the prefix to it, do make and make install and give pylotro the wine binary:

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"

I don't have a dev env so this would fail at the configure and make stage. I'll just have to wait till this filters out to the mainstream. Maybe the Ubuntu community will push it through.

Thanks for the time and documentation, though.

Are you to dumb to download the soutces via apt-get build-dep wine?

That's pretty rude, dude. I don't have a dev environment. That means no compilers, no dev libraries, either 32- or 64-bit, etc. In other words, no way to deal with the source code once it's downloaded. It will be a while before I can set up a dev system.

apt-get build-dep wine gets all packages that you need to build (eg. compilers and such).

Oh, seriously Björn, please don't put down others.

I wasn't meant be rude, but he just asked, we helped, he just played dumb, so that we do it for him. He coud get some informations in the wiki how to do it.

And that's where you're wrong. I didn't *play* dumb, I actually did not understand. And I did not know there was a wiki, but I was more than willing to look in other places, provided that someone would point me there. I don't appreciate the accusations of deceit.

You played cause don't tryed to get informations from other sources (google and such).

BTW; Add the head of the page there's an button to Wiki.

And how do you think I found WINEhq in the first place? Note that my accounts were created today. I googled, this looked like the place to start finding info, created accounts, reported the bug, shared logs, and started asking questions. I did a lot of looking on dozens of sites today besides here. You have no idea what I did over the course of my day, you are just defending your poor manners. You're just arrogant.

Im don't ignorant I just help people when their doing theit part of the things they wan't to help ( it's the word help it self: its helping and not doing the job for the one that needs help).

You started this off by helping, and I appreciate *that.* I didn't realize that the entire development environment would be loaded in one command. In fact, it wasn't, it didn't load all dependencies as you had stated in your own message. I knew I didn't have a full dev env and I knew I didn't have the disk for it. So I originally just came here looking for a binary. (Ask Daniel Santos - he's the one on the Bugzilla reporting side who directed me here to do just that.)

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.

This was what i meant i wrote the wrong words sorry (english isn't my native language).

Yeah, that is pretty rude *scolds Björn*, but his point is that it's not that f*cking hard you retard, what the f*ck is wrong with you!?

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!

I posted all what he needs to do, he just needs to do copy, paste and set settings in pylotro.

Yes, I used to do development work in Unix and Linux, but that was mostly 2 decades ago. I didn't know what the build-dep line was about. But I tried it and it took a while, and I had to empty some disk space and start over twice. Now it's done. Except for the last line. This is what I get:
~/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.

Okay. No MAKEFILE was made. The error seems to actually be that the commands given did not install the appropriate 32-bit development libraries:

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.

You need to install the lib32 -dev packages to build it.

It's actually not quite so easy to get this wine build to work on a 64bit ubuntu 12.04, because the multi-arch stuff is... uhm... broken in some ways.

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).

Yeah. After researching some more, I got lib32 installed, and start the compiles, and then it complains about missing X 32-bit development files. More googling to do.

you need to install the -dev or -devel packages from them.

See Björn? It's not always as easy as we may think it is! :)

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!

Yeah, and there is discussion on the Ubuntu forums that the xlib devs for 32-bit arch on 64-bit systems don't install correctly. I've just completed all the "fixes" for that issue, and the configure command still complains about missing Xlib/Xfree86 packages. So there are more that didn't get loaded with the commands listed here:

ubuntuforums.org/showthread.php?t=1942266

*note: this is not a complaint, just sharing what I'm finding so far in case there is any interest.*

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.

Yes cause he wants to build bin-32 packages on an x86_64 system.

ooh! did you build it the Ubuntu way or some other way? If Ubuntu, can you post the binaries somewhere pretty please & thank you!? :)

I can upload my, build on my system(www.sysprofile.de/id123113) with -march=native and -mtune=native with an i7 2600k so it wont run on old machines.

here is the file:docs.google.com/open?id=0B_FQtIHEHNn8YlFlU2p4UmVOVUU

Thanks so much! Do you think you can build one with "-march=nocona -mtune=generic" for those who have an incompatible CPU?

If this happens I can, since this game requires new hardware it shoud bug on older hardware.

It will run just fine on many other CPUs that don't have all of the instruction sets that the i7 2600k, or more specifically, the Sandy Bridge architecture. So your executable probably will use AVX instructions, which don't exist on Nehalem or Westmere, which is only one or two years older. Also, there are other manufactures. AMD Barcelonas don't have SSE4, but they do have SSE4.1, that many Intel CPUs lack, etc.

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.

This worked for me - thanks so much! I'm running an Intel Core 2 Duo E7500 @ 2.93 GHz if that's any use to anyone.

I've built it the 'Debian Unstable'-way from wiki.winehq.org/WineOn64bit.

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.

Cool Björn, I didn't know ptylotro let you do that. I've always used a script that I named setWineBase.sh:

#!/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).

Do what i said go to Tools --> Options --> tick "Advanced Options" -->
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 .

I meant "path" not patch.

Will this patch work also in the new 1.5.16 version?

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.

Intel Sandy-Bridge or later CPU only
x86_64/i686 (generic, some parts like wine64 are only useble with x86_64)

Anyone getting the same error:
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

Very nice sysprofile link! What version of wine though? Also, at what point are you getting this error please?

Im using wine-1.5.15 with the patch from: Bug #31979, it hapens when playing a while and using OpenGL as game render.

hmm, this is occurring in pulse audio you know. I've been getting some odd blips in audio playback lately I've noticed, so could be a wine bug. I'm curious what would happen if you change wine to use alsa as default (or perhaps in-game if you can get that far, maybe you can even change that in the .ini).

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.

Wine don't uses pulseaudio (this version had just the lotro fix patch), the game uses pulse audio through OpenAL.

This happens about every time, it's just faster when using OpenGL as render.

Well, I don't know, but I just noticed that the Gentoo distro of wine 1.5.15 includes a massive patch set for pulse audio, I'm not sure what it does yet:

dev.gentoo.org/~tetromino/distfiles/wine/winepulse-patches-1.5.15.tar.bz2

Yes and arch don't inclues any patches to wine, so applications can only use pulseaudio inderectly via OpenAL,

OK guys, this isn't any particular maintainer's fault, I'm changing the version description based upon the scheme that Turbine is using *at the moment*. Hopefully, they still stick with this scheme and we wont have to change it again. I think we should leave past versions named the way they are, since that was the versioning scheme they were using at that time.

So note to maintainers, please use the "Update x.x.x" scheme for future versions, unless they change the damn thing again. Thanks!

Anyone got sucess towards getting the game running?

no, but I've submitted a bug for it (see Known Bugs above)

diff -rpuN wine-1.5.10.orig/dlls/user32/winpos.c wine-1.5.10/dlls/user32/winpos.c
--- 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

Thanks you may at it to the bug report?

Hey, this looks good, because the details of the crash are indicating a problem there. It seems to me as if the game tried to call this way too early.

Patch for lastest wine:
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;
}

Thanks with my updated atch it fixed it for me.

Thank you, it works here too. Who wrote this patch please?

Is there a way to apply this patch to crossover on mac? If yes, how would one do that?

No you need to apply the patch to the sources and build them.

I've passed the info along to Crossover.
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.

It was from an user on the bullroarer forums on lotro, they are wiped so don't really know who it was, Sorry.

Wow, that is highly unfortunate. I hope they come forward. That's how us geeks boost our ohloh profile. :)

There seems to be two New LOTRO pages in the past 24 hours.

BTW, Riders of Rohan is NOT Volume 4, but still Volume III.
Volume III Book 7, 8 9, to be exact.

Fixed the version name, don't, know why some created another version for RoR.

I deleted it.

Thanks.