Uwe Bonnes [EMAIL PROTECTED] writes:
at present, wine e.g. crashes if it finds user32.dll in the same directory
as the executable. To keep wine from using this DLL, the dos-path to that
dll has to be given explicit to the -dll argument, like
wine h:/tmp/programm.exe --dll
Alexandre == Alexandre Julliard [EMAIL PROTECTED] writes:
Alexandre Uwe Bonnes [EMAIL PROTECTED] writes:
at present, wine e.g. crashes if it finds user32.dll in the same
directory as the executable. To keep wine from using this DLL, the
dos-path to that dll has to be given
Uwe Bonnes [EMAIL PROTECTED] writes:
There are two cases:
- windows/system is populated with some executables. Calling them directly
causes immediate crash
Only if windows/system is not configured as system directory. I don't
see why you'd want to do that.
- for testing, I had
Alexandre == Alexandre Julliard [EMAIL PROTECTED] writes:
Alexandre Uwe Bonnes [EMAIL PROTECTED] writes:
There are two cases: - windows/system is populated with some
executables. Calling them directly causes immediate crash
Alexandre Only if windows/system is not configured
Uwe Bonnes [EMAIL PROTECTED] writes:
Several possibilities:
- several versions of winxx are available. You are trying to run one
executable in the context of another system
- you have an empty windows/system directory and want to run application
from the windows/system directory of the
Alexandre == Alexandre Julliard [EMAIL PROTECTED] writes:
Alexandre Uwe Bonnes [EMAIL PROTECTED] writes:
Several possibilities: - several versions of winxx are available. You
are trying to run one executable in the context of another system -
you have an empty windows/system
Uwe Bonnes [EMAIL PROTECTED] writes:
Only for my understanding: Can you give (an) example(s) where the present
behaviour is usefull against the non-granulat approach.
There are cases where applications come with their own replacements
for system dlls, for one reason or another. This happens a
