You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
# Start with an empty WinePrefix...
export WINEPREFIX=$HOME/.wine-directx9
# Install .NET Framework 2.0
winetricks -q dotnet20
# Regedit starts normally
wine regedit
# Install directx9 (NOTE: -q, quiet mode, not implemented?)
winetricks -q directx9
# NOTE: You need a delay here so that winedevice shuts down. A wineboot does
the job, too.
sleep 10
# Running regedit this time you'll get the error:
# The program mscorsvw.exe has encountered a serious problem and needs to
close. We are sorry for the inconvenience.
wine regedit
What is the expected output? What do you see instead?
Would expect wine regedit to start without error dialogs. (Note that the error
dialog is coming from wine startup, not from regedit.)
What version of the product are you using? On what operating system?
Ubuntu 10.10 Maverick Meerkat
wine-1.3.13
winetricks 20110123
Please provide any additional information below.
The last couple of lines of winetricks' load_directx9() function are:
# reenable mscoree, or other installs may fail, see issue 25
w_override_dlls builtin,native mscoree
Doing this, however, clobbers mscoree as used by .NET Framework 2.0. Whenever
you try to start Wine (even for something like winecfg) the ".NET Runtime
Optimization Service v2.0.50727_X86" service fails to start with the following
error message:
The program mscorsvw.exe has encountered a serious problem
and needs to close. We are sorry for the inconvenience.
Working around the problem:
Start winecfg, go to the Libraries tab and change the override from "*mscoree
(builtin, native)" to "*mscoree (native)". The error message goes away.
Original issue reported on code.google.com by [email protected] on 17 Feb 2011 at 10:34
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 17 Feb 2011 at 10:34The text was updated successfully, but these errors were encountered: