http://bugs.winehq.org/show_bug.cgi?id=16956
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net 2009-01-16 15:33:21 --- Hello,
without further log files my educated guess is that the main application installer runs some custom action after .NET 2.0 SP1 installer execution to verify if .NET 2.0a/SP1 is really installed which should ideally fail if the check is done thoroughly.
Running .NET 2.0 SP1 installer alone on WINEPREFIX with .NET 2.0 present (using winetricks) should (incorrectly) report success.
Thanks for reporting this, I really forgot about this issue some time ago.
The problem is actually msi insufficiency when it comes to determining the list of applicable patches (type, patch sequence order and status) which should be passed to sub-installer (see MsiDetermineApplicablePatchesA/W).
MSDN http://msdn.microsoft.com/en-us/library/aa370084.aspx for more info.
BTW .. that winetricks 'winxp' step is unnessary. Wine winver defaults to XP and should be reset properly after winetricks steps (unless you use broken winetricks script).
Regards