Installing dotnet 2.0 on 64 bit machine
Solution 1
You can have multiple wine prefix on your machine, each running as a separate wine. So you can make a 32 bits prefix and install dotnet2 in it:
This will create a new wineprefix (.wine32 in your home) and configure it as 32 bits:
WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
You can use it this way combined with winetricks to configure WINEARCH, create the prefix and install dotnet 2.0 in one command:
env WINEARCH=win32 WINEPREFIX=~/.wine32 winetricks dotnet20
or only:
env WINEPREFIX=~/.wine32 winetricks dotnet20
if you already set the WINEARCH and created the WINEPREFIX with the 1st command above.
Solution 2
just to make it more straightforward to use wine in 32bit mode. Create a file in ~/bin/wine32 with the following content
env WINEARCH=win32 WINEPREFIX=~/.wine32 wine $*
Make the file executable to launch wine in 32bit mode using
wine32 my_exe_file_that_needs_32bit.exe
Hope that helps :-)
Wayne Len
Updated on September 18, 2022Comments
-
Wayne Len over 1 year
I have a speed-reading program I purchased with uses dotnet2. However, dotnet2 doesn't run on 64 bit wine. How would I install dotnet2?
-
Wayne Len over 11 yearsThanks. . . How would you install the program to that prefix?
-
laurent over 11 years
WINEPREFIX=~/.wine32 wine setupprogram.exe
-
jaorizabal almost 11 years@laurent how do you uninstall programs in that prefix?
-
laurent almost 11 yearsIf the program has an uninstall, you can run it the same way. If not... you can remove the directory (or the files) where your program is installed (
~/.wine32/drive_c/Program Files/your_program
or something similar) -
Ryan over 10 yearsThe first command is wrong, the WINEPREFIX should be ~/.wine32 not ~/.win32,
WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
-
laurent over 10 yearsYou can give to it the name you want (and use the same name in other commands) but sure, I will make it consistent with the other examples.
-
Wayne Len over 10 years@laurent dotnet2.0 is failing to install. It keeps asking if I want to send the report to Microsoft.
-
Stephen Angelico almost 9 yearsRather than making a script in ~/bin (which I think is a security problem anyway), you could make a bash alias in ~/.bashrc. Just take the same line from the script and put it in a line in .bashrc like this: alias wine32='env WINEARCH=win32 WINEPREFIX=~/.wine32 wine $*'
-
laurent over 8 yearsSorry for the long delay (2 years!) but dotnet2.0 is out of support since 2010 so I guess it is normal it doesn't install nicely anymore (support.microsoft.com/en-us/lifecycle/search/…). The process described above should still be valid to install any application in a different wine prefix or architecture.