Closed GoogleCodeExporter closed 9 years ago
UPDATE: Due to install problems in previous runs, I was trying to install
dotnet30sp1 step-by-step. That is,
1. winetricks dotnet20sp1
2. winetricks dotnet30sp1 => this is where setup would fail.
Instead, installing dotnet30sp1 directly works correectly, because: $
winetricks dotnet30sp1
results in install order as: dotnet20 => dotnet30 => dotnet20sp1: Install
completes
Next step however (winetricks dotnet35 OR dotnet35sp1) stops as below. What
install sequence should I use in order to get to a dotnet35/dotnet35sp1
environment?
Executing w_do_call dotnet30sp1
Executing load_dotnet30sp1
Executing w_do_call dotnet30
dotnet30 already installed, skipping
Executing w_do_call dotnet20sp1
dotnet20sp1 already installed, skipping
ADD - HKLM\Software\Microsoft\Net Framework Setup\NDP\v3.0 Version 0 REG_SZ 3.0
1
The operation completed successfully
ADD - HKLM\Software\Microsoft-\Net Framework Setup\NDP\v3.0 SP 0 REG_DWORD 0001
1
The operation completed successfully
Executing wine msiexec /i XPSEP XP and Server 2003 32 bit.msi
------------------------------------------------------
Note: command 'wine msiexec /i XPSEP XP and Server 2003 32 bit.msi' returned
status 2. Aborting.
Original comment by r...@berentweb.com
on 11 Aug 2013 at 7:58
Correct the above issue by editing winetricks.sh, line 4923
-- w_try $WINE msiexec /i "XPSEP XP and Server 2003 32 bit.msi"
${W_OPT_UNATTENDED:+/qb}
++ w_try $WINE msiexec /i "XPSEP%20XP%20and%20Server%202003%2032%20bit.msi"
${W_OPT_UNATTENDED:+/qb}
Regards.
Original comment by r...@berentweb.com
on 11 Aug 2013 at 8:20
That is already fixed in SVN:
https://code.google.com/p/winetricks/source/detail?r=1038
Original comment by austinenglish@gmail.com
on 12 Aug 2013 at 6:34
Don't have this problem in current winetricks
Should this issue be closed?
Original comment by litimetal
on 2 Oct 2014 at 12:26
Old issue & was corrected AFAIK. Should be closed (I can't do it as reg user).
Original comment by r...@berentweb.com
on 3 Oct 2014 at 11:05
Fixed.
Original comment by austinenglish@gmail.com
on 7 Oct 2014 at 7:37
Original issue reported on code.google.com by
r...@berentweb.com
on 10 Aug 2013 at 8:45