Is Wine64 usable yet?

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Boris Shingarov

Is Wine64 usable yet?

Post by Boris Shingarov »

Hi,

I am trying to get a general feel of how usable Wine64 is.
I just built 1.3.13.
To see how well it works, I ran 64-bit Putty. It works flawlessly.
Now, I am trying to play around with different little programs. I took
"notepad.exe" from a Windows 7 install (hoping it would be a reasonably
simple program for a start). It crashed with:

fixme:heap:HeapSetInformation (nil) 1 (nil) 0

It didn't even get to the point to display a window.

Next, I took calc.exe. It, too, crashed before showing anything:

wine: Call from 0x7b847a14 to unimplemented function
windowscodecs.dll.WICCreateImagingFactory_Proxy, aborting
wine: Unimplemented function
windowscodecs.dll.WICCreateImagingFactory_Proxy called at address
0x7b847a14 (thread 0009), starting debugger...
couldn't load main module (0)
Unhandled exception: unimplemented function
windowscodecs.dll.WICCreateImagingFactory_Proxy called in 64-bit code
(0x000000007b847a14).
fixme:dbghelp_dwarf:compute_location Unhandled attr op: 4
fixme:dbghelp:elf_new_wine_thunks Duplicate in L"kernel32<elf>":
__wine_dbch_time<7bbc3000-00000010> __dbch<7bbc3000-0>

What I want to achieve in the end, is run Hauptwerk for Windows which
has no Linux replacement. I want to run it headless/embedded, and am
finding Windows ill-suited for autonomous embedded operation. The 32
bit version seems to work well under Wine. I need to figure out a few
issues with devices -- this will mean writing a couple of LibWine native
DLLs -- but before going in there, I wanted to see whether 64 bits are a
major additional complication. If we were talking about a couple of
bugs, I would try to help fixing those. But the amount of success I am
getting with simplest programs such as Notepad and Calc, is not
encouraging. Do we need to wait a few years before Wine64 matures, or
am I missing something?
madewokherd
Level 4
Level 4
Posts: 149
Joined: Mon Jun 02, 2008 5:03 pm

Is Wine64 usable yet?

Post by madewokherd »

You'll want to make sure you have a recent gcc; see
http://wiki.winehq.org/Wine64

As a general rule, taking programs shipped with Windows and trying to
run them in Wine is not a good test of anything. They are not like
normal programs. Maybe notepad and calc used to be simple, but I'm not
so sure that's the case in Windows 7.

Your error is caused by an unimplemented function, which is nothing to
do with the architecture. That particular error tends to show up in
.NET programs that use WIC.

I'm pretty sure that if you compile a 64-bit PE notepad or calc from
Wine's codebase, those programs will work.

I think the fact that 7zip and Putty work is an indication that the
simplest of 64-bit programs do run, and the basic architecture is
working.

I would guess that if you have a program that is compiled for 32-bit
and 64-bit from a shared codebase, it's not using any MS components
when it runs in Wine, its installer works, and it's not using
typelibs, the architecture probably won't be very important.
User avatar
André H.
Moderator
Moderator
Posts: 207
Joined: Sun Dec 07, 2008 8:33 am

Post by André H. »

Also more complex apps like Firefox 4.0b12pre win64 run in wine
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

I was able to install vcrun2005_x64 and vcrun2008_x64 with winetricks but had no success with any applications or dotnet installations. However nice to know that shared wow64 build is now easy to do. It was pretty hard to find the OpenCL-libs for Ubuntu, maybe someone would want to update the wiki with links to correct debs.
James McKenzie

Is Wine64 usable yet?

Post by James McKenzie »

On 2/21/11 7:21 AM, sniveri wrote:
I was able to install vcrun2005_x64 and vcrun2008_x64 with winetricks but had no success with any applications or dotnet installations. However nice to know that shared wow64 build is now easy to do. It was pretty hard to find the OpenCL-libs for Ubuntu, maybe someone would want to update the wiki with links to correct debs.
You can do this yourself by obtaining a Wiki editor account and updating
the entries. Remember NO WAREZ sites are permitted on the Wiki and they
will be removed and you will be banned. If the sites are supported by
Ubuntu, that is best.

James McKenzie
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Re: Is Wine64 usable yet?

Post by sniveri »

James McKenzie wrote: You can do this yourself by obtaining a Wiki editor account and updating
the entries. Remember NO WAREZ sites are permitted on the Wiki and they
will be removed and you will be banned. If the sites are supported by
Ubuntu, that is best.
Thanks for the tip, James. The sites where I grabbed the debs were a bit odd so it would be best that someone who really knows this stuff gets the correct packages hosted in somewhere. Maybe I was just lucky to get something useful out of those as the build was successful. I will try to look if I found the site again so someone skilled guy could look if these debs are usable and does not contain anything unwanted.

