Ros-dev December 2005

ros-dev@reactos.org

81 participants
142 discussions

by Hartmut Birr

Hi, I've fixed Alex' win32k changes. First, I try to commit the original changes. I've used 'svn merge -r20366:20368 svn://svn.reactos.org/trunk/reactos' to get the changes and I'm using 'svn commit' to commit the changes again. I get an error message: I:\Sandbox\ros_work\reactos>svn commit Lösche include\win32k\bitmaps.h <snip> Sende w32api\include\wingdi.h Übertrage Daten ................svn: Übertragen fehlgeschlagen (Details folgen): svn: Source url 'svn://svn.reactos.org/trunk/reactos/include/win32k/ntgdibad.h' is from different repository svn: Ihre Log-Meldung wurde in einer Temporärdatei abgelegt: svn: 'I:/Sandbox/ros_work/reactos/svn-commit.2.tmp' Usually, I get all error messages in german. What do I make wrong? - Hartmut

19 years, 3 months

Re: [ros-diffs] [ion] 20436: - Fix InterlockedBitTestAndReset and InterlockedBitTestAndSet

by Thomas Weidenmueller

ion(a)svn.reactos.org wrote: > + /* Value changed... wait until it's locked */ > + while (*SpinLock == 1) YieldProcessor(); This might be optimized away since SpinLock was not defined as volatile KSPIN_LOCK* - Thomas

19 years, 3 months

Re: [ros-diffs] [greatlrd] 20421: some case from win32k can call to RtlClearAllBits with NULL pointer. and check for null pointer after RtlClearAllBits. This take care of those case for moment.

by Thomas Weidenmueller

greatlrd(a)svn.reactos.org wrote: > some case from win32k can call to RtlClearAllBits with NULL pointer. and check for null pointer after RtlClearAllBits. This take care of those case for moment. This change is wrong, please revert it and fix win32k instead. - Thomas

19 years, 3 months

Re: [ros-diffs] [ion] 20366: - Added support for NTLDR style freeloader GUI. To enable, edit freeldr.ini and add:

by Hartmut Birr

ion(a)svn.reactos.com wrote: > - Also made the boot-up screen black, not blue, since that's the actual color it's been after NT4. If booting without NOGUIBOOT, this results in a much nicer transition to the boot screen (especially if using the NTLDR theme) > This changes the 'blue screen of death' to a 'black screen of death'. I don't like it if you change every and any thing to the real windows implementation. I see no reason for this cloning. - Hartmut

19 years, 3 months

Re: [ros-bugs] [Bug 399] OpenOffice Metabug

by WaxDragon

Why was this done? Having these bugs listed as blockers to 399 allows devs to find the old bugs easier in case of regressions. I don't see any downsize to keeping them listed. On 12/28/05, ReactOS.Bugzilla(a)reactos.org <ReactOS.Bugzilla(a)reactos.org> wrote: > http://www.reactos.org/bugzilla/show_bug.cgi?id=399 > > > greatlord(a)reactos.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > BugsThisDependsOn|398, 400, 937 | > > > > > ------- Additional Comments From greatlord(a)reactos.com 2005-12-28 17:54 CET ------- > Bug 398 are fixed, Bug 400 are fixed, Bug 937 are fixed > I remove tuse from Bug depends on. > > > > -- > Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > You are the QA contact for the bug, or are watching the QA contact. > _______________________________________________ > Ros-bugs mailing list > Ros-bugs(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-bugs > WD -- <Russell> argh <Russell> iterator shenanigans :/

19 years, 3 months

Re: [ros-svn] [ion] 20367: - Major Win32k Header Cleanup: Add ntgdi.h based on latest Platform SDK Public header. It contains the official definitions for NtGdi APIs.

by Hartmut Birr

