Page 32 of 37
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Mar 06, 2007 4:10 pm
by katriell
I'm thinking that once a concrete method of setting up Ryzom is hammered out, we could get it added to that app's list.
Beyond helping those who have already decided they want to play Ryzom on Linux, it might attract attention to the game's existence.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Mar 06, 2007 11:16 pm
by maryen
well, the method is pretty concrete, the big problem is the installer is fickle and sometimes crashes at the very end. It seems to do it randomly too, but thankfully the bug doesn't seem to harm the actual installation of the game.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Fri Mar 09, 2007 5:16 am
by maryen
Rally V1.2.2 Beta is here, and it seems to be stable!
http://sourceforge.net/projects/rally/
as you can see, I've got this hosted on sourceforge now, and I hope to expand this program to work with other games in linux soon.
There are a number of changes from 1.2.1, for example, now Rally detects installations of Ryzom from the start and patches them to work in linux. Uninstall is now properly working too! Also, the program is just one file now, with rally generating patch.pl etc. Finally, a lot of the reliance on bash code has been removed.
This is probably the most stable one I've made so far, with me having installed and uninstalled ryzom around 20 times to test this script.
coming in subsequent releases:
optional gtk and qt UI, a configuration program to replace the built in one for ryzom, more error checking, and support for oblivion.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Sat Mar 10, 2007 8:02 pm
by blaah
maryen wrote:Uninstall is now properly working too!
if i understand it correctly, you nuke entire Uninstall directory under "Program Files" ?
what if user has other uninstall programs under there ? you nuke them too that way.
what you need to to is find right key from [Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\] (system.reg file, no spaces in that key)
you can check "DisplayName" value to find right key
For ryzom, its this currently: (it may or may not change with new installers)
[Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\InstallShield_{A9BF1560-04E4-4D92-98CD-6BFCDD240489}]
(again, no spaces in that key)
and then run this:
uninstaller --remove "InstallShield_{A9BF1560-04E4-4D92-98CD-6BFCDD240489}"
... or lazy mode: tell User that script is gonna run Uninstaller and that he/she needs to select Ryzom and press uninstall button
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Sun Mar 11, 2007 9:34 am
by maryen
^yes, it nukes the uninstall directory right now, but I'm making the next version target the ryzom uninstaller specifically. As to why I avoid having the actual uninstaller remove the game, it's because the uninstaller is much more unstable than the installer and very crash prone.
I'm also working on a method of installation that bypasses the ryzom installer using cabextract, for stability and speed purposes. I've managed to actually create an unofficial installer for linux, but it's slower than the ryzom distributed one, and includes the opensource vera fonts instead of the ones distributed by the game. These get flushed out by the game updating, but they have to be deleted by the user or they get in the way of the normal fonts. Anyway, v1.2.3 will have a completely crash free install (if you have cabextract on your system) and hopefully a quicker install to boot.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Mar 13, 2007 9:15 am
by japamala
I get this when I try runing it:
Code: Select all
[japa@localhost Desktop]$ ./Ryzom_Windowed.sh
wine: Unhandled page fault on read access to 0x0000000c at address 0x7800fdc9 (t
hread 000b), starting debugger...
Unhandled exception: page fault on read access to 0x0000000c in 32-bit code (0x7
800fdc9).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:7800fdc9 ESP:0034ed54 EBP:0034ed7c EFLAGS:00010286( - 00 -RISP1)
EAX:0034edcc EBX:45c6eef3 ECX:0034edcc EDX:017c3a34
ESI:00000000 EDI:ffffffff
Stack dump:
0x0034ed54: ffffffff 016f7d10 45c6eef3 ffffffff
0x0034ed64: 7800bd6a 0034e8c8 0034edcc 7800bd6a
0x0034ed74: 78033930 ffffffff 0034fe6c 0091a98c
0x0034ed84: 00000000 0152ee7c 014e66ac 0152f1b7
0x0034ed94: 016f7d10 00000000 0000fe34 00000000
0x0034eda4: 01790100 01816c30 01816c3d 01816c3e
Backtrace:
=>1 0x7800fdc9 in msvcrt (+0xfdc9) (0x0034ed7c)
2 0x0091a98c in client_ryzom_rd (+0x51a98c) (0x0034fe6c)
3 0x011966b2 in client_ryzom_rd (+0xd966b2) (0x0034ff08)
4 0x7ee901de start_process+0xee(arg=0x0) [/home/japa/Desktop/wine-0.9.32/wine-
0.9.32/dlls/kernel32/process.c:820] in kernel32 (0x0034ffe8)
5 0xb7e235d7 wine_switch_to_stack+0x17() in libwine.so.1 (0x00000000)
0x7800fdc9: testb $0x40,0xc(%esi)
Modules:
Module Address Debug info Name (91 modules)
PE 350000-369000 Deferred wwwcore
PE 370000-378000 Deferred wwwutils
PE 380000-386000 Deferred wwwtrans
PE 390000-399000 Deferred wwwmime
PE 3a0000-3a7000 Deferred wwwcache
PE 3b0000-3b7000 Deferred wwwstream
PE 3c0000-3cd000 Deferred wwwapp
PE 3d0000-3e3000 Deferred gnu_regex
PE 3f0000-3fe000 Deferred wwwhttp
PE 400000-16ce000 Export client_ryzom_rd
PE 16d0000-16db000 Deferred wwwhtml
PE 16e0000-179e000 Deferred stlport_vc645
PE 10000000-10007000 Deferred wwwfile
PE 78000000-78045000 Export msvcrt
PE 780c0000-78121000 Deferred msvcp60
ELF 7bf00000-7bf03000 Deferred <wine-loader>
ELF 7d7f6000-7d80b000 Deferred midimap<elf>
\-PE 7d800000-7d80b000 \ midimap
ELF 7d831000-7d849000 Deferred msacm32<elf>
\-PE 7d840000-7d849000 \ msacm32
ELF 7d869000-7d89b000 Deferred uxtheme<elf>
\-PE 7d870000-7d89b000 \ uxtheme
ELF 7d89b000-7d8a5000 Deferred libxcursor.so.1
ELF 7d8a5000-7d8c2000 Deferred imm32<elf>
\-PE 7d8b0000-7d8c2000 \ imm32
ELF 7d8c2000-7d8c5000 Deferred libxinerama.so.1
ELF 7d93c000-7d93e000 Deferred libnvidia-tls.so.1
ELF 7d93e000-7e101000 Deferred libglcore.so.1
ELF 7e101000-7e186000 Deferred libgl.so.1
ELF 7e186000-7e18c000 Deferred libxdmcp.so.6
ELF 7e18c000-7e18f000 Deferred libxau.so.6
ELF 7e18f000-7e28d000 Deferred libx11.so.6
ELF 7e28d000-7e29c000 Deferred libxext.so.6
ELF 7e29c000-7e2b5000 Deferred libice.so.6
ELF 7e2b5000-7e2be000 Deferred libsm.so.6
ELF 7e2be000-7e34b000 Deferred winex11<elf>
\-PE 7e2d0000-7e34b000 \ winex11
ELF 7e3bc000-7e4e9000 Deferred libxml2.so.2
ELF 7e4e9000-7e517000 Deferred libfontconfig.so.1
ELF 7e517000-7e52a000 Deferred libz.so.1
ELF 7e52a000-7e597000 Deferred libfreetype.so.6
ELF 7e599000-7e59e000 Deferred libxfixes.so.3
ELF 7e59e000-7e5a2000 Deferred libxrandr.so.2
ELF 7e5a2000-7e5ab000 Deferred libxrender.so.1
ELF 7e5ad000-7e5f6000 Deferred dbghelp<elf>
\-PE 7e5c0000-7e5f6000 \ dbghelp
ELF 7e5f6000-7e60d000 Deferred imagehlp<elf>
\-PE 7e600000-7e60d000 \ imagehlp
ELF 7e60d000-7e69b000 Deferred winmm<elf>
\-PE 7e620000-7e69b000 \ winmm
ELF 7e69b000-7e6cd000 Deferred winspool<elf>
\-PE 7e6a0000-7e6cd000 \ winspool
ELF 7e6cd000-7e789000 Deferred comctl32<elf>
\-PE 7e6e0000-7e789000 \ comctl32
ELF 7e789000-7e7de000 Deferred rpcrt4<elf>
\-PE 7e7a0000-7e7de000 \ rpcrt4
ELF 7e7de000-7e877000 Deferred ole32<elf>
\-PE 7e7f0000-7e877000 \ ole32
ELF 7e877000-7e8cf000 Deferred shlwapi<elf>
\-PE 7e890000-7e8cf000 \ shlwapi
ELF 7e8cf000-7e9c4000 Deferred shell32<elf>
\-PE 7e8e0000-7e9c4000 \ shell32
ELF 7e9c4000-7ea64000 Deferred comdlg32<elf>
\-PE 7e9d0000-7ea64000 \ comdlg32
ELF 7ea64000-7eaf7000 Deferred gdi32<elf>
\-PE 7ea80000-7eaf7000 \ gdi32
ELF 7eaf7000-7ec31000 Deferred user32<elf>
\-PE 7eb10000-7ec31000 \ user32
ELF 7ec31000-7ec76000 Deferred advapi32<elf>
\-PE 7ec40000-7ec76000 \ advapi32
ELF 7ec76000-7ec88000 Deferred libresolv.so.2
ELF 7ec88000-7eca6000 Deferred iphlpapi<elf>
\-PE 7ec90000-7eca6000 \ iphlpapi
ELF 7eca6000-7ecd2000 Deferred ws2_32<elf>
\-PE 7ecb0000-7ecd2000 \ ws2_32
ELF 7ecd2000-7ecec000 Deferred wsock32<elf>
\-PE 7ece0000-7ecec000 \ wsock32
ELF 7ecec000-7ecf6000 Deferred libnss_files.so.2
ELF 7ecf7000-7ed0c000 Deferred psapi<elf>
\-PE 7ed00000-7ed0c000 \ psapi
ELF 7ee20000-7ef46000 Dwarf kernel32<elf>
\-PE 7ee40000-7ef46000 \ kernel32
ELF 7ef46000-7ef6b000 Deferred libm.so.6
ELF 7ef6b000-7f000000 Deferred ntdll<elf>
\-PE 7ef80000-7f000000 \ ntdll
ELF b7cc2000-b7cc6000 Deferred libdl.so.2
ELF b7cc6000-b7df3000 Deferred libc.so.6
ELF b7df3000-b7e06000 Deferred libpthread.so.0
ELF b7e06000-b7e0b000 Deferred libxxf86vm.so.1
ELF b7e1c000-b7f2d000 Dwarf libwine.so.1
ELF b7f2e000-b7f48000 Deferred ld-linux.so.2
Threads:
process tid prio (all id:s are in hex)
0000000a (D) C:\Program Files\Ryzom\client_ryzom_rd.exe
0000000b 0 <==
00000008
00000009 0
do I need to re-install wine?
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Mar 13, 2007 10:34 am
by blaah
japamala wrote:do I need to re-install wine?
if you already haven't reinstalled it
, then you may try to remove msvcrt.dll from ryzom directory and/or from windows\system or windows\system32
then run wineprefixcreate (that makes wine msvcrt.dll appear in system32 again.
try to run Ryzom again. if it crashes, reinstall wine (and if you compiled it yourself, make sure there is no traces under /usr/local/bin and /usr/local/lib as there it goes by default)
if it runs, all good
(well, without msvcrt.dll from windows, it runs a bit slower, or did last time i checked)
... or you could move Ryzom out from ".wine/drive_c/Program Files", nuke the entire .wine directory, run wineprefixcreate, move Ryzom back to "Program Files" (if you want, it does not have to be there, just edit launcher scripts for right location) and try again.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Mar 13, 2007 12:18 pm
by japamala
tried re-installing wine, removing the DLL, and nuking the entire directory..
formating is next on my list.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Sun Mar 18, 2007 8:55 am
by emfinnsy
Yay. I finally got everything (bar sound) up and stable by following the current thread and scripts here and 4 days later (3 of them playless work days) along comes and new Ryzom patch.
I'm sitting indefiitely at the "Launching Ryzom Patcher" point. Is it just me?
Using the old patch.pl gets me a
"No such file or directory at /home/mark/.wine/drive_c/Program Files/Ryzom/patch.pl line 3."
Am I alone in the world or is this a new wave of sufferring?
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Sun Mar 18, 2007 11:45 am
by blaah
emfinnsy wrote:I'm sitting indefiitely at the "Launching Ryzom Patcher" point. Is it just me?
add this to client.cfg (caps matter, so big B and big D)
BackgroundDownloader = 0;
maybe it helps.
Using the old patch.pl gets me a
"No such file or directory at /home/mark/.wine/drive_c/Program Files/Ryzom/patch.pl line 3."
i believe it just says that it cant find updt_nl.bat (script ryzom creates to move new files inplace). unless you get "Relaunch Ryzom" all the time, nothing to worry about.