mariusvam / winetricks

Automatically exported from code.google.com/p/winetricks
3 stars 0 forks source link

[vcrun2010]Possible bug with Wine 64bits #334

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install vcrun2010 thanks to winetricks v20130707.

I think there a bug in winetricks file when you want install vcrun2010 into a 
64-bits wineprefix. 

In a 64-bits prefix, when you want to install this app with winetricks :
1- it install the 32-bits version in the first one 
2- Copy the 64-bits dlls 

At the first step, vcrun2010-x86 is installed so the 32-bits dlls are installed 
in the "system32" folder.

At the second step, winetricks copy the 64-bits dll into "$W_SYSTEM64_DLLS" 
folder. 

But if you see at line 3380 in the winetricks file :
- W_SYSTEM64_DLLS="$W_WINDIR_UNIX/system32"

Winetricks install the 64-bits dlls in the 32-bits folder, not the 64-bits 
folder.

To test, I installed vcrun2010 64-bits without winetricks, msvc100* dlls are 
installed into "syswow64" not "system32"

Max

Original issue reported on code.google.com by Berillions on 1 Aug 2013 at 6:18

GoogleCodeExporter commented 9 years ago
SysWOW64 is the 32-bit directory on Windows.
system32 is the 64-bit directory on Windows.

Illogical but true.

Original comment by ImWellCu...@googlemail.com on 1 Aug 2013 at 12:29

GoogleCodeExporter commented 9 years ago
Yep. You can verify the dlls are correct using 'file':
austin@aw25 ~/.wine/drive_c/windows $ file syswow64/*dll system32/*dll | grep 
msvcr100
syswow64/msvcr100.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
system32/msvcr100.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows

Original comment by austinenglish@gmail.com on 1 Aug 2013 at 11:22

GoogleCodeExporter commented 9 years ago
Thanks Austin but there is something that i don't understand. If "system32" 
folder is the 64-bits directory, why when i install vcrun2010 64-bits directly 
by wine (don't use winetricks), the 64-bits are installed into "syswow64" 
directory ?

Original comment by Berillions on 2 Aug 2013 at 6:12

GoogleCodeExporter commented 9 years ago
Because there's a wine bug:
http://bugs.winehq.org/show_bug.cgi?id=30713

Original comment by austinenglish@gmail.com on 2 Aug 2013 at 4:58