The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Nothing
What does not
The program does not work at all. It gives the following error whenever you attempt to run it:
err:ntdll:RtlpWaitForCriticalSection section 0x7efece04 "loader.c: loader_section" wait timed out in thread 0012, blocked by 0011, retrying
(60 sec)
Couldn't inject dll.
err:seh:raise_exception Unhandled exception code c0000194 flags 0 addr 0x7ef93f60
I have emailed Ian Patterson, one of the program's authors, about the problem, and he gives this as his response:
This appears to be a discrepancy between the Windows implementation of
the DLL dependency handler/loader and the Wine implementation.
Unfortunately I don't have a linux install to test this on, but my
first guess would be that calling CreateProcess with the
CREATE_SUSPENDED flag set leaves the new process' loader critical
section locked until the main thread is resumed.
The loader works in a pretty straightforward way:
- create the new process with CREATE_SUSPENDED
-
VirtualAllocEx some executable memory in the new process to store
enough code for "jmp LoadLibraryA" and a null-terminated string
pointing to our DLL (in a perfect world we would just point the thread
entry point straight at LoadLibraryA, but this makes some virus
scanners explode, literally)
- use CreateRemoteThread to create a thread in the new process pointing
to the injected code, setting the parameter to the thread function to
the DLL path in the new process (conveniently the calling convention
and signature of thread entry points and LoadLibrary are exactly the
same)
- wait for the thread to terminate, signifying that the DLL has been loaded
- clean up
This sequence requires that processes not be holding the loader lock immediately after creation.
Do Not Load Directly
by Lampros Liontos on Saturday August 20th 2011, 23:35
To those who are seeing error messages when launching obse_loader.exe, this may help:
Do not launch the loader directly with "wine obse_loader.exe", as this will cause the application to crash. However, launching it with a third-party tool, such as Wrye Bash, will allow the launcher to work. I have not seen any issues; nGCD and Progress seem to perform as expected.