And slight correction to my earlier post: I was not able to install any of applications I normally use with wine, but for example Firefox 64-bit works as described in Andres post earlier.
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

Here is link for the discussion about ATI OpenCL-libs on Ubuntu forums:

http://ubuntuforums.org/showthread.php?t=1477153

And here is link to actual debs what I did use:

http://orwell.fiit.stuba.sk/~nou/
James McKenzie

Is Wine64 usable yet?

Post by James McKenzie »

On 2/21/11 7:55 AM, sniveri wrote:
Here is link for the discussion about ATI OpenCL-libs on Ubuntu forums:

http://ubuntuforums.org/showthread.php?t=1477153

And here is link to actual debs what I did use:

http://orwell.fiit.stuba.sk/~nou/
Looks like a rouge AMD engineer. At least this code may make it into
the Catalyst series of drivers. As to the person asking that they be put
on the Ubuntu ppa, not going to happen. Have you tried building a
custom build of Wine with them and does it make video better or worse?

James McKenzie
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Re: Is Wine64 usable yet?

Post by sniveri »

James McKenzie wrote:Looks like a rouge AMD engineer. At least this code may make it into
the Catalyst series of drivers. As to the person asking that they be put
on the Ubuntu ppa, not going to happen. Have you tried building a
custom build of Wine with them and does it make video better or worse?
I did install those packages because I got complains about missing libs when building wow64 - wine setup from latest sources pulled from wine-git. After installing those OpenCL-debs there were no warnings about missing libs.

I did not notice anything changed on wine-usage as there is not much to test, Firefox 64 actually runs pretty well and graphics with it seems to be correct. Do not know if this answers your question. Have to test what happens when some application is installed in 32-bit side..
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

Tried to test installations and other stuff but somehow winetricks or something else is mixed up.. if I set WINEARCH=win32 I get result:

Code: Select all

wine: WINEARCH set to win32 but '.wine' is a 64-bit installation
If I set WINEARCH=win64 I get result:

Code: Select all

wine: WINEARCH set to win64 but '.wine' is a 32-bit installation
and If I remove the WINEARCH from env variables then wine 64 becomes usable again. Maybe someone has instructions how to enable 32-bit wine in wow64 setup?[/code]
James McKenzie

Is Wine64 usable yet?

Post by James McKenzie »

On 2/21/11 2:49 PM, sniveri wrote:
Tried to test installations and other stuff but somehow winetricks or something else is mixed up.. if I set WINEARCH=win32 I get result:


Code:
wine: WINEARCH set to win32 but '.wine' is a 64-bit installation



If I set WINEARCH=win64 I get result:


Code:
wine: WINEARCH set to win64 but '.wine' is a 32-bit installation



and If I remove the WINEARCH from env variables then wine 64 becomes usable again. Maybe someone has instructions how to enable 32-bit wine in wow64 setup?[/code]

Use the WINEPREFIX environment variable to create a Wine Prefix.
Something like:

WINEPREFIX=$HOME/wine64 WINEARCH=wine64 wine <64bit program installer>

and the same for 32 bit but name the wine prefix directory wine32.

James McKenzie
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

James McKenzie wrote:On 2/21/11 2:49 PM, sniveri wrote:
Use the WINEPREFIX environment variable to create a Wine Prefix.
Something like:

WINEPREFIX=$HOME/wine64 WINEARCH=wine64 wine <64bit program installer>

and the same for 32 bit but name the wine prefix directory wine32.
James McKenzie
Hmm.. It is just not that simple. Setting up prefix for both of wines does only separate wine32 and wine64 folders which both are 64-bit wows. Do not know how this could help?

What I did found out is that if I try to run wine directly from command line it does not do anything useful, instead it just complains wrong architecture. BUT if I start installers and programs from nautilus right clicking and using "Wine Windows Program Loader"-command, installations can be done and programs runs no matter if it is 32-bit or 64-bit app.

So seems that the wineloader can detect if app is 32-bit or 64-bit, sounds great! However winetricks does not work for me at all. For time to time I have luck to get something installed with winetricks, but usually it just complains that it can not retrieve "%ProgramFiles%" folder if winearch is set to WINEARCH=win32.

For the graphics: I did only had one issue during installation where screen first turns black and then graphics appear again, but all the white colors are replaced with green. When the installation was almost finished screen went black again and after that graphics was correct. I did install SolidWorks 2010 SP5 to wow64 32-bit side.

All the test was done with Ubuntu 10.10 64-bit and from latest sources from wine-git.
madewokherd
Level 4
Level 4
Posts: 149
Joined: Mon Jun 02, 2008 5:03 pm

Is Wine64 usable yet?

Post by madewokherd »

On Mon, Feb 21, 2011 at 3:49 PM, sniveri <[email protected]> wrote:
Tried to test installations and other stuff but somehow winetricks or something else is mixed up.. if I set WINEARCH=win32 I get result:


