Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 56
  1. #21
    Community Member jbleargh's Avatar
    Join Date
    Jan 2011
    Posts
    281

    Default

    For those having difficulties with 32bits x 64bits

    http://wiki.winehq.org/WineOn64bit

    IMHO, the best way is the Ubuntu instructions: create a chroot and install git.

    (((It isolates the patched version of wine and the official one made by your distro. So it wont mess with other games and when the official eventually starts working with ddo again you don't have to reconfigure anything)))

    If you follow the instructions, before the:

    cd wine
    ./configure
    make

    You must apply the Lotro patch:

    git apply lotro.patch


    Them in pylotro "options" you change from the regular wine to the patched one (something like "/var/chroot/wine/wine").

    Hope it helps.

  2. #22
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    That does not work on ubuntu.


    Quote Originally Posted by wkavinsky View Post
    To those having problems, please can you post specific distributions so that those of us who *have* patched and are playing can maybe help a bit better?

    For those of you on Archlinux, the steps to fix this are fairly simple:

    1) Download this PKGBUILD: http://bit.ly/TjPH2I
    2) extract PKGBUILD
    Code:
    tar -xvzf wine.tar.gz
    (not my PKGBUILD btw)
    3)
    Code:
    cd wine
    4)
    Code:
    makepkg -s
    5) wait (compiling took me a little over an hour).
    6)
    Code:
    sudo pacman -U wine-1.5.17-3-i686.pkg.tar.xz
    - you are using sudo right?
    7) play ddo. Or lotro (same issue affects both programs).

    Other distros will have different ways of compiling code, may or may not be able to help with that.

  3. #23
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by Germainium View Post
    Nice, patch works perfectly. If anyone needs a gentoo amd64 fix w/ a portage overlay ebuild, Let me know and I'll throw up a walk threw.
    I need a walk through for unbuntu 64bit amd with wine latest 64 bit

  4. #24
    Community Member
    Join Date
    Sep 2011
    Posts
    118

    Default

    Quote Originally Posted by MrElusiveness View Post
    That does not work on ubuntu.
    If you read the instructions, they're for archlinux - not Ubuntu.
    Walchek @ Ghallanda

  5. #25
    Community Member
    Join Date
    Sep 2011
    Posts
    118

    Default

    You'll either need to install the 32-bit (i386 i think on ubuntu) linux headers, or create a 32 bit chroot.

    Either way, you're stepping outside of my knowledge of building and packages on ubuntu - taking the information from this thread to the ubuntu forums will almost certainly get you more help than i can provide - sorry.

    Ubuntu Forums: http://ubuntuforums.org/

    Quote Originally Posted by AsherStar View Post
    I followed your instructions to the letter and all went well until step 4:

    4. Compile in the usual way ( "./configure ; make depend ; make" )
    # ./configure
    # make depend
    # make


    Code:
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking whether make sets $(MAKE)... yes
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables... 
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking for cpp... cpp
    checking whether gcc -m32 works... no
    configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
    yikes!
    Walchek @ Ghallanda

  6. #26
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by wkavinsky View Post
    You'll either need to install the 32-bit (i386 i think on ubuntu) linux headers, or create a 32 bit chroot.

    Either way, you're stepping outside of my knowledge of building and packages on ubuntu - taking the information from this thread to the ubuntu forums will almost certainly get you more help than i can provide - sorry.

    Ubuntu Forums: http://ubuntuforums.org/
    Yeah i tried that but, cant use a 32bit wine server with a64 bit install. (sigh)

  7. #27
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by jbleargh View Post
    For those having difficulties with 32bits x 64bits

    http://wiki.winehq.org/WineOn64bit

    IMHO, the best way is the Ubuntu instructions: create a chroot and install git.

    (((It isolates the patched version of wine and the official one made by your distro. So it wont mess with other games and when the official eventually starts working with ddo again you don't have to reconfigure anything)))
    Hope it helps.
    Chrooting does nto work because i tried that. Its a waste of time and drive space. what we need is a real fix for what the new update screwed up. it seems they may have doen something bad to the exe's

  8. #28
    Community Member
    Join Date
    Jul 2012
    Posts
    6

    Default

    Quote Originally Posted by wkavinsky View Post
    You'll either need to install the 32-bit (i386 i think on ubuntu) linux headers, or create a 32 bit chroot.

    Either way, you're stepping outside of my knowledge of building and packages on ubuntu - taking the information from this thread to the ubuntu forums will almost certainly get you more help than i can provide - sorry.

    Ubuntu Forums: http://ubuntuforums.org/
    I am running Ubuntu 12.04 x64. I attempted too create a 32 bit chroot from here: http://wiki.winehq.org/WineOn64bit - I got it to work, but with my dual monitors the screens were in twin view. After I exited the game it made Ubuntu in twin view, and I could not change it without rebooting. I thought of installing NVIDIA drivers in the chroot, but that would also install the kernels and most everything for a whole 32 bit system.

    I also attempted the patch method, to solve the problem with "Cannot build a 32-bit program, you need to install 32-bit development libraries" You can change it to: ./configure --enable-win64 but that creates a 64bit wine. Also I could not figure out how to go about installing winetricks and dlls from winetricks in to the built wine from git.

    Could someone explain winetricks in the wine-git build?

    Only options I can see is to use 32 bit Ubuntu, stop playing DDO or go back to win7 x64.

    I will attempt to do the chroot again tomorrow adding nvidia drivers and see what happens.

  9. #29
    Community Member Xilth's Avatar
    Join Date
    Jan 2011
    Posts
    103

    Default

    Quote Originally Posted by jbleargh View Post
    For those having difficulties with 32bits x 64bits

    http://wiki.winehq.org/WineOn64bit

    IMHO, the best way is the Ubuntu instructions: create a chroot and install git.

    (((It isolates the patched version of wine and the official one made by your distro. So it wont mess with other games and when the official eventually starts working with ddo again you don't have to reconfigure anything)))

    If you follow the instructions, before the:

    cd wine
    ./configure
    make

    You must apply the Lotro patch:

    git apply lotro.patch


    Them in pylotro "options" you change from the regular wine to the patched one (something like "/var/chroot/wine/wine").

    Hope it helps.

    Chroot worked for me (Ubuntu 12.04.1 x64), i have done steps from wiki + patch into source code but not with:

    git apply patch

    but old:

    patch -p1 < patch_name.diff

    No winetricks was needed for me to run ddo, only steps from wiki + patching, and adding to luncher "/var/chroot/wine/wine" as wine program. Important thing (at least for me) was to add to wine registry key with correct size of videomemory, without it i had low frame rate... it looked like wine didn't use video memory at all without that key.

    I took patch from winehq (http://bugs.winehq.org/attachment.cgi?id=42169) but its the same patch as all above.
    Last edited by Xilth; 11-14-2012 at 06:52 AM.

  10. #30
    Community Member
    Join Date
    Sep 2011
    Posts
    118

    Default

    Quote Originally Posted by Xilth View Post
    Chroot worked for me (Ubuntu 12.04.1 x64), i have done steps from wiki + patch into source code but not with:

    git apply patch

    but old:

    patch -p1 < patch_name.diff

    No winetricks was needed for me to run ddo, only steps from wiki + patching, and adding to luncher "/var/chroot/wine/wine" as wine program. Important thing (at least for me) was to add to wine registry key with correct size of videomemory, without it i had low frame rate... it looked like wine didn't use video memory at all without that key.

    I took patch from winehq (http://bugs.winehq.org/attachment.cgi?id=42169) but its the same patch as all above.
    Would you mind awfully posting a step by step on what you did for the many buntu users who are looking for help? I am *NOT* installing an ubuntu VM / partition just to figure out building it on Ubuntu - too much work, and i don't particularily like all the bloat in ubuntu anyway
    Walchek @ Ghallanda

  11. #31
    Community Member Eilyen's Avatar
    Join Date
    May 2009
    Posts
    90

    Default

    The patch to fix this crash has apparently been added to the git as of about 7 hours ago.

    This means whenever wine 1.5.18 binaries are released, they should have the fix.

  12. #32
    Community Member Xilth's Avatar
    Join Date
    Jan 2011
    Posts
    103

    Default

    Quote Originally Posted by wkavinsky View Post
    Would you mind awfully posting a step by step on what you did for the many buntu users who are looking for help? I am *NOT* installing an ubuntu VM / partition just to figure out building it on Ubuntu - too much work, and i don't particularily like all the bloat in ubuntu anyway

    Ok, i will help and write it but right now i have some nasty erros on forums and lose all what i write i do it when im back at home and have more time, but i it won't be different then http://wiki.winehq.org/WineOn64bit i just copy/past commands from that wiki... only dificult for anyone would be to edit schroot.conf (to edit schroot.conf you have to have root privilege) so from comand line wound be needed, sudo + any text editor, like:

    Code:
     sudo nano schroot.conf
    and after "Download the Wine source tree into your chroot:" but befour "Compile:" to patch source code.

  13. #33
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by Xilth View Post
    Ok, i will help and write it but right now i have some nasty erros on forums and lose all what i write i do it when im back at home and have more time, but i it won't be different then http://wiki.winehq.org/WineOn64bit i just copy/past commands from that wiki... only dificult for anyone would be to edit schroot.conf (to edit schroot.conf you have to have root privilege) so from comand line wound be needed, sudo + any text editor, like:

    Code:
     sudo nano schroot.conf
    and after "Download the Wine source tree into your chroot:" but befour "Compile:" to patch source code.
    I wonder why that link wont even load up?

  14. #34
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default attn:

    none of these fixes fix anything. The devs have borked the game so that it does not work for linux, mac, wine ect ect.
    I dont know if this was planned, but I hope they can revert it back. BTW chrooting does no good because the new in stall of wine 32bit can not run the 64bit ddo install, wich just stinks. the real fix will be when the dev correct what they did or WineHQ ends up with a new fix for our 64bit 1,4/1.5 wine's

  15. #35
    Community Member Xilth's Avatar
    Join Date
    Jan 2011
    Posts
    103

    Default

    Im very bad at writing guides for linux (i very rarely use teminal commands, and i don't know english that well...) but here it is, steps by steps what i did to run ddo on Ubuntu 12.04.1 x64 (all based on wiki: http://wiki.winehq.org/WineOn64bit)

    Important, Remove: * from all: /*etc/, i dont know how or why... but when posting that 5 chars i always get forum error... so i puted * into it to avoid errors.

    1)
    Code:
     sudo apt-get install dchroot debootstrap
    Code:
     sudo mkdir /var/chroot

    2) open /*etc/schroot/schroot.conf and eddit it, by adding at end following lines, and changing username and your ubuntu code name (ubuntu 12.04 is precise so no need to change that if u have that version).

    Code:
    [precise]
    description=Ubuntu Precise
    directory=/var/chroot
    users=your_username
    groups=sbuild
    root-groups=root

    Note: to edit /*etc/schroot/schroot.conf you have to have root privilege, i edited it by using nano but any text editor would be good too, i used command to open it:

    Code:
     sudo nano /*etc/schroot/schroot.conf
    When the file is open just add at end lines and save, nano is easy to use so there shuldnt be any problems.

    3) In next command one more time replace "precise" with your Ubuntu version, you can alsow change mirror site if u like but i don't think that is needed, that server has files for other ubuntus too:
    Code:
     sudo debootstrap --variant=buildd --arch i386 precise /var/chroot/ http://ubuntu.cs.utah.edu/ubuntu/
    4)
    Code:
     sudo cp /*etc/apt/sources.list /var/chroot/*etc/apt/
    5)
    Code:
     sudo chroot /var/chroot
    6)
    Code:
     apt-get update
    Code:
     apt-get build-dep wine
    7)
    Code:
     apt-get install git
    Code:
     git clone git://source.winehq.org/git/wine
    8) Right now we are inside chroot, so "/var/chroot" is now "/" and u can't "go" outside the chroot at this terminal, so for commands at this point just open new terminal window, but dont close "chroot" one, we will be back to it in next point.

    - download and save patch in your (/home/your_user_name) directory, patch is from: http://bugs.winehq.org/attachment.cgi?id=42169, after downloding change name for somthing that you will remember.

    - Copy patch to /var/chroot/wine, go to source code and add patch to the sources with commands:
    (change your_user_name and name_of_the_patch with appropriate names)
    Code:
     sudo cp /home/your_user_name/name_of_the_patch /var/chroot/wine
    Code:
     cd /var/chroot/wine
    Code:
     patch -p1 < name_of_the_patch
    *close this terminal window and back to chroot one

    9) In chroot terminal we go to wine directory and compile sources with comands:
    Code:
     cd wine
    Code:
     ./configure
    Code:
     make
    * runing make will take lots of time... so be patient

    10) exiting the chroot, to "normal" terminal
    Code:
     exit
    11) If u had ealier installed wine by normal package u should be good and no need to install it again, if u didnt had any wine version u have to install it outside the chroot with command:

    Code:
     sudo apt-get install wine
    12) go to pylotro > options and add: /var/chroot/wine/wine as wine program, for me that worked but i had low frame rate... so one more step

    13) We are adding to wine registry correct size of video memory. Wine folder in your home directory is usually hiden, but this time it was just: wine for me, eddit it by adding right registry key.

    - open registry file with nano:
    Code:
     nano /home/your_user_name/wine/user.reg
    - add at end of file 2 lines, replace your_video_memoy_size with corect number e.g. 512 mb > 512, 1Gb > 1024,
    Code:
     [Software\\Wine\\Direct3D] 1331547889
    "VideoMemorySize"="your_video_memoy_size"
    And thats all what i did to run ddo... please have in minde that i trayed to be as much helpfull as i can but im not specialist in linux stuff
    Last edited by Xilth; 11-15-2012 at 01:36 PM.

  16. #36
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by Xilth View Post
    Im very bad at writing guides for linux (i very rarely use teminal commands, and i don't know english that well...) but here it is, steps by steps what i did to run ddo on Ubuntu 12.04.1 x64 (all based on wiki: http://wiki.winehq.org/WineOn64bit)

    Important, Remove: * from all: /*etc/, i dont know how or why... but when posting that 5 chars i always get forum error... so i puted * into it to avoid errors.

    1)
    Code:
     sudo apt-get install dchroot debootstrap
    Code:
     sudo mkdir /var/chroot

    2) open /*etc/schroot/schroot.conf and eddit it, by adding at end following lines, and changing username and your ubuntu code name (ubuntu 12.04 is precise so no need to change that if u have that version).

    Code:
    [precise]
    description=Ubuntu Precise
    directory=/var/chroot
    users=your_username
    groups=sbuild
    root-groups=root

    Note: to edit /*etc/schroot/schroot.conf you have to have root privilege, i edited it by using nano but any text editor would be good too, i used command to open it:

    Code:
     sudo nano /*etc/schroot/schroot.conf
    When the file is open just add at end lines and save, nano is easy to use so there shuldnt be any problems.

    3) In next command one more time replace "precise" with your Ubuntu version, you can alsow change mirror site if u like but i don't think that is needed, that server has files for other ubuntus too:
    Code:
     sudo debootstrap --variant=buildd --arch i386 precise /var/chroot/ http://ubuntu.cs.utah.edu/ubuntu/
    4)
    Code:
     sudo cp /*etc/apt/sources.list /var/chroot/*etc/apt/
    5)
    Code:
     sudo chroot /var/chroot
    6)
    Code:
     apt-get update
    Code:
     apt-get build-dep wine
    7)
    Code:
     apt-get install git
    Code:
     git clone git://source.winehq.org/git/wine
    8) Right now we are inside chroot, so "/var/chroot" is now "/" and u can't "go" outside the chroot at this terminal, so for commands at this point just open new terminal window, but dont close "chroot" one, we will be back to it in next point.

    - download and save patch in your (/home/your_user_name) directory, patch is from: http://bugs.winehq.org/attachment.cgi?id=42169, after downloding change name for somthing that you will remember.

    - Copy patch to /var/chroot/wine, go to source code and add patch to the sources with commands:
    (change your_user_name and name_of_the_patch with appropriate names)
    Code:
     sudo cp /home/your_user_name/name_of_the_patch /var/chroot/wine
    Code:
     cd /var/chroot/wine
    Code:
     patch -p1 < name_of_the_patch
    *close this terminal window and back to chroot one

    9) In chroot terminal we go to wine directory and compile sources with comands:
    Code:
     cd wine
    Code:
     ./configure
    Code:
     make
    * runing make will take lots of time... so be patient

    10) exiting the chroot, to "normal" terminal
    Code:
     exit
    11) If u had ealier installed wine by normal package u should be good and no need to install it again, if u didnt had any wine version u have to install it outside the chroot with command:

    Code:
     sudo apt-get install wine
    12) go to pylotro > options and add: /var/chroot/wine/wine as wine program, for me that worked but i had low frame rate... so one more step

    13) We are adding to wine registry correct size of video memory. Wine folder in your home directory is usually hiden, but this time it was just: wine for me, eddit it by adding right registry key.

    - open registry file with nano:
    Code:
     nano /home/your_user_name/wine/user.reg
    - add at end of file 2 lines, replace your_video_memoy_size with corect number e.g. 512 mb > 512, 1Gb > 1024,
    Code:
     [Software\\Wine\\Direct3D] 1331547889
    "VideoMemorySize"="your_video_memoy_size"
    And thats all what i did to run ddo... please have in minde that i trayed to be as much helpfull as i can but im not specialist in linux stuff
    The only problem with this method is that for those of us who still use a 64bit install of wine, the chrooted on will not run our 64 bit wine drive of ddo . Iam going to see if i can compile the 64 bit edition from sources with the patch and I will elt you know if it worked or not.

  17. #37
    Community Member
    Join Date
    Dec 2010
    Location
    Dartmouth, Nova Scotia
    Posts
    6

    Default

    Updated to Wine 1.5

    Installed git and grabbed the previously posted DDO patch...

    But I get this on apply

    me@Edited ~/wine-git $ patch -p1 < ddo.patch
    patching file dlls/user32/winpos.c
    Hunk #1 FAILED at 250.
    1 out of 1 hunk FAILED -- saving rejects to file dlls/user32/winpos.c.rej

    Ideas?

  18. #38
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by ZaGs View Post
    Updated to Wine 1.5

    Installed git and grabbed the previously posted DDO patch...

    But I get this on apply

    me@Edited ~/wine-git $ patch -p1 < ddo.patch
    patching file dlls/user32/winpos.c
    Hunk #1 FAILED at 250.
    1 out of 1 hunk FAILED -- saving rejects to file dlls/user32/winpos.c.rej

    Ideas?
    Yeah that patch will not work for the curent 64bit wine. I tried that earlyer. and whats weird now, is I dont even get the errors when trying to run ddo. it just does nothing after login screen.

  19. #39
    Community Member Eilyen's Avatar
    Join Date
    May 2009
    Posts
    90

    Default

    Quote Originally Posted by ZaGs View Post
    Updated to Wine 1.5

    Installed git and grabbed the previously posted DDO patch...

    But I get this on apply

    me@Edited ~/wine-git $ patch -p1 < ddo.patch
    patching file dlls/user32/winpos.c
    Hunk #1 FAILED at 250.
    1 out of 1 hunk FAILED -- saving rejects to file dlls/user32/winpos.c.rej

    Ideas?
    As I said before (few posts up), the patch has already been added to the git, no need to patch it, just compile it.

  20. #40
    Community Member
    Join Date
    Nov 2009
    Posts
    151

    Default

    Quote Originally Posted by Eilyen View Post
    As I said before (few posts up), the patch has already been added to the git, no need to patch it, just compile it.
    Ya you can tell that something was updated because now none of the ddo programs will even load up. no more error debug info, nothing at all cept for the basic pylotro stuff working. LOL NOW WHAT?

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload