Ros-dev

ros-dev@reactos.org

2 participants
5791 discussions

Alex.
by Lucio Diaz 16 Oct '05

16 Oct '05

Alex Ionescu wrote: Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu ------------------------------------------ After being reading this mailing list for over a year i can really understand Alex, Period. Lucio Diaz-Flores Varela. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

Break
by Alex Ionescu 16 Oct '05

16 Oct '05

Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu

8 14

Ros boot failure - r 18469
by Gge 16 Oct '05

16 Oct '05

Hi, Ros installs successfuly from BootCD ( r 18469) but then at start Ros bugchecks . Any idea ? (ntoskrnl\ldr\loader.c:876) Loading Module \SystemRoot\system32\drivers\npfs.sys... (ntoskrnl\ldr\loader.c:879) Module \SystemRoot\system32\drivers\npfs.sys loaded at 0x9d120000. (ntoskrnl\ke\i386\exp.c:1306) Unhandled UserMode exception, terminating thread KeBugCheckEx at ntoskrnl\ex\init.c:716 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000071 (0x00000001,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2615 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))> <ntoskrnl.exe:bea8a (ntoskrnl/ex/init.c:716 (ExpInitializeExecutive))> <ntoskrnl.exe:6806 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:bc854 (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_text_start__))> KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:1236 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,0x800a2d47,0x00000000,0x1f000000) *** ntoskrnl.exe - Address 0x800a2d47 base at 0x80000000, DateStamp 0x0 Regards Gge

1 0

Installing ReactOS 0.2.8 on vmware 5.5 beta
by Saravanan Jayakumar 16 Oct '05

16 Oct '05

Hi, Can anyone please let me know how to run React 0.2.8 RC1 on VMware 5.5 Beta.When i run it on vmware its asking to install certain vmwarre tools, i guess its the graphics driver.Then vmware complains that the driver is not found for this OS and i dont see anything on the screen. regards Jay

5 7

Gudie Lines for SVN Write access
by Magnus Olsen 16 Oct '05

16 Oct '05

Hi I should love to see some new gudieles how to get svn access. Today it seam anyone that provide with a patch that is coder can getting svn access. But I think we need start think how we should handle it, Here is some ideas how it can be 1. A maling list with patch or in Bugzila I love see a maling list with the patch 2. When people have submit the patch to us we start examing it see if it any godd (we are doning that already) 3. To get SVN write access u need lest provide patch in regual basic under 6 month lest, Then after 6 month the provider can write to mailing list see if can getting SVN write access before he grant SVN write access, the full name and mailing address must be provided, and we should have a vote if that provder can getting SVN write access. no accpect from all this rules. Yestday some was granted svn access his name was not on the mailing list why he got one, he did not write either on the mailing list asking for svn access that why I want see new guide lines how svn write access handles. so every one know how he is and why he was granted to be granted after few patcher are not accpect in my eys. For we are starting getting alot with people with svn write access. And new guide lines must be create. BestReagds Magnus Olsen

7 8

MM and CM architecture
by Saravanan Jayakumar 16 Oct '05

16 Oct '05

Hi, I am new to React-OS but following the project for quite sometime. I would like to know how the memory managemnet and cache manger works in React OS.Isit similar to NT?.If anyone can let me know the arcitecture of these two components in ReactOS, it would be helpful for me to follow the code.Youcould also give me a few pointers as of where to start of in the code for MM and CM so that i could dissect the flow. regards Jay

2 1

Re: [ros-diffs] [gvg] 18468: Make sure we don't hang forever when activating a window belonging to
by Gunnar Dalsnes 16 Oct '05

16 Oct '05

gvg(a)svn.reactos.com wrote: > > - co_IntSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > > + co_IntPostOrSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > I think the whole co_IntPostOrSendMessage function is wrong and crazy. Who made it? Sending and posting messages are completely different things. I think something like co_IntSendMessageTimeout should be used instead, but i dont think its implemented yet. G.

3 3

Via 8233 Sound Install
by James Tabor 16 Oct '05

16 Oct '05

Hi! From running Setup in the via8233 directory. http://www.qdigrp.com/qdisite/eng/support/d_downloadcd.htm http://www.qdigrp.com/qdisite/driver/utility/sound/Via8233.zip (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:2072) Relocating (76160000 -> 6e0000) C:\ReactOS\system32 \comctl32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (777d0000 -> 782000) C:\ReactOS\system32 \winmm.dll (lib/ntdll/ldr/utils.c:2072) Relocating (76260000 -> 7db000) C:\ReactOS\system32 \oleaut32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77a90000 -> 4b1000) C:\ReactOS\system32 \VERSION.dll (lib/comctl32/theming.c:138) Could not re-register class L"#32770": 57 FIXME: CopyImage doesn't support IMAGE_ICON correctly! (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.dr v' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1240000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\193e5.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\DOCUME~ 1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\_ISUSER.DLL' (Status c00001 35) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1263000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_WUTL951.DLL (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 4c1000) C:\DOCUME~1\ADMINI~ 1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\v32audio.dll (lib/setupapi/devinst.c:1818) : flag DIGCF_PRESENT ignored Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 7c9250bc C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c9250bc DS 23 ES 23 FS 3b GS 0 EAX: 005df4a0 EBX: 7ffdf000 ECX: 7668543c EDX: 00000000 EBP: 005df4a4 ESI: 00000000 ESP: 005df498 EDI: 00696120 EFLAGS: 00010202 Frames: 76660000+5ccc C:\ReactOS\System32\SETUPAPI.DLL 76660000+6ba9 C:\ReactOS\System32\SETUPAPI.DLL 76660000+55fc C:\ReactOS\System32\SETUPAPI.DLL 76660000+540c C:\ReactOS\System32\SETUPAPI.DLL 4c1000+1452 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP 0.DIR\v32audio.dll 400000+fff8 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10b29 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16912 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16bff C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10e60 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+113ad C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+76b77 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 7c800000+31255 C:\ReactOS\system32\KERNEL32.dll (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! The linux sound system does work. Thanks, James

