Hello, while working with EAC, I tracked down an error to EAC requiring the ntdll.dll it has read from system32 being over 4095 bytes in size. For some reason, it seems that the fake dlls have recently dropped in size, and consist of only a header. EAC also reads the export table later on and checks for mov instructions that are present in the old fake DLLs.
----- On Apr 30, 2019, at 7:35 AM, Derek Lesho [email protected] wrote:
Hello, while working with EAC, I tracked down an error to EAC requiring the ntdll.dll it has read from system32 being over 4095 bytes in size. For some reason, it seems that the fake dlls have recently dropped in size, and consist of only a header. EAC also reads the export table later on and checks for mov instructions that are present in the old fake DLLs.
Could this possibly be related to something with MinGW? Around wine-4.4/4.5 MinGW was "enabled" for some cross-compile of PE-files (fake-dll's perhaps is compiled with MinGW?). I have not really studied it, and stopped using it due to various errors with recent wine (latest was some build problems with MinGW enabled).
Could you perhaps try to use the " --without-mingw" configure option if you compile yourself?
If you use the WineHQ pre-compiled binaries, i think this is compiled without using MinGW (atleast for Debian based distros).
Sveinar
Sveinar Søpler [email protected] writes:
----- On Apr 30, 2019, at 7:35 AM, Derek Lesho [email protected] wrote:
Hello, while working with EAC, I tracked down an error to EAC requiring the ntdll.dll it has read from system32 being over 4095 bytes in size. For some reason, it seems that the fake dlls have recently dropped in size, and consist of only a header. EAC also reads the export table later on and checks for mov instructions that are present in the old fake DLLs.
Could this possibly be related to something with MinGW? Around wine-4.4/4.5 MinGW was "enabled" for some cross-compile of PE-files (fake-dll's perhaps is compiled with MinGW?). I have not really studied it, and stopped using it due to various errors with recent wine (latest was some build problems with MinGW enabled).
The plan is to build fake dlls with MinGW, but that's not enabled yet.
At this point nothing has changed. The fake dlls that contain an export table were most likely generated by wine-staging. Main wine doesn't do that yet.
On Tue, 30 Apr 2019 08:35:18 +0200 (CEST) Sveinar Søpler [email protected] wrote:
If you use the WineHQ pre-compiled binaries, i think this is compiled without using MinGW (atleast for Debian based distros).
That is correct; the build failed when I tried it with MinGW.
Rosanne DiMesio [email protected] writes:
On Tue, 30 Apr 2019 08:35:18 +0200 (CEST) Sveinar Søpler [email protected] wrote:
If you use the WineHQ pre-compiled binaries, i think this is compiled without using MinGW (atleast for Debian based distros).
That is correct; the build failed when I tried it with MinGW.
It would be a good idea to fix this if possible. What error did you get, and with what MinGW version?
On Tue, Apr 30, 2019 at 3:17 AM Alexandre Julliard [email protected] wrote:
The fake dlls that contain an export table were most likely generated by wine-staging.
Ah, it looks like you're right, I was comparing the fake dlls to my system wine version, which looks like was staging. My bad.
-
Alexandre Julliard -
Derek Lesho -
Rosanne DiMesio -
Sveinar Søpler