ion(a)svn.reactos.com wrote: > - Major Win32k Header Cleanup: Add ntgdi.h based on latest Platform SDK Public header. It contains the official definitions for NtGdi APIs. > - Added ntgdityps.h for structures needed to use the header (which were sadly not publically shipped). > - Removed internal win32k header data from public headers and put it to internal win32k headers. > - Fixed ntuser.h STDCALL->WINAPI. > - Added ntgdihdl.h for shared GDI Handle information between gdi32/win32k > - Added ntusrtyp.h for some shared NtUser types. > - Added ntgdibad.h which contains all non-compatible NtGdi prototypes, along with a detailed comment for each, and information on how to fix it. I had a 20 000+ line patch fixing all these issues, but it contained many bugs and I scrapped it in place for this approach, which while dirtier at first, simplifies the number of changes needed so that others can work on it as well. > - Fixed some gdi32/win32k/user32 header issues. > > This change breaks running ros on qemu and real hardware. I don't see a mouse cursor after the gui is started. If I move the mouse, ros does crash. If I don't move the mouse, ros starts up to the first device install dialog. After this ros terminates itself and does switch off the computer. - Hartmut (ntoskrnl\mm\mm.c:317) Address: 87dcf974 Unhandled exception ExceptionCode: c0000005 Faulting Address: 87dcf974 Address: 77e9238b C:\ReactOS\system32\user32.dll CS:EIP 1b:77e9238b DS 23 ES 23 FS 3b GS 0 EAX: 87dcf974 EBX: 0144fdec ECX: 0144ffb4 EDX: f000ff53 EBP: 0144fb6c ESI: 00000000 ESP: 0144fb24 EDI: 00000000 EFLAGS: 00000246 Frames: 77e50000+2f461 C:\ReactOS\system32\user32.dll 77e50000+2fdf6 C:\ReactOS\system32\user32.dll 77e50000+31fb6 C:\ReactOS\system32\user32.dll 10000000+72cf C:\ReactOS\system32\win32csr.dll 77e50000+52657 C:\ReactOS\system32\user32.dll 77e50000+53a52 C:\ReactOS\system32\user32.dll 7c900000+a15b C:\ReactOS\system32\ntdll.dll 10000000+764e C:\ReactOS\system32\win32csr.dll 7c800000+2fe1d C:\ReactOS\system32\kernel32.dll (./subsys/win32k/ntuser/window.c:581) thread cleanup: while destroy wnds, wnd=0x870d11a4 (subsys\win32k\main\dllmain.c:281) thread clean: remove reference obj 0x870d11a4 (subsys\win32k\main\dllmain.c:281) thread clean: remove reference obj 0x870d11a4 KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:1242 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: win32k.sys Technical information: *** STOP: 0x0000001E (0xc0000005,0x9da2ba1f,0x00000000,0xfffffff4) *** win32k.sys - Address 0x9da2ba1f base at 0x9d99b000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:9da2ba1f <win32k.sys:90a1f (./subsys/win32k/ntuser/msgqueue.c:271 (co_MsqTranslateMouseMessage))> cr2 fffffff4 cr3 f58c000 Proc: 80ac2050 Pid: 7c <csrss.exe> Thrd: 80c6d220 Tid: b4 DS 23 ES 23 FS 30 GS 0 EAX: fffffff4 EBX: 80c6d5f8 ECX: 00000000 EDX: 9da883d0 EBP: 9e194a8c ESI: 0164fe24 ESP: 9e1949f0 EDI: 9e194d64 EFLAGS: 00000297 kESP 9e1949f0 kernel stack base 9e192000 Frames: <win32k.sys:9170b (./subsys/win32k/ntuser/msgqueue.c:621 (co_MsqPeekHardwareMessage))> <win32k.sys:92bfa (./subsys/win32k/ntuser/msgqueue.c:1259 (co_MsqFindMessage))> <win32k.sys:88626 (./subsys/win32k/ntuser/message.c:731 (co_IntPeekMessage))> <win32k.sys:890a3 (./subsys/win32k/ntuser/message.c:941 (co_IntWaitMessage))> <win32k.sys:893d2 (./subsys/win32k/ntuser/message.c:1051 (NtUserGetMessage))> <ntoskrnl.exe:9a8ea (ntoskrnl\ke\i386\syscall.S:372 (KiSystemService))> <user32.dll:52bd3 (lib/user32/windows/message.c:1166 (GetMessageW))>

19 years, 3 months

ROS really multitasking?

by nitro2k01

>From the way ROS tends to hamng up when running CPU-intense processes, I'm starting to suspect ROS is in fact not pre-emptively multitasking. And this seems to have gotten worse from 0.2.8 to 0.2.9. Any thoughts? /nitro2k01 -- The blog of nitro2k01: <http://soundandcomplete.blogspot.com/> Saliga äro de som kan stava till 2k01!

19 years, 3 months

Re: [ros-svn] [hpoussin] 20343: Replace implementation of QueryServiceConfigW by a stub (like in pre-20255), as rpcrt4 throws sometimes an exception and breaks PnP manager

by James Tabor

hpoussin(a)svn.reactos.com wrote: > Replace implementation of QueryServiceConfigW by a stub (like in pre-20255), as rpcrt4 throws sometimes an exception and breaks PnP manager > > LOL! That was no surprise! Sounds like Wine need to fix their broken code. I had a patch but I'm still ban from sending email to wine-patch! So~ rm * the patch! James