Code:
wine: WINEARCH set to win32 but '.wine' is a 64-bit installation



If I set WINEARCH=win64 I get result:


Code:
wine: WINEARCH set to win64 but '.wine' is a 32-bit installation
Sounds like a broken build/install.

I find that I have to install wine32 before wine64 (but I have to
build wine64 before wine32) when building a wow64 Wine, but I don't
know if that is still the case.
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Re: Is Wine64 usable yet?

Post by sniveri »

madewokherd wrote: Sounds like a broken build/install.

I find that I have to install wine32 before wine64 (but I have to
build wine64 before wine32) when building a wow64 Wine, but I don't
know if that is still the case.
Yep, that could be, cause I did not have that issue anymore when doing few more builds.

I did the latest test with this kind of procedure:

Code: Select all

mkdir wine64
cd wine64
../wine-git/configure --enable-win64
make
cd ..
mkdir wine32
cd wine32
../wine-git/configure --with-wine64=../wine64
make
make install
cd ..
cd wine64
make install
And now I`m able to install all kinds of applications but things like Net Framework and msxml6 can not be installed.. Net Framework 2.0 seems to need package that installs on both of the architectures simultaneously and I do not know what is the problem with msxml6.. But anyway this looks pretty amazing so far :)
User avatar
André H.
Moderator
Moderator
Posts: 207
Joined: Sun Dec 07, 2008 8:33 am

Post by André H. »

Further WINEARCH=wine64 does nothing!
it's WINEARCH=win32 (without the e, and 32)
Wine at the moment just checks for win32 and handles it if on 64-bit.
every other value like wine32 or wine64 are ignored and lead to wow setups :)

for compiling and installing, you have to build 64-bit before 32-bit (at least the tools/ folder of wine64 has to be done before you can start the wine32 build process) and i guess the installing can be every way, i mostly install wine64 before wine32 or both at the same time, never hurt.
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

André H. wrote:Further WINEARCH=wine64 does nothing!
it's WINEARCH=win32 (without the e, and 32)
Wine at the moment just checks for win32 and handles it if on 64-bit.
every other value like wine32 or wine64 are ignored and lead to wow setups :)
Yep, the format is documented to be "win32" or "win64".

I was able to install msxml6 to 64-bit environment when changed from XP -> Windows 2003 from winecfg. Setting it as Vista did not work so well.. SolidWorks 2010 x64 almost installs but fails to run, maybe it is related to GDI+ that does not install on wow64, it has the same thing as the dotnet20: installer tries to install some files to x64 and x86 sides and fails on some "update.exe" -problems..
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

Hmm.. is this "update.exe" problem same which is happening with ie7 in32-bit (needs some cat file copied somewhere to run)?

With wow64 build I have been testing to install SolidWorks 2009-2011 x64 and most of the times installer tries by default install the app to "Program Files (x86)"-folder, sometimes it gets correct program files folder, usually not. Installer fails on execution of regasms or something similar stuff, all the files are copied however. Seen the same regasm failure in many other x64 installers. Is the regasm actually part of the dotnet20?

Also SolidWorks needs both versions of gdiplus; 32 and 64 bit. It was a bit odd to me that the 64-bit version of gdiplus has to be copied to system32-folder and 32-bit version to syswow64 to make the "could not load gdiplus"-errors go away.

When starting up SolidWorks spmanager it flashes a messagebox: "could not load resource dll", but when using WINEDEBUG=+all, there is no errors before that messagebox. First thing with SolidWorks x64 would be to get the swspmanager.exe to tell what is his problem :D
Jetbird_D2
Level 2
Level 2
Posts: 13
Joined: Fri Mar 18, 2011 3:12 pm

Post by Jetbird_D2 »

Hello!

Are there nay speculation when WineHQ 64bit will be officially released?
I am new to Linux so compiling apps isn;t something for my brain, are there any chances to see 64 bit version officially released any time soon?
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

If you want to speculate, then there is already available some instructions for packagers: http://wiki.winehq.org/Wine64ForPackagers. However I haven`t found release schedule from anywhere, so maybe it will take some time. There is also a script for building wine64 wow64-setup for ubuntu available at somewhere on the internet.
User avatar
dimesio
Moderator
Moderator
Posts: 13369
Joined: Tue Mar 25, 2008 10:30 pm

Post by dimesio »

Jetbird_D2 wrote:Are there nay speculation when WineHQ 64bit will be officially released?
I am new to Linux so compiling apps isn;t something for my brain, are there any chances to see 64 bit version officially released any time soon?
Ask your distro; they're the ones who build the binaries. OpenSUSE and Fedora have provided 64 bit packages for some time now.
sniveri
Level 2
Level 2
Posts: 22
Joined: Mon Jan 25, 2010 5:43 am

