dotnet20sp1 should be affected by Wine Bug 34207 but it doesn't seem to get
this far.
http://bugs.winehq.org/show_bug.cgi?id=34207
Following a successful dotnet20 installation:
winetricks -q dotnet20sp1
Executing w_do_call dotnet20sp1
Executing load_dotnet20sp1
Current wine does not have wine bug 16956, so not applying workaround
Executing w_do_call dotnet20
dotnet20 already installed, skipping
------------------------------------------------------
Setting windows version so installer works
------------------------------------------------------
Setting Windows version to win2k
Executing winetricks_early_wine regedit /S
C:\windows\Temp\_dotnet20sp1\set-winver.reg
wine: cannot find
L"C:\\windows\\Microsoft.NET\\Framework\\v2.0.50727\\mscorsvw.exe"
fixme:service:scmdatabase_autostart_services Auto-start service
L"clr_optimization_v2.0.50727_32" failed to start: 2
ADD - HKLM\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727 Version 0
REG_SZ 2.0.50727 1
The operation completed successfully
fixme:clusapi:GetNodeClusterState ((null),0x33ebb4) stub!
fixme:advapi:DecryptFileA ("y:\\d9abe31837b52ee938dc\\", 00000000): stub
Setting Windows version to winxp
Executing winetricks_early_wine regedit /S
C:\windows\Temp\_dotnet20sp1\set-winver.reg
------------------------------------------------------
dotnet20sp1 install completed, but installed file
/home/test/.wine/dosdevices/c:/windows/winsxs/manifests/x86_Microsoft.VC80.CRT_1
fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2.cat not found
------------------------------------------------------
The console logs are very different to the logs in the bug even though I'm
using the same setup.
To make matters worse it breaks a successful manual install of dotnet20sp1.
This becomes a problem because dotnet35sp1 (for example) calls the dotnet20sp1
script.
Dotnet Verifier confirms.
The workaround is to remove
$WINESERVER -k
and
$WINESERVER -w
from the dotnet20sp1 recipe.
Winetricks then experiences Wine Bug 34207 and has to be run again, which
completes successfully.
Original issue reported on code.google.com by ImWellCu...@gmail.com on 5 Aug 2013 at 3:53
Original issue reported on code.google.com by
ImWellCu...@gmail.com
on 5 Aug 2013 at 3:53