3 Aug
2005
3 Aug
'05
7:31 p.m.
Hi!
I can install Xchat 2.4.4 from http://www.silverex.org/news/.
It look horrible but it does run with some exceptions. One, you may have to
start the app from it's lib directory, "..\xchat". I do not have a screen-
shot 8^P. But here is a debug print, this does not happen often, only when
exiting the app from the X button. It looks like something I posted before.
GTK+ apps are starting to work under ROS, this alone should speak volumes!
Btw! We need to implement NtGdiOffsetClipRgn, I dont care if it is a haxed wine
port, atleast something. Bitmap seems broken too.
X-Chat,
WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME
NTED!
WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME
NTED!
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(lib/comctl32/toolbar.c:416) bitmap for ID 0, index 1 is not valid, number of bi
tmaps in imagelist: 0
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(subsys/win32k/objects/gdiobj.c:545) GdiHdr->Locks: 1
Assertion 'FALSE' failed at subsys/win32k/objects/gdiobj.c line 549
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x9dcf622e,0x00000009)
*** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0
Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())>
cr2 77ee23f6 cr3 20c91000 Proc: 817108e0 Pid: 128 <gtk2_prefs.exe> Thrd: 81c744b
8 Tid: 120
DS 10 ES 10 FS 30 GS 0
EAX: 00000044 EBX: 000000d5 ECX: 00000000
EDX: 000003f8 EBP: 9db53c14 ESI: 0068fec0 ESP: 9db53b84
EDI: 9db53d74 EFLAGS: 00000292 kESP 9db53b84 kernel stack base 9db51000
Frames:
<win32k.sys:802b8 (subsys/win32k/objects/gdiobj.c:549 (GDIOBJ_FreeObj))>
<win32k.sys:805d2 (subsys/win32k/objects/gdiobj.c:670 (GDI_CleanupForProcess))>
<win32k.sys:3aea3 (subsys/win32k/main/dllmain.c:102 (Win32kProcessCallback))>
<ntoskrnl.exe:82c0e (ntoskrnl/ps/win32.c:99 (PsTerminateWin32Process))>
<ntoskrnl.exe:7a5f2 (ntoskrnl/ps/kill.c:295 (PspExitThread))>
<ntoskrnl.exe:7ad74 (ntoskrnl/ps/kill.c:593 (NtTerminateProcess))>
<ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))>
<kernel32.dll:32142 (lib/kernel32/process/proc.c:592 (ExitProcess))>
gdi32_crosstest bitmap,
(subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete
d!
(subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete
d!
(subsys/win32k/objects/gdiobj.c:939) Attempted to lock object 0x0 that is delete
d!
Assertion 'Dest != NULL && Source != NULL && DestRect != NULL
&& SourcePoint !=
NULL' failed at subsys/win32k/eng/copybits.c line 53
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x00000296,0x0a32ec37)
*** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0
Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())>
cr2 930000 cr3 3aeda000 Proc: 816eb508 Pid: 120 <gdi32_crosstest> Thrd: 816f63c0
Tid: 124
DS 10 ES 10 FS 30 GS 0
EAX: 00000085 EBX: 0000106a ECX: 00000000
EDX: 000003f8 EBP: 9f32e8c0 ESI: 006cee54 ESP: 9f32e830
EDI: 9f32ed74 EFLAGS: 00000282 kESP 9f32e830 kernel stack base 9f32c000
Frames:
<win32k.sys:30ce0 (subsys/win32k/eng/copybits.c:53 (EngCopyBits))>
<win32k.sys:7a1e3 (subsys/win32k/objects/dib.c:508 (NtGdiGetDIBits))>
<ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))>
<gdi32_crosstest.EXE:565c>