3 4

ReactOS build fallen over
by Wesley Parish 16 Oct '05

16 Oct '05

I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result. I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile. [wparish@localhost reactos027]$ make [MKDIR] obj-i386/tools [MKDIR] obj-i386/tools/rbuild [MKDIR] obj-i386/tools/rbuild/backend [MKDIR] obj-i386/tools/rbuild/backend/mingw [CC] tools/rbuild/backend/mingw/mingw.cpp [CC] tools/rbuild/backend/mingw/modulehandler.cpp [CC] tools/rbuild/backend/mingw/proxymakefile.cpp [MKDIR] obj-i386/tools/rbuild/backend/devcpp [CC] tools/rbuild/backend/devcpp/devcpp.cpp [CC] tools/rbuild/backend/backend.cpp [CC] tools/rbuild/automaticdependency.cpp [CC] tools/rbuild/bootstrap.cpp [CC] tools/rbuild/cdfile.cpp [CC] tools/rbuild/compilerflag.cpp [CC] tools/rbuild/configuration.cpp [CC] tools/rbuild/define.cpp [CC] tools/rbuild/exception.cpp [CC] tools/rbuild/filesupportcode.cpp [CC] tools/rbuild/include.cpp [CC] tools/rbuild/installfile.cpp [CC] tools/rbuild/linkerflag.cpp [CC] tools/rbuild/module.cpp [CC] tools/rbuild/project.cpp [CC] tools/rbuild/ssprintf.cpp [CC] tools/rbuild/stubbedcomponent.cpp [CC] tools/rbuild/testsupportcode.cpp [CC] tools/rbuild/wineresource.cpp [CC] tools/rbuild/XML.cpp [CC] tools/rbuild/rbuild.cpp [MKDIR] output-i386/tools [MKDIR] output-i386/tools/rbuild [LD] output-i386/tools/rbuild/rbuild [MKDIR] obj-i386/tools/bin2res [CC] tools/bin2res/bin2res.c [CC] tools/bin2res/mkstemps.c [MKDIR] output-i386/tools/bin2res [LD] output-i386/tools/bin2res/bin2res [MKDIR] obj-i386/tools/buildno [CC] tools/buildno/buildno.cpp [CC] tools/buildno/exception.cpp [CC] tools/buildno/ssprintf.cpp [CC] tools/buildno/XML.cpp [MKDIR] output-i386/tools/buildno [LD] output-i386/tools/buildno/buildno [BUILDNO] include/reactos/buildno.h [MKDIR] obj-i386/tools/wmc [CC] tools/wmc/getopt.c [CC] tools/wmc/lang.c [CC] tools/wmc/mcl.c [CC] tools/wmc/utils.c [CC] tools/wmc/wmc.c [CC] tools/wmc/write.c [CC] tools/wmc/y_tab.c [CC] tools/wmc/misc.c [MKDIR] output-i386/tools/wmc [LD] output-i386/tools/wmc/wmc [WMC] include/reactos/bugcodes.h [WMC] include/reactos/errcodes.h [MKDIR] obj-i386/tools/nci [CC] tools/nci/ncitool.c [MKDIR] output-i386/tools/nci [LD] output-i386/tools/nci/nci [NCI] ntoskrnl/include/internal/napi.h [MKDIR] obj-i386/tools/gendib [CC] tools/gendib/gendib.c [MKDIR] output-i386/tools/gendib [LD] output-i386/tools/gendib/gendib [GENDIB] subsys/win32k/dib/dib16gen.c [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating proxy makefiles...done Checking automatic dependencies...done [DLLTOOL] obj-i386/lib/kernel32/libkernel32.a make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$ -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

2 2

Re: [ros-diffs] [hbirr] 18481: Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.
by Gunnar Dalsnes 15 Oct '05

15 Oct '05

This is not the right fix... I will revert these changes when i come up with a proper fix. I also dont understand how this can fix bug 805 (eternal loop in thread windows cleanup routine). Even with your changes the eternal loop is still there, it just doesnt run out of stack? G. hbirr(a)svn.reactos.com wrote: > Don't use alloca in a macro, which may be used in a loop. This does fix bug #805. >

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev