Installation of WMP10 fails on first attepmpt

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run winetricks wmp10 using latest wine
2. Proceed with installation, it should fail
3. Run winetricks wmp10 again, now it installs correctly

What is the expected output? What do you see instead?
Installation of WMP10

What version of the product are you using? On what operating system?
I tested this using wine 1.7.4, Ubuntu 13.10 64Bit

Please provide any additional information below.
Works OK on wine 1.6

Original issue reported on code.google.com by mate...@gmail.com on 11 Nov 2013 at 10:24

[GoogleCodeExporter]

I'm regression testing this using git bisect. I'll put a result soon.

Original comment by mate...@gmail.com on 12 Nov 2013 at 9:08

[GoogleCodeExporter]

I found commit which brakes brakes installation process:

621454ef0ed37c19c917aa1aa6dba66e163e07d8 is the first bad commit
commit 621454ef0ed37c19c917aa1aa6dba66e163e07d8
Author: Hans Leidekker <hans@codeweavers.com>
Date:   Wed Oct 2 16:04:19 2013 +0200

    wine.inf: Initialize 64-bit prefixes with the right Windows version.

:040000 040000 2eaccc9b4062a8dacf278f114064074061ad7c83 
e1ebf42976441e6314a9a24ff667df2474d44e23 M      tools

From diff I found that default Windows version changed on 64bit systems from 
Windows XP to Windows XP 64bit. Is it bug of winetricks or should I create bug 
report in wine bugzilla?

Original comment by mate...@gmail.com on 12 Nov 2013 at 11:16

[GoogleCodeExporter]

I modified winetricks script locally by adding:
w_set_winver winxp
at the beginning of load_wmp10 function. It helped, WMP10 installed (with 
codecs). It seems that WMP10 installer doesn't support Windows XP 64bit, which 
is default on 64bit prefixes now. It makes sens, because WMP10 was bundled 
together with Windows XP 64bit (which was modified Windows 2003).

Original comment by mate...@gmail.com on 13 Nov 2013 at 10:36

[GoogleCodeExporter]

Running w_set_winver (or any windows version) on a 64-bit prefix is likely to 
break things even worse.

I assume it works in a 32-bit wineprefix?

Original comment by austinenglish@gmail.com on 13 Nov 2013 at 7:14

[GoogleCodeExporter]

I know that setting 32bit windows version on 64bit prefix is ugly hack, but in 
this case it is an only option. Probably issue 372 is caused by wrong (32bit) 
version of windows set.

Yes, while running something like this:

rm -rf /home/konrad/.local/share/wineprefixes/wmp10/
export WINEARCH=win32 && export 
WINEPREFIX=/home/konrad/.local/share/wineprefixes/wmp10 && wineboot && 
winetricks prefix=wmp10 wmp10 

everything works as expected. WMP10 installs with codecs. The problem is that 
on Ubuntu 64bit (probably in other distros too) wine by default creates 64bit 
prefixes.

BTW, looks like w_set_winver always sets 32bit windows version, so winetrick 
will break 64-bit prefixes in few other verbs too. In fact wmp10 changes 
windows version too, as it runs w_unset_winver function, which calls 
w_set_winver winxp. Thats why on second run wmp10 installs on 64bit prefixes 
and leaves prefix in broken state (as a side effect).

Personally I don't miss WMP, but some games need WMV codecs to play in-game 
videos, for example: "Call of Juarez: Gunslinger" 
(http://appdb.winehq.org/objectManager.php?sClass=application&iId=15187).

Preferably, winetricks should revert windows version to original one in 
w_unset_winver function. Then it would be possible to set 32bit version 
temporally and revert to original 64 bit at the end. Second option is to add 
support for 64bit versions in w_set_winver. In any case I'll try to help.

Original comment by mate...@gmail.com on 13 Nov 2013 at 10:00

[GoogleCodeExporter]

Well, using a 32-bit wineprefix isn't a hack, it's sometimes the only option 
(such as here were the application doesn't work in a 64-bit prefix).

Note that winetricks doesn't fully support 64-bit prefixes. I'm working on that 
as I have time, but I don't have a lot of that nowadays.

I'll add a check for this in wmp10.

Original comment by austinenglish@gmail.com on 13 Nov 2013 at 11:10

[GoogleCodeExporter]

This issue was closed by revision r1077.

Original comment by austinenglish@gmail.com on 13 Nov 2013 at 11:12

• Changed state: Fixed