You are not logged in.

Applications: [GameMaster: OPEN] | [Volunteer Testers: OPEN]


This forum will be permanently shut down on Friday 13.07.2018
Please copy or save all important information from old forum before they will be deactivated
We have moved to new board. https://forum.runesofmagic.gameforge.com/Come join us.

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

1

Sunday, May 15th 2011, 2:09pm

[Guide] Running RoM on Linux

RoM on Linux (aka Peryl's Adventures in Linuxland)

Update:
The guide has been completely re-written and updated for Wine version 1.7.15 and Runes of Magic Chapter VI (6.0.7 as of this writing). As I now run ArchLinux instead of Ubuntu or variant, some of the Ubuntu packages to be installed may be a little off. If you have trouble, check with Ubuntu on how/where to install the correct package.

The guide to compiling an old version of Wine should no longer be needed, But it is in post #29 in this thread if you still want to use it.

You may also wish to try installing and running Wine via PlayOnLinux. zedock posted instructions on using PlayOnLinux here: [Guide] Running RoM on Linux though I don't know how up to date they are.

The section on installing on VMware has been removed as the game runs fine via Wine.


Introduction
This is a guide on installing and running Runes of Magic on Linux. Originally written for Ubuntu and variants, as I now run ArchLinux I will try to keep instructions for both distros.

I suggest reading through the whole guide before attempting anything. First because this will allow you to decide what method you want to try. Second, you'll have an idea of what's involved and what issues to expect.


The "Test" Machine
Since we'll be looking at running RoM via Wine, performance comes into play so it may be of interest to take note of what I used to test this on.

AMD Phenom II X2 Black Edition 3.2 GHz (with 2 extra cores unlocked), 16 GB of memory, Dual widescreen LCD monitors, ArchLinux 64 bit OS.


Download The RoM Client
To install the game, it is best to use the manual install files. See this post for download links.

Put the files in a convenient location for use later.


A Little Wine With Your RoM
The following instructions should all be performed at a command terminal. This makes it easier to give precise instructions, and you can simply copy the required commands straight from the post to avoid possible errors. Make sure you use the correct commands for your distro since there are instructions for both Ubuntu and ArchLinux.

Before we start, check if you already have Wine on your system. Do this by getting the Wine version using the following command in a command terminal:

Source code

1
wine --version

If the command fails, then you do not have Wine installed. If it works, check the version number returned. If it is less than version 1.6, you will likely need to update it (even numbered Wine versions are stable releases, while odd numbered versions are the development branch, so a Wine version of 1.6.x should more fine).

To install Wine on ArchLinux, simply do

Source code

1
sudo pacman -S wine


To install Wine 1.7 on Ubuntu (and variants), you will first need to install the PPA for it. The following three lines will install Wine 1.7:

Source code

1
2
3
sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt-get install wine1.7


For full instructions or installing on other Linux distros see http://www.winehq.org/download/.

Once Wine is installed, we will also need to install winetricks in order to get Wine properly setup for Runes of Magic.

On ArchLinux, winetricks can be installed straight from the community repos with

Source code

1
sudo pacman -S winetricks


On Ubuntu, winetricks should be installed as a recommended package to Wine so nothing really to do.

For other distros, see the the instructions at http://wiki.winehq.org/winetricks.


Setting a Wine Prefix
Now that Wine and winetricks are installed, we can get on with setting things up for Runes of Magic. I recommend installing Runes of Magic in a seperate Wine prefix.

To create a Wine prefix all we really need to do is tell Wine where to put it and Wine will create the prefix. However, we should first make a couple of decisions. First we need to decide what version of Windows we want Wine to emulate, and we must decide if the prefix will be a 32 bit or 64 bit one. This last is rather important since you cannot convert a prefix from one to the other. So if you make a mistake, then you will need to re-create the entire prefix. Note that if you are runniung a 32 bit version of Linux, you won't have the option to create a 64 bit prefix, so that decision is made for you.

To actually make the prefix, use:

Source code

1
WINEPREFIX=~/.romwine winecfg

This will create a wine prefix in the hidden folder .romwine inside your home folder. The prefix will be 64 bit on a 64 bit Linux, 32 bit otherwise.

To create a 32 bit prefix on 64 bit Linux systems, the command is almost the same:

Source code

1
WINEPREFIX=~/.romwine WINEARCH=win32 winecfg

That's it. Adding that one option will make a 32 bit wine prefix.
The remainder of this guide will assume that you are using a 64 bit Wine prefix. If not, just make sure to add the WINEARCH=win32 part to the commands.

Once the prefix is created, the Wine configuration panel will open. In the Applications tab, you can set the version of Windows that Wine will emulate. I've had success setting this to Windows XP and Windows 7 so either will do. You may also want to set the Automatically Capture The Mouse setting in the Graphics tab. Click apply then close the dialog.

Now to install the things RoM will need in order to run properly. Namely .NET 2.0, a version of IE, the Visual C runtime, and wininet. We should also install some basic Windows fonts. We do this via winetricks. Enter the following command:

Source code

1
WINEPREFIX=~/.romwine winetricks corefonts vcrun2005 ie7 wininet dotnet20


Note: When winetricks installs ie7, it may give an error saying that it internet explorer doesn't run on your operating system. You may ignore this.

If you get a wine error message complaining about missing libncurses.so.5 you will need to install libncurses.

On ArchLinux this can be done with

Source code

1
sudo pacman -S ncurses

Though you might need to install the 32 bit version for 64 bit OSes so enable the multi-architecture repositories (see the Arch Wiki on doing this) and use

Source code

1
sudo pacman -S lib32-ncurses


On Ubuntu, use

Source code

1
sudo apt-get install libncurses5

You again may need to also enable multiarch support. See the Ubuntu documentation on doing this.




Installing the Game
Now that Wine is setup properly, we are ready to start installing the game. Go to the folder where you downloaded the RoM install files and run the installer with (this assumes version 6.0.6.2685, change the name as appropriate for the version you've downloaded).

Source code

1
WINEPREFIX=~/.romwine wine ROMSetup_6.0.6.2685.exe





Once the game is installed, have it launch the game directly so that it updates to the latest patch.



After it updates, select the region you want, also set the initial configuration. Note that the launcher may not see all video modes, so set everything as close to what you want as you can, then we'll edit the initial config file manually later. You can run the game now to try it out, but we have one more thing to do so after trying it out, exit the game.

If you need to configure RoM's initial configuration to set the screen resolution, navigate to the game's install folder (inside the Wine prefix). Use the following commands to get to the correct folder (we do this in two parts because on 64 bit Wine prefixes, the game installs to Program Files (x86) but the parenthesis in the name are treated in a special way on Linux.

Source code

1
2
cd ~/.romwine
cd 'drive_c/Program Files (x86)/Runes of Magic'

note the use of single quotes in the second line here.

Now you can edit the file client.config.ini with either kate (KDE) or gedit (Gnome) or other text editor of your choice. To use kate do

Source code

1
kate client.config.ini

Change the width and height for windowed and/or fullscreen modes here and save the file (this affects the startup resolution only, this can always be changed again later in game).


Creating a Startup Script
As a final step, we'll create a startup script with which to launch the game. This is needed because the desktop icon that is created tends to not work properly from Linux (Wine does try, but I've never gotten it to work with RoM).

So create a file called StartRoM somewhere (your home directory should be a good place) and add the following:

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
#!/bin/bash

# Runes of Magic startup script for Linux

# Put ourselves in the correct folder before calling Wine
# we first go to the prefix folder then the game folder. This is done
# because of the parenthesis in the folder name 
cd ~/.romwine
cd 'drive_c/Program Files (x86)/Runes of Magic'

# Start Runes of Magic using Wine
# Sets the wine prefix to be used and disables all wine debug messages
WINEPREFIX=~/.romwine WINEDEBUG=-all wine "Runes of Magic.exe"

Note that the above assumes the Wine prefix is 64 bit. In 32 bit Wine prefixes, the game installs to Program Files, not Porgram Files (x86). Change as appropriate.

Save the file then change the permissions of the file to be executable with

Source code

1
chmod a+x StartRoM


Finally, add a new launcher shortcut on your desktop to start this script.

You can now use this new shortcut to start the game. Enjoy!
2013... The year from hell....

This post has been edited 3 times, last edit by "Peryl" (Apr 20th 2014, 8:08pm) with the following reason: Adding info for Intel integrated graphics


DSDrennen2

Beginner

Posts: 16

Location: Runes of Magic: Mage Academy for the Talented

Occupation: Programmer/Network Admin

  • Send private message

2

Sunday, May 15th 2011, 3:17pm

2 things.
1: Thank you so much. Now I can run this on either boot, and you have no idea how happy this makes me.
2: Love dem backgrounds. >=D

DSDrennen2

Beginner

Posts: 16

Location: Runes of Magic: Mage Academy for the Talented

Occupation: Programmer/Network Admin

  • Send private message

3

Sunday, May 15th 2011, 5:50pm

This should really be stickied in the Guides section.
Come on, GM's. You know i am right!

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

4

Monday, May 16th 2011, 10:37pm

Woohoo! I made the stickies! Thanks to the FMs/CMs/GMs for that.


Anyway, here some extra info on configuring Wine and/or Linux:


Explorer-Like Interface for Wine
There is a program installed with Wine called Winefile. This gives you a graphical vie of your Wine folders and you can run executables from it as well. To run it, open a console or create a shortcut and enter the command

Source code

1
winefile
That's it. Now run it and an explorer like window will appear. Clicking on the C: button will take you to your Wine C drive and from there you can navigate to the Runes of Magic game folder and run the game by double clicking the Runes of Magic.exe file. Just another way to run the game in case you prefer this method. However, if you do run the game through this, you'll need to then exit Winefile from the file menu to close it, but once the game has started (even if only the updater is showing) it can be closed.

Virtual Desktops
One issue that arises with the way I described the Wine configuration is that trying to go fullscreen may still display a window title bar at the top of the screen. Further, if like me you have a multi-monitor setup, RoM will want to use both monitors for fullscreen mode.


The above screenshot was taken in fullscreen mode on my machine. Notice how the action bars don't even hit the right side of the screen. Also, imagine a break exactly where my character is standing. This is where the sides of the monitors are. Looks cool, but not very good for playing.

To get around this, you can set a virtual desktop in your Wine configuration to encompass the entire screen, then RoM will be able to properly run fullscreen. You can open the Wine configuration by running winecfg either via the console, or from a menu icon (if one is installed). Under the graphics tab, select the Virtual Desktop checkbox, then entire the size of your screen as the size of the virtual desktop. Now RoM will only see and use this desktop size, even in fullscreen mode.


Audio Issues/Random Lockups
(Obligatory disclaimer: I must admit that I'm a little biased against pulseaudio so you may wish to take the following with a grain of salt. Having said this however, all my experiences with pulseaudio have been bad. Friends of mine have also had many crashes/run-away programs that were directly caused by pulseaudio, so there is precendent for my bias.)

If you are experiencing audio problems, random run-away programs, or random crashes during gameplay (assuming it isn't the game itself that is crashing of course). consider getting rid of pulseaudio.

Even when you don't use pulseaudio as the main driver, if it is active it still inserts itself into the audio mixing chain and therefore can cause problems.

Unfortunately, pulseaudio is distributed as the default audio back-end on Ubuntu distros and can be a pain to get rid of. For other flavors of Ubuntu, this may not be the case and so can be removed via the package manager.


For Ubuntu
Help page for getting rid of pulseaudio:
http://ubuntuforums.org/showthread.php?t=1313253&page=15
see the second post on that page for a link to the a PPA (non-standard) to remove pulseaudio.


For kubuntu (Xubuntu as well?)
Simply open your package manager, look for and un-install the pulseaudio package. This will remove a bunch of other pulseaudio related things, as well as the ubuntu-desktop package. This last will remove the normal ubuntu desktop but as you are likely using KDE, this isn't a problem. If you still want to keep the old ubuntu desktop, then follow the instructions for the Ubuntu distro above.


For Mint
Try here:
http://community.linuxmint.com/tutorial/view/439
I'm not sure how recent/relevant this is as I don't run Mint.


Other Linux distros
See the support forums for the specific Linux distro you have.
2013... The year from hell....

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

5

Tuesday, May 17th 2011, 5:41pm

** Update **

Just wanted to give a quick mention that the game updated to 3.0.11 perfectly fine using the Wine install.

Also, I compiled the latest source release of Wine (1.3.20) and using the virtual desktop and the new Mouse Grab feature in Wine, the mouse issues with Wine are now completely gone! So either wait for the binary release of Wine 1.3.20 or bug me for instructions on compiling it from source. (I'd slap up another post, but I still have a couple of small things to figure out for a nice clean build guide).
2013... The year from hell....

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

6

Wednesday, May 18th 2011, 4:23pm

Another Update!

The binary version of Wine 1.3.20 has now made it into the Ubuntu PPA packages for Wine. I've updated the guide to reflect this.

Since Wine 1.3.20 fixes the mouse problem, this is now the preferred method for running RoM under Linux.
2013... The year from hell....

Posts: 1

Location: New York , Upsate US.

  • Send private message

7

Monday, May 23rd 2011, 4:06am

Thanks for the updated information, =). Haven't tried what you said yet.. Was just going to open a new question, but came across this.. RoM is running on my Wine, but kinda laggy, but that's usual on Wine.. It crashes quite often, maybe this tweak will help some. @Peryl If I could make a suggestion, if you like the command line, I honestly think you'll like Arch Linux, I love it, =). IMHO, it runs so much more better than (K)Ubuntu, but, it's all console in the beginning, but installs less than 10 minutes, if you have a dual core CPU, I should add..

My Details:

OS: Arch Linux;
Wine Version: 1.3.20; //Note: it's the latest of the wine series..
CPU: Intel Duo core 2;
Internet: 5 MB/Sec down : 1 MB/Second up;
Monitor: 23" Gateway hooked up to HDMI Input;
RAM: 4 gigs;

Anyway, thanks again, =).

8

Sunday, June 5th 2011, 9:57pm

Mouse bug in Wine 1.3.21

I am using Ubuntu 11.04, and I'm new to Linux. I upgraded Wine to version 1.3.21 using terminal commands, however this update screwed up the mouse in RoM. Every time I try to adjust the camera by holding the mouse buttons, the mouse freezes and becomes immovable.:( Everything else seems to work fine. I have the virtual desktop and mouse grab options enabled in my Wine Configuration, so I doubt thats the problem. I had RoM working almost perfectly in version 1.3.20, but sadly this mouse bug makes it very difficult to play. Do you have any suggestions on how to fix this or how to revert back to 1.3.20?

EDIT: I found a way to downgrade wine versions using the Synaptic Package Manager. However the only available versions to downgrade to are 1.3.21 (which I already have installed) and 1.3.15 (which does not have the mouse grab option). I read some other support forums and their solutions require deletion of your current Wine version and then installing the specific version you want. If I completely reinstall Wine like the other guides say, will I have to reinstall RoM and other programs as well? If inescapably so, is it possible for me to get version 1.3.20 and not 1.3.21 without a total re-installation RoM and Wine?

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

9

Monday, June 6th 2011, 4:53am

Quoted from "JedSled;425162"

... I upgraded Wine to version 1.3.21 using terminal commands, however this update screwed up the mouse in RoM. Every time I try to adjust the camera by holding the mouse buttons, the mouse freezes and becomes immovable.:( Everything else seems to work fine. I have the virtual desktop and mouse grab options enabled in my Wine Configuration, so I doubt thats the problem. ...

I'm at a loss as to what may be causing this. I just tried updating my Wine to version 1.3.21 and things are working fine for me. All I can think is that something got buggered in the update. Try uninstalling then re-installing Wine using the Synaptic Package Manager. All I can think of off the top of my head.

Quoted from "JedSled;425162"

EDIT: I found a way to downgrade wine versions using the Synaptic Package Manager. However the only available versions to downgrade to are 1.3.21 (which I already have installed) and 1.3.15 (which does not have the mouse grab option). I read some other support forums and their solutions require deletion of your current Wine version and then installing the specific version you want. If I completely reinstall Wine like the other guides say, will I have to reinstall RoM and other programs as well? If inescapably so, is it possible for me to get version 1.3.20 and not 1.3.21 without a total re-installation RoM and Wine?

One of the problems with using PPA packages is that they update fairly often and don't have previous versions since they are proposed packages as opposed to full releases. The only way I know that would get you back to version 1.3.20 would be to download the source and recompile it yourself (not for the faint of heart).

Edit: Forgot to mention, No you don't need to re-install RoM if you re-install Wine. So removing Wine then re-installing it or a newer/older version will work fine.

Edit 2: You Might still have the 1.3.20 .deb file still in your APT cache. To check try this from a command line:

Source code

1
2
cd /var/cache/apt/archives
ls

If it is present, you should see the file wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb (yes, those are tildes ('~') in the filename).

If you have it, you can copy it somewhere then try this to install it (after uninstalling any other Wine package currently installed)

Source code

1
sudo dpkg -i wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb

Unfortunately, this will manually install 1.3.20 and so will not get flagged for updates. Also, if your package manager has auto-remove turned on (or similar feature) it may want to uninstall it every time you update, so check for that as well.
2013... The year from hell....

10

Monday, June 6th 2011, 7:30pm

There is no easy way out...

(Attempt 1): No improvement
I used the Synaptic Package Manager to remove Wine 1.3 by selecting it and going to: Package -> Mark for complete removal, and then clicking apply. I reinstalled it using the terminal commands you listed in the guide to see if updating it with the terminal caused the problem. However, the mouse problem was still constant.

(Attempt 2): Worsened Conditions
I removed Wine 1.3 using the Synaptic Package Manager again, rather than using terminal commands to install it, I used the install option provided by the package manager (Package -> Mark for install, Apply). This solved nothing and I no longer had sound in programs running in Wine. I opened Wine configuration and went to the Audio tab, I selected different drivers and tested them. However, each time I selected a new driver and clicked the Test Sound button, I received an error message that read, "Audio test failed!" Computers suck. :mad:

(Attempt 3): No improvement, but sound was restored.
Once again, I went to the Synaptic Package Manager and selected Wine 1.3. This time, I reinstalled it by going to: Package -> Mark for Reinstallation and clicked apply. I opened Wine Configuration again and went to audio. This time, I selected the ALSA driver and tested it. The sound works again in my Wine Programs. However, This mouse bug in RoM was still present.

(Further Attempts): No improvement
Not knowing what to do next, I checked winehq.org for information about Runes of Magic. In the comments section several people reported similar issues with the mouse, one particular comment had a link to an image showing the mouse bug while using Wine 1.3.21 (which is identical to mine). Heres the link: http://img69.imageshack.us/img69/6840/cut1.png.

I opened the package manager again and selected Wine 1.3, this time I tried another approach: Package -> Force Version (as I stated before only 2 options are available for this, versions 1.3.21 and 1.3.15) and I selected 1.3.15. Version 1.3.15 runs slower than 1.3.20 and 1.3.21 and has problems with the mouse as well. The mouse has only a limited range of movement and I cannot zoom in on my character. :( I forced the version back to 1.3.21 again.

After some Google searches, I found out that people have similar mouse problems when upgrading to newer versions of wine. On several of the forum sites I visited, Ubuntu developers called this a "Regression," and said that they should perform a regression test. I looked up how to do a regression test, and it looks very complicated. Simply put, regression tests look scary as hell. If I performed a regression test, would this fix the problem, or just acknowledge that there is a problem?


(Following your instructions): Left me wondering what the hell is wrong with Wine

I used the command line, cd /var/cache/apt/archives ls
to see if I still had the file wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb. The terminal showed me a long list of files and It appeared under Partial and in red. Does this mean I only have part of the files required for 1.3.20? :confused:

I used the synaptic package manager to remove wine (For the sixth or seventh time, and counting). I entered
sudo dpkg -i wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb into the terminal and got the following:

dpkg: error: dpkg status database is locked by another process

What does this mean? Is this because the package manager did not uninstall Wine completely, or maybe I did something wrong? If the package manager is not uninstalling properly and is causing this problem, Is it possible to uninstall Wine with a terminal command (that won't affect any of my programs like RoM)? I reinstalled it again with the package manager and switched between versions 1.3.15 and 1.3.21 several times. I am Currently changing a variety of settings on the while switching between the two. However, nothing seems to be working as good as 1.3.20.

I'm thinking about waiting until Wine 1.4 is released, maybe it will be fixed by then. I heard a rumor that Runes of Magic will have browser based launcher sometime this year, maybe it will be cross platform like Quake Live :D. Forgive me for asking stupid questions and wasting your time, I'm an Idiot with computers. :o

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

11

Monday, June 6th 2011, 8:30pm

Quoted from "JedSled;425400"

... After some Google searches, I found out that people have similar mouse problems when upgrading to newer versions of wine. On several of the forum sites I visited, Ubuntu developers called this a "Regression," and said that they should perform a regression test. I looked up how to do a regression test, and it looks very complicated. Simply put, regression tests look scary as hell. If I performed a regression test, would this fix the problem, or just acknowledge that there is a problem?
Yeah, looks like the Wine guys messed something up with the mouse and 1.3.21.

Quoted from "JedSled;425400"

I used the command line you suggested to see if I still had 1.3.20. The file name you said appeared under Partial and in red. Does this mean I only have part of the files required for 1.3.20? :confused: If this is normal, could you elaborate how to copy the file somewhere and install 1.3.20? Because when I try the command you suggested I receive this in the terminal, "jedidiah@owner-Inspiron-570:~$ sudo dpkg -i wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb
dpkg: error: dpkg status database is locked by another process"
The files in the partials folder are, as the name implies, incomplete. So that won't work. You can get it here: http://wine.budgetdedicated.com/archive/binary/ Look for the file wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb or wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_amd64.deb if you want the 64 bit binaries. They are each about 12 MB in size. Make sure of the filename however since there are also debug versions ("-dbg" in name) and development versions ("-dev" in name).

Try downloading that one then do the dpkg -i line shown previously.

Quoted from "JedSled;425400"

Forgive me for asking stupid questions and wasting your time, I'm an Idiot with computers. :o
No problem. It's how we learn after all.

Edit:
OK, to elaborate on the other questions you had. To copy the .deb file to some other location (lets say your home folder), assuming you are using the command line and currently in the folder where the file is, you would use:

Source code

1
cp wine1.3_1.3.20-0ubuntu1~maverick1~ppa1_i386.deb ~/
The tilde-slash at the end is the folder we want to copy to, in this case the tilde (~) translates to your home folder.
You could of course use a file manager such as Nautilus to do the copying. I tend to show console commands for guides since they are easier to type in and for others to copy/paste.

The error you were getting for the dpkg command is likely because you had the Synaptic Package Manager or some other package manager already running. GUI Package managers are typically front-ends that actually call dpkg in the background. Hence the error "database is locked by another process". Yeah I know, a little cryptic if you don't know what it really means.
2013... The year from hell....

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

12

Monday, June 6th 2011, 8:41pm

Added a notice at the start of the guide about the possible mouse issue with Wine 1.3.21.
2013... The year from hell....

13

Tuesday, June 7th 2011, 12:52pm

Hi, guys, I experienced this issue as well.. I'm experimenting right now with PlayOnLinux, which seems to allow user to have several wine versions and configs present.. I'll let you know if I was succesful (as downgrading seems to be the only option now)

14

Tuesday, June 7th 2011, 2:06pm

Call me Master Zedock from now on.. I was succesful, here are the steps needed for running RoM on wine 1.3.20 (without the mouse missing problem):

1) Install PlayOnLinux (use your package manager - sudo apt-get install playonlinux on Debian and derivates (*buntu)..

2) You may not need this, but i installed RoM under my vanilla 1.3.21 wine and i didn't want install it (and UPDATE it) again, so I've did this:


  1. Run PlayOnLinux, Tools -> Manage wine versions -> install v1.3.20. Should be straightforward.
  2. mkdir /home/username/.PlayOnLinux/wineprefix/RoM && env WINEPREFIX=/home/username/.PlayOnLinux/wineprefix/RoM wineboot
  3. cp -r /home/username/.wine/drive_c/Program\ Files/Runes\ of\ Magic /home/username/.PlayOnLinux/wineprefix/RoM/drive_c/Program\ Files/ (or mv it, doesn’t make a difference)
  4. touch /home/username/.PlayOnLinux/configurations/installed/RoM
  5. Place the following in the RoM file:

[INDENT]#!/bin/bash
export WINEPREFIX="/home/username/.PlayOnLinux/wineprefix/RoM"
export WINEDEBUG="-all"
cd "/home/username/.PlayOnLinux/wineprefix/RoM/drive_c/Program Files/Runes of Magic"
wine "launcher.exe" $@
[/INDENT]NOTE: DO NOT COPY THESE COMMANDS..u need to change the username here (at least) and better read it twice (original post - regarding StarCraft - here).

3) in PoL interface, Manage Wine version, applications tab, select RoM and change version to 1.3.20

4) i thought it would work now, but i forgot installing vcrun2005 ie6 and wininet through winetricks (i know u did before, but not for this wine version/prefix), so, fire up you terminal and issue these two commands:

Source code

1
2
3
WINEPREFIX=/home/username/.PlayOnLinux/wineprefix/RoM winetricks vcrun2005

WINEPREFIX=/home/username/.PlayOnLinux/wineprefix/RoM winetricks ie6 wininet
and YES, do it in two steps and YES, first is WINEPREFIX and then a command...

VOILA!! I've played RoM on this setup and experienced no bugs. Ok, it was a little bit laggy, but mind that i have two VMs, full blown IDE and Firefox with 30 tabs running! Windows would choke on this..

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

15

Tuesday, June 7th 2011, 3:19pm

Thanks zedock, I knew of the multiple prefix thing with Wine but hadn't thought of attempting it through PlayOnLinux. I've updated the little notice at the start of the guide to mention your post.

Edit:
Instead of copying the RoM installed files as mentioned in zedock's post, you can move them by replacing the the copy command (cp) with the move command (mv) (you likely will need to drop the -r switch as well). Will save some time.

Also wanted to mention that the reason you need to redo the winetricks stuff is that you now have a different, independent Wine version going and therefore need to install vcrun2005, ie6, and wininet again for this new Wine prefix.
2013... The year from hell....

16

Sunday, June 12th 2011, 12:23pm

Hi Peryl,

i am the french player, who use linux since many time.

I have try to play rom with your Tutorial. But after i have update my client for the latest rev, and when i want click on start Game, the pop up arrived and tell me, your ClientUpdate have a serious problem.

Linux 11.04 i386 32bit
Wine 1.3.21

Thank by Advance.

Edit : Now i can start the game, because i have add wonetricks ie7
but i crash now when i arrived on the char loading page

have you the idea why ?

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

17

Sunday, June 12th 2011, 2:10pm

You should make sure that ie6, wininet, and vcrun2005 are installed via winetricks (you said you installed ie7 and that allowed RoM to run, so you don't need ie6 now).

Make sure that these are installing in the correct Wine and/or Wine prefix. If you had a version of Wine prior to updating (especially if one of them was manually installed instead of going through a package manager), it is possible that you have two versions of Wine on your system.

Try manually running Wine from the command line with the --version and see what version it is with:

Source code

1
wine --version

Now edit the icon you are using to start RoM and see how it starts wine, then copy the command and see if it is using the same version and/or prefix. It may simply be that it is using another and wininet and/or vcrun2005 are not installed.

Also be aware that some people seem to have problems with Wine 1.3.21. In this case, you may want to try using the PlayOnLinux guide posted by zedock above.
2013... The year from hell....

18

Sunday, June 12th 2011, 5:35pm

I have verif, i have only the 1.3.21 version on my computer.

I have verif the link on my deskop,it's good.

and i have already try playonlinux, and the launcher crash when i click on start game with him.

so i think wine alone is better and i need find why i can't play with him

If you can help me, you are welcome :)

Thank by Advance.

Peryl

Intermediate

  • "Peryl" started this thread

Posts: 313

Location: Elsewhere

  • Send private message

19

Sunday, June 12th 2011, 6:54pm

Quoted from "elderyn;427709"

I have verif, i have only the 1.3.21 version on my computer.

I have verif the link on my deskop,it's good.

and i have already try playonlinux, and the launcher crash when i click on start game with him.

Well if might be Wine 1.3.21 though I don't think so. Though if nothing else works, you can try to get 1.3.20 instead.

Other things to try:
- Make sure you have configured the audio correctly. I use the ALSA driver. Run winecfg and in the audio tab, select the ALSA driver. Also, check post #4 in this thread above. You might need to get rid of pulseaudio. It is known to be problematic.

- Also in winecfg, check under the graphics tab and ensure the vertex shader is set to hardware and the Allow Pixel Shader checkbox is checked. And also make sure you have an up-to-date video driver for your video card installed. This will likely require one of the so-called restricted drivers.

- If this still doesn't get things working, try installing DirectX9 under wine. This shouldn't be required, but it might still help. You can do this with winetricks with:

Source code

1
winetricks d3dx9
2013... The year from hell....

20

Monday, June 13th 2011, 3:30am

Now

I have reached the point where Rom is fully patched, and i can launch it and get audio, but no graphics.

I have install the linux ATI driver Radeon HD 5xxx
Have remove wine , winetricks and install the wine 1.3.20 with your .deb and install only your Winetricks packet

and i don't understand why i get audio but no graphics ...

Thank by advance for your help