Post by sniveri »

hmm.. regtlb seems to be working on both sides (32&64) but when trying to execute regasm on 64-bit side it fails for example:

Code: Select all

err:process:start_process L"C:\\windows\\Microsoft.NET\\Framework64\\v2.0.50727\\regasm.exe" doesn't have an entry point, it cannot be executed
when running command:

Code: Select all

wine64 regasm /codebase System.Drawing.dll
in folder: ~/.wine/drive_c/windows/Microsoft.NET/Framework64

in 32-bit side of framework the regasm works as expected. So this might be one of the issues why some of the recource dlls cannot be loaded as those must be registered to gac. Do not know if this is correct explanation for the issue, but somehow all the installers fails at the same situation: registering 64-bit assemblies.
Berillions
Level 4
Level 4
Posts: 230
Joined: Sat Mar 28, 2009 12:55 pm

Post by Berillions »

I built and package myself wine with WoW64 build.

I installed Assassin's Creed 1 without option WINEARCH=win32.
So, the game was installed on "Program File (x86) folder. To play entierly at game with wine 64bits, i must to use "wine" or "wine64" ?

Because with the first or the second, the game launch and run correctly. :wink:
Iceburgh69
Level 1
Level 1
Posts: 5
Joined: Sun Jan 10, 2010 11:37 am

Post by Iceburgh69 »

I'm having issues with getting Wine64 to even install properly. I'm using an AMD 64 processor with Fedora 14 x64. When I try to get things working, here's what I get with the gcc:


Touching configure...
[root@Iceburgh gcc-svn]# cd ..
[root@Iceburgh Iceburgh]# rm -rf gcc-build
[root@Iceburgh Iceburgh]# mkdir gcc-build
[root@Iceburgh Iceburgh]# cd gcc-build
[root@Iceburgh gcc-build]# ../gcc-svn/configure --prefix=/usr/local/gcc --enable-languages=c --disable-bootstrap
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/home/Iceburgh/gcc-build':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
[root@Iceburgh gcc-build]# make
make: *** No targets specified and no makefile found. Stop.

Also, it can't find ./configure anywhere, and I have no idea where to tell it to go to find it.

Ultimately, I'm trying to get DDO to work, but first I have to get Wine working. I'm a bit of a noob at this, so any help would be appreciated.
Iceburgh69
Level 1
Level 1
Posts: 5
Joined: Sun Jan 10, 2010 11:37 am

Post by Iceburgh69 »

...kinda wish I could edit my previous post. There's a bit more that I should've mentioned. Here's the script I was using:

#!/bin/sh
# Build gcc from trunk
# Enable just the C language (since that's all Wine needs)

sudo apt-get build-dep gcc
sudo apt-get install texi2html libgmp3-dev libmpfr-dev
svn checkout svn://gcc.gnu.org/svn/gcc/trunk gcc-svn
cd gcc-svn
contrib/gcc_update
cd ..
rm -rf gcc-build
mkdir gcc-build
cd gcc-build
../gcc-svn/configure --prefix=/usr/local/gcc --enable-languages=c --disable-bootstrap
make
sudo make install

Though I was using the su command instead of the sudo, since I didn't want to have to type in my pw every time I did something, so I edited the script accordingly. I've been following the instructions found at http://wiki.winehq.org/WineOn64bit#head ... 7b740fd886 for my distro, as well as http://forums.ddo.com/showthread.php?t=212618
User avatar
dimesio
Moderator
Moderator
Posts: 13369
Joined: Tue Mar 25, 2008 10:30 pm

Post by dimesio »

Iceburgh69 wrote:I'm having issues with getting Wine64 to even install properly. I'm using an AMD 64 processor with Fedora 14 x64. When I try to get things working, here's what I get with the gcc:

Touching configure...
[root@Iceburgh gcc-svn]# cd ..
[root@Iceburgh Iceburgh]# rm -rf gcc-build
[root@Iceburgh Iceburgh]# mkdir gcc-build
[root@Iceburgh Iceburgh]# cd gcc-build
[root@Iceburgh gcc-build]# ../gcc-svn/configure --prefix=/usr/local/gcc --enable-languages=c --disable-bootstrap
I'm not sure why you're trying to build gcc from source rather than just using whatever version is available in your distro's repository, but questions about how to do it have nothing to do with Wine.
sudo apt-get build-dep gcc
sudo apt-get install texi2html libgmp3-dev libmpfr-dev
Apt-get is for Debian-based systems; it won't work on Fedora.
I've been following the instructions found at http://wiki.winehq.org/WineOn64bit#head ... 7b740fd886 for my distro
Don't think so. Those instructions do NOT call for building gcc from source, and they clearly give the correct command for installing packages in Fedora (yum, not apt-get).
Locked