Hi,
I imported function ReplaceFileW from Wine, but it do not work in ReactOS.
RepleceFileW there do not pass 11 tests (kernel32_winetest file). I think,
that a problem in call MoveFileEx. Somebody can help with it?
Function in Wine: http://www.reactos.org/paste/index.php/2745/
Patch for ReactOS: http://www.reactos.org/paste/index.php/2744/
--
WBR,
Dmitry Chapyshev
Hi ALL!
Okay, not sure what is going on but here is the original output:
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 682000
Address: 7c91e6ae C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c91e6ae
DS 23 ES 23 FS 3b GS 0
EAX: 011f0020 EBX: 011f0020 ECX: 090b071d
EDX: 242c2c64 EBP: 008afc54 ESI: 00681ffe ESP: 008afc4c
EDI: 011f1010 EFLAGS: 00010212
Frames:
77e30000+211d2 C:\ReactOS\system32\user32.dll
77e30000+21365 C:\ReactOS\system32\user32.dll
77e30000+20c56 C:\ReactOS\system32\user32.dll
400000+892c C:\ReactOS\user32_crosstest.exe
400000+8e73 C:\ReactOS\user32_crosstest.exe
400000+a3ab C:\ReactOS\user32_crosstest.exe
400000+b4ac8 C:\ReactOS\user32_crosstest.exe
400000+b4c56 C:\ReactOS\user32_crosstest.exe
400000+1247 C:\ReactOS\user32_crosstest.exe
400000+1298 C:\ReactOS\user32_crosstest.exe
7c700000+218e4 C:\ReactOS\system32\kernel32.dll
(subsystems/win32/csrss/api/wapi.c:115) CSR: received hard error c0000144
(subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at
"0x7c91e6ae" referenced memory at "0x00682000". The memory could not
be "read".
After patch:
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
Than, get two exit strings at the command console.
bi -> 6819854 (0x68100E) is the one and it is from MapViewOfFile. The
difference from 0x682000 is 4082.... Well with in the normal page but
why is 0x68100E the start address and not 0x681000?
It could be just simply bad math being used in LoadBitmapImage. Wine
does use the same code in user32 from gdi32 to handle bitmap and
friends.
Thanks,
James
Hi rosdevs!
This is an issue I've been working on for a while on the Wine side of
things and now they have initial support for it. If any of you
Win32k/GDI hackers are interested in making ReactOS look a bit better
on LCDs please enable support in freetype and review the following
Wine patch to get an idea of the requirements.
Thanks
http://source.winehq.org/git/wine.git/?a=commitdiff;h=028617b90ba586bdb3072…
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
Mozilla Firefox 2.0: install it, run it, then quit - total hang
without KDBG or any exception, TAB+K doesn't work.
Then, reboot - try to navigate via Start Menu to Applications ->
Mozilla Firefox. Explorer will die with exception in dll/win32/user32/
misc/exticon.c:88 (find_entry_by_id). Maybe due to files corruption.
WBR,
Aleksey.
tkreuzer(a)svn.reactos.org wrote:
> For some unknown reason wmc likes to include string.h from the wine folder
and we cannot link it on linux hosts. This hack should hopefully resolve the
issue.
Not that mysterious actually.
The "include/reactos/wine" directory is shared among Wine host and target
tools while "include/crt" contains target-only headers and thus it's only
available for target components.
Therefore #include_next cannot find any other "string.h" file, when you use
it inside host tools. Furthermore, #include_next is a GCC-only thing, so we
should avoid it wherever possible.
To circumvent these problems and remove the hacks from the actual CRT/PSDK
headers, I propose we i.e. add '#include <reactos/wine/string.h>' to the CRT
"string.h" and do the appropriate thing for other files.
This is the prettiest solution I can think of without editing a bunch of
Wine files.
Best regards,
Colin
Sooner or later, this problem should be solved somehow. And not only for
Armenians, but also for other peoples of the world, who live without code
pages.