[FAQ] Ryzom in Linux (The Unofficial HOW-TO)

[blaah]

what am I doing wrong?

check if .exe and .dll's are in ryzom folder or still in unpack folder.

if still in unpack, then you can get and run this http://atys.pri.ee/files/updt_nl.sh while in ryzom folder (sh updt_nl.sh)
it's dated 15 feb, but should work still.

if no .exe/.dll's are found, then new install (you can use Repair in InstallShield i think).
no need to use install script (.run file), but if you want to, get http://atys.pri.ee/files/ryzom_linux_installer_070228.tgz

[japamala]

thanks, the sh worked.

[japamala]

Ok, I got it working and everrything, but there's only one small problem:

when I press shift of Ctrl (I have not tried alt, but I assume it too) I get this:

http://img467.imageshack.us/my.php?imag ... ot2yh8.png

can anybody help with this?

[katriell]

Your image is only a thumbnail, but I guess your problem might be this.

Add this to your launch script, just before the "wine client_ryzom_rd.exe" part:

Code: Select all

export LANG=en_US

for k in 50 37 64 62 109 113; do xset r $k; done

Then after the "wine client_ryzom_rd.exe" part, add:

Code: Select all

sleep 20
for k in 50 37 64 62 109 113; do xset r $k; done

[japamala]

Your image is only a thumbnail, but I guess your problem might be this.

Add this to your launch script, just before the "wine client_ryzom_rd.exe" part:

Code: Select all

export LANG=en_US

for k in 50 37 64 62 109 113; do xset r $k; done

Then after the "wine client_ryzom_rd.exe" part, add:

Code: Select all

sleep 20
for k in 50 37 64 62 109 113; do xset r $k; done

I fixed the link.

and I'm in wondows atm, but I'll try that as soon as I reboot.

[blaah]

when I press shift of Ctrl (I have not tried alt, but I assume it too) I get this:

what wine version you using ? (wine --version)

dont remember exact wine release, but at least from 0.9.30 this shoud be fixed.
thats why i didnt include xset commands in install scripts (not that it does any harm if you use xset, just not needed with latest wine).

i even run in fullscreen now and can use alt-tab to switch to other programs (xset fix does not allow this)
(after switching back to Ryzom, press alt first as it's most probably stuck after alt-tab out)

[jamela]

I've been trying again, and now that Wine 0.9.32 has been released I guess that all the links in your scripts, maryen and blaah, have been changed; they all seem to end up installing wine 0.9.31, and not working. I found and downloaded a .tar.bz2 for 0.9.30 and am trying to work out how to install it .

Edit: Ubuntu help with installing tarballs is ... amusingly circular.

[katriell]

I've been trying again, and now that Wine 0.9.32 has been released I guess that all the links in your scripts, maryen and blaah, have been changed; they all seem to end up installing wine 0.9.31, and not working. I found and downloaded a .tar.bz2 for 0.9.30 and am trying to work out how to install it .

Edit: Ubuntu help with installing tarballs is ... amusingly circular.

Usually, installing from source (what you usually get in .tar.* files, and certainly what you get in Wine's case) is done with three simple commands in the Terminal. This is done after you've extracted the tar, opened Terminal, and cd'ed into the freshly extracted directory.

First, make sure you have the recommended packages, which can be installed via Synaptic Package Manager.

Code: Select all

./configure

^ Take care of any warnings this gives you before moving on. ^

Code: Select all

make

Code: Select all

sudo make install

[maryen]

I just got done installing wine 0.9.32 source, Quick How-to:

First, download and run this script by Dan Kegel http://kegel.com/wine/edgy.sh

sudo sh edgy.sh

next, download the source and unpack it. Go into the unpacked directory in the terminal and type

./configure CFLAGS=-fno-stack-protector

after type

make depend

and

make

finally, type

sudo make install

and you're done.

to uninstall, use 'sudo make uninstall'.

also, 0.9.32 has fixed the regression in msi!! I'm currently testing how it runs the game. Also(2), new version of the installer! It's blaah's code, with some modifications from me and ported to python. Now if I could only figure out how to work makeself...

new in this version...

- basic error detection for wget (if you lose your internet connection and wget closes, the installer recognizes it instead of trying to install a half downloaded file)
- md5 checksum checking for the client installer
- uninstall removed till I can figure out how to remove every trace of ryzom from your wine folder.
-install disabled if using wine 0.9.31
and other stuff...
http://rapidshare.com/files/19142197/Rally_v1.2.tar.gz

you run it by typing

./rally.py

instead of 'sh'. Also, python has to be installed on your system for this.

[blaah]

Also(2), new version of the installer! It's blaah's code, with some modifications from me and ported to python. Now if I could only figure out how to work makeself...

give rally.py execute status (chmod +x rally.py) and then in "Rally v1.2" directory
makeself . ../Rally_v1.2.run "Rally v1.2" ./rally.py
first is patch what to include, second is file it generates, third is title for that file, fourth is script that is executed after .run file is executed and unpacked.
rally.py is then executed in the temporary directory where .run was unpacked. in shell, i used `pwd` to get that directory and saved it for later when copying ryzom scripts.

dont know about Puthon much (probably some libraries that most ppl dont have installed, has some UI elements , but to keep things simple...

to add text mode UI to it, you can use dialog or whiptail (whiptail is "light" version from dialog, but syntax is same). one of those should be present in every installed desktop linux.

to add GUI, check kdialog (from kde), zenity (from gnome).
kdialog is mostly the same as dialog/whiptail again. so if you detect that kdialog is installed, you can just use it instead of text mode dialog.

zenity does some things his own way (damn him), so you need some "simple" workarounds (like you calling your own function with needed parameters and that function translates them to whichever ui program is in use)

getting user input back should be same for all of them (dialog/whiptail is).
Button presses is error code (pressing ESC or program own failure is negative error code, -1 for example), user text input is stderr output (in shell, you redirect stderr to file and then read that file to get the answer)

also, after installing Ryzom and not finding Ryzom in "Program Files" ask user where it's installed and generate Ryzom scripts for that path ?

just someideas for your next release