19 years, 3 months

Build 20369 crashes with unhandled exception

by Alex Buell

Here's the debugging log: (./ntoskrnl/ke/main.c:295) --------------------------------------------------------------- (./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20051227-r20369) Used memory 131072Kb (./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits. InitTop = 0x80100000, Init = 0x800fd000 (./ntoskrnl/mm/mm.c:283) No current process (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service PCNet failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service vmx_svga failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service pciide failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service PCNet failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service vmx_svga failed (Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service pciide failed (Status c0000001) (./ntoskrnl/io/pnpreport.c:86) IoReportResourceForDetection partly implemented (./ntoskrnl/io/pnpmgr.c:545) IoOpenDeviceRegistryKey(): Base key doesn't exist, exiting... (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000034) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service pciide failed (Status c0000034) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (Status 0xc0000034) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (Status 0xc0000034) (./ntoskrnl/io/disk.c:630) RDiskCount 2 SM: creating system paging files (./subsys/smss/initpage.c:220) SMSS: Created paging file \??\C: \reactos\pagefile.sys with size 131072 KB (./subsys/win32k/ntuser/winsta.c:108) IntWinStaObjectOpen (./subsys/win32k/ntuser/winsta.c:118) Create winsta atomtable (./subsys/win32k/ntuser/desktop.c:812) Trying to open desktop (\Windows \WindowStations\WinSta0\Default) (./subsys/win32k/ntuser/desktop.c:646) IntShellHookNotify: No desktop! (./subsys/win32k/ntuser/desktop.c:812) Trying to open desktop (\Windows\WindowStations\WinSta0\Winlogon) (./subsys/win32k/ntuser/desktop.c:646) IntShellHookNotify: No desktop! (./subsys/win32k/ntuser/desktop.c:812) Trying to open desktop (\Windows \WindowStations\WinSta0\Screen-Saver) (./subsys/win32k/ntuser/desktop.c:646) IntShellHookNotify: No desktop! WL-Status: ReactOS is starting up... WARNING: WSHGetSockaddrType at drivers/net/wshtcpip/wshtcpip.c:103 is UNIMPLEMENTED! (services/dhcp/util.c:72) ERROR: util.c read_client_conf not implemented! 80a4bef0: 00 00 00 00 ac 18 65 00 01 00 00 00 0f ef 40 00 ......e.......@. 80a4bf00: ac 18 65 00 31 34 35 00 ac 10 75 02 03 00 00 00 ..e.145...u..... 80a4bf10: 0a 00 00 00 1a 74 40 00 00 00 00 00 01 00 00 00 .....t@......... 80a4bf20: 00 00 00 00 .... (lib/shell32/iconcache.c:438) Failed to load IDI_SHELL_DOCUMENT icon! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.drv' (Status c0000135) (SAMLIB:lib/samlib/samlib.c:399) User already exists! (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (lib/setupapi/devinst.c:3154) Flags 0x800000 ignored (./lib/advapi32/service/scm.c:1573) StartServiceW is unimplemented, but returns success... (./ntoskrnl/ke/clock.c:132) FIXME: TIMER UPDATE NOT DONE!!! (./ntoskrnl/ke/clock.c:132) FIXME: TIMER UPDATE NOT DONE!!! (lib/ntdll/ldr/utils.c:2072) Relocating (77400000 -> 00c80000) C: \ReactOS\System32\msacm32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77400000 -> 00c90000) C:\ReactOS\System32\msvfw32.dll (lib/comctl32/commctrl.c:970) (TRUE, (null)): stub (lib/dinput8/dinput8_main.c:69) (void): stub (lib/ntdll/ldr/utils.c:2072) Relocating (777b0000 -> 00c80000) C: \ReactOS\System32\msi.dll (lib/oleacc/main.c:55) (lib/ntdll/ldr/utils.c:2072) Relocating (77aa0000 -> 00407000) C: \ReactOS\System32\olepro32.dll (lib/olepro32/olepro32stubs.c:48) not implemented (olepro32.dll) (lib/rpcrt4/rpcrt4_main.c:672) (): stub (lib/shdocvw/shdocvw_main.c:518) (TRUE, (null)): stub! (lib/shell32/shell32_main.c:1184) TRUE (null): stub (lib/wininet/wininet_main.c:36) (TRUE, (null)): stub (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (./ntoskrnl/mm/mm.c:300) Address: c0000040 (lib/rtl/i386/exception.c:90) Invalid exception frame (./ntoskrnl/ke/exception.c:94) KiRaiseException (ntoskrnl/ke/i386/exp.c:1312) Unhandled UserMode exception, terminating thread Unhandled exception ExceptionCode: c0000005 Faulting Address: 7fe0f9cc Address: 77e9238b C:\ReactOS\system32\user32.dll CS:EIP 1b:77e9238b DS 23 ES 23 FS 3b GS 0 EAX: 7fe0f9cc EBX: 0144fdec ECX: 0144ffb4 EDX: f000ff53 EBP: 0144fb6c ESI: 00000000 ESP: 0144fb24 EDI: 00000000 EFLAGS: 00000246 Frames: 77e50000+2f461 C:\ReactOS\system32\user32.dll 77e50000+2fdf6 C:\ReactOS\system32\user32.dll 77e50000+31fb6 C:\ReactOS\system32 \user32.dll 10000000+727f C:\ReactOS\system32\win32csr.dll 77e50000+52657 C:\ReactOS\system32\user32.dll 77e50000+53a52 C:\ReactOS\system32\user32.dll 7c900000+a15b C:\ReactOS\system32 \ntdll.dll 10000000+75fe C:\ReactOS\system32\win32csr.dll 7c800000 +2fd9d C:\ReactOS\system32\KERNEL32.dll (./subsys/win32k/ntuser/window.c:581) thread cleanup: while destroy wnds, wnd=0x8d322894 (subsys/win32k/main/dllmain.c:245) thread clean: remove reference obj 0x8d322894 (subsys/win32k/main/dllmain.c:245) thread clean: remove reference obj 0x8d322894 KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1242 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: win32k.sys Technical information: *** STOP: 0x0000001E (0xc0000005,0x9edcd9af,0x00000000,0xfffffff4) *** win32k.sys - Address 0x9edcd9af base at 0x9ed3d000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:9edcd9af <win32k.sys:909af (./subsys/win32k/ntuser/msgqueue.c:271 (co_MsqTranslateMouseMessage))> cr2 fffffff4 cr3 73a3000 Proc: 80b09360 Pid: 7c <csrss.exe> Thrd: 80cd0110 Tid: b4 DS 23 ES 23 FS 30 GS 0 EAX: fffffff4 EBX: 80cd0470 ECX: 00000000 EDX: 9ee2a3d0 EBP: 9f638a8c ESI: 0164fe24 ESP: 9f6389f0 EDI: 9f638d64 EFLAGS: 00010293 kESP 9f6389f0 kernel stack base 9f636000 Frames: <win32k.sys:9169b (./subsys/win32k/ntuser/msgqueue.c:621 (co_MsqPeekHardwareMessage))> <win32k.sys:92b8a (./subsys/win32k/ntuser/msgqueue.c:1259 (co_MsqFindMessage))> <win32k.sys:885b6 (./subsys/win32k/ntuser/message.c:731 (co_IntPeekMessage))> <win32k.sys:89033 (./subsys/win32k/ntuser/message.c:941 (co_IntWaitMessage))> <win32k.sys:89362 (./subsys/win32k/ntuser/message.c:1051 (NtUserGetMessage))> <ntoskrnl.exe:9aa4c (ntoskrnl/ke/i386/syscall.S:372 (KiSystemService))> <user32.dll:52bd3 (lib/user32/windows/message.c:1166 (GetMessageW))> -- http://www.munted.org.uk Anyone that thinks an imaginary deity is going to protect them against earthquakes and hurricanes needs psychiatric help.

19 years, 3 months

Update: Office2000 install on trunk

by Steven Edwards

Hi, I am pleased to announce that with Ge's patch to fix Exception handling and Brandon and Thomas's work on the pagefile it is now possible to install Office 2000 on the trunk. You will get quite a few errrors at the end of the install due to missing dlls from MDAC/ADO that Office2000 expects a Windows 2000 system to ship with, which we of course do not have stubbed at this time. Thanks to Eric Kohls work on services msiexec is mostly happy installing Office2000 if started from the command line like the following msiexec /i data1.msi There is still issues with setup.exe properly working althogh I think this is more due to version numbers we report. We are still unable to run Office applications at this time due to unhandled exceptions which look like they are due to COM errors as well as some problems due to the amount of memory we are reporting. Both Winword and Access display message boxes saying that there is not enough memory to run the application. Also even if we do get those issues fixed we are currently blocked by the registry instablity. -- Steven Edwards - ReactOS and Wine developer "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

19 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev December 2005