http://bugs.winehq.org/show_bug.cgi?id=10601
--- Comment #32 from Anastasius Focht focht@gmx.net 2009-10-06 14:42:43 --- Hello,
--- quote --- Antasius Focht states: "...this specific problem is worked around by commit 8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see comment #15 for analysis." Great - and what are the APPROPRIATE steps to work around the installer crashing? --- quote ---
That comment was referring to an earlier state of the bug. Commit 8044c11ecfca09e2b643feccb95a4d8f645ba656 was reverted because it caused other apps to fail (defaulting to fat32 would have been the better choice as some Windows apps can't cope with unixfs).
Anyway, if winetricks .NET 2.0 install worked for you before (<1.1.30), please do regression test to identify the commit that broke it.
http://wiki.winehq.org/RegressionTesting
If you don't want to go though that process you could produce a debug log for regsvcs.exe bootstrapping process (which is probably the one crashing here).
1. run winetricks dotnet20 on clean WINEPREFIX, dismiss the crash handler and installer dialog (if any), wait a bit. 2. open console, kill any lingering wine processes if present (wineserver -k) 3. make sure Wine version is (still) set to "Windows 2000" (winecfg) 4. run the following in console (and dismiss crash handler again):
WINEDEBUG=+tid,+seh,+relay wine "C:\windows\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe" /bootstrapi &> log.txt
compress the resulting log with 'bzip2 -9 log.txt' and attach the file 'log.txt.bz2'.
Though you're probably better off with regression testing because bugs emerging from managed executables are hard to diagnose looking only at logs if developers can't reproduce/debug it (code is jitted at this point).
Regards