Ros-dev June 2012

ros-dev@reactos.org

21 participants
13 discussions

by Pierre Schweitzer

Hi, after having finished its 11405th build, the last official RBuild builder has gone offline, forever. The Linux CMake builder has now turned as being the official builder. Thanks RBuild, you served us well :-). Also, the other RBuild builder, the release builder has also gone offline forever. Its hardware was not able to properly handle a ReactOS build, and was hardly upgradable. Daily release builds should replace it any time soon. With my best regards, -- Pierre Schweitzer <pierre(a)reactos.org> Systems Administrator ReactOS Foundation

12 years, 11 months

Monthly meeting rescheduled

by Aleksey Bragin

Hello! I was away this week, so the meeting at the usual time got canceled. I propose to conduct meeting next thursday, 5th of July. If someone would not be able to make it - please email me. Regards, Aleksey Bragin.

13 years, 1 month

ReactOS on ARM, working on the iPhone

by Richardo Stallmanu

Hello everyone! I just got freeldr working properly (sort of) on the iPhone 4! Currently, I use Apple's iBSS (first stage DFU bootloader), with the go command patched to always branch to 0x41000000. 0x41000000 contains the actual LLB, which is relocated to 0x42000000. The LLB will initialize the ReactOS loader console and ARM loader block, which is sent to FreeLoader, just like on Omap3/Zoom2MDK and Versatile/PB. Time to get ramdisks working. :) http://goput.it/uc5.jpg <- There's your picture. -- winocm

13 years, 1 month

Re: [ros-dev] [ros-builds] Trunk_x86_GCCLin Debug: build failed

by Pierre Schweitzer

Hi, we are currently working on the failed server to fix it definitely (we hope). I have set up a temporary solution to ensure ISOs are well stored. They cannot be downloaded though. Sorry about all that troubles. With my best regards, P. Schweitzer On Tue, 2012-06-26 at 08:43 +0000, buildbot(a)reactos.org wrote: > The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS. > Full details are available at: > http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/998 > > Buildbot URL: http://build.reactos.org/ > > Buildslave for this Build: Linux_AMD64_1 > > Build Reason: scheduler > Build Source Stamp: 56807 > Blamelist: tfaber > > BUILD FAILED: failed shell > > sincerely, > -The Buildbot > > -- Pierre Schweitzer <pierre(a)reactos.org> System Administrator ReactOS Foundation

13 years, 1 month

Re: [ros-dev] [ros-builds] Trunk_x86_GCCLin Debug: build failed

by Pierre Schweitzer

Hi, this is unfortunately due to our entry server to network storage that has crashed once again tonight. All attempts to remotely reboot it failed. A human intervention will be required. It will not happen before several hours. The responsible person for the server has been informed. In case it was not possible to restore the server in a correct time, a workaround solution will be deployed once again. We are sorry for the caused inconvenience. With my best regards, P. Schweitzer Le dimanche 24 juin 2012 à 21:10 +0000, buildbot(a)reactos.org a écrit : > The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS. > Full details are available at: > http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/989 > > Buildbot URL: http://build.reactos.org/ > > Buildslave for this Build: Linux_AMD64_1 > > Build Reason: scheduler > Build Source Stamp: 56800 > Blamelist: ekohl > > BUILD FAILED: failed shell > > sincerely, > -The Buildbot > > -- Pierre Schweitzer <pierre(a)reactos.org> Systems Administrator ReactOS Foundation

13 years, 1 month

Newbie to ReactOS

by Lonnie Cumberland

Greetings All, I am new to ReactOS but have much experience with with Windows, Linux, etc... as well as programming mainly in C/C++. Recently, I have decided to looking into ReactOS from a learning perspective after which, once the learning curve has been completed, I may try to get involved with some of the development efforts as well as work on some additional projects. >From what I have seen, ReactOS has come a very long ways in its development and is really turning into a special OS to be recognized. I would like to review some of the documentation on the Wiki but had a question regarding an experiment that I wanted to investigate with ReactOS. The question that I wanted to answer is this. What is the absolute minimum size, as relates to booting and OS files that are needed by ReactOS to run, for example, the notepad.exe program? To caveat this, it would include leaving out all of the OS tools, Explorer, Desktop, and absolutely everything that is not clearly needed to run the notepad.exe application. Basically, I would like ReactOS to boot and go directly into the notepad application. The real point here is to investigate what "absolute" minimum files are needed to run a simple application. Sounds a bit crazy, but that is the question that I would like to answer. Any ideas or information related to this would be greatly appreciated. Thanks and have a great day, Lonnie

13 years, 1 month

ReactOS and MS XP compatability

by Lonnie Cumberland

Greetings All, I have been reviewing ReactOS on the website and wiki to get a better feel for the project, which I must say is very impressive. >From what I have read, it seems that ReactOS is initially shooting for a drop-in replacement for WindowsXP and beyond which raised a question for me. The site also seems to suggest, for the most part and with the exception of a few core ReactOS files (ie. kernel plus a couple of others), that ReactOS should be 100% compatible with WindowsXP. With this in mind, I wondered this. If I had an old licensed Windows XP disk, which I do, then shouldn't it be possible to use the base core ReactOS files (ie. the minimalist ReactOS configuration like in my previous inquiry to the mailing list) and then use the WindowsXP subsystem core files? I guess what I was wondering, not to detract from the true developments of ReactOS which I like a lot, is would the WindowsXP system files function the same with the ReactOS kernel, and minimal files that were listed by Alex in a previous email. reeldr (ntldr) ntoskrnl hal bootvid kdcom fastfat ramdisk kbdclass i8042prt ntdll smss What I am getting at, is a development that is still forming, but the idea is to utilize ReactOS to allow for the development of a Super Sandbox system that is run in a specialize VM, and which would allow for each application to be run in their own ReactOS VM. Although I am still playing with the idea a lot, it is forming in such a way that would totally isolate each application in a separate VM that is composed of super minimal ReactOS kernel running. Just playing with ideas that I have had for a while, but at the moment, I am still learning about ReactOS so that I will be able to contribute to it soon. Thanks and have a great day, Lonnie

13 years, 1 month

(no subject)

by Marc Piulachs

http://secondlife.zhaarteth.net/wp-content/themes/dark-wood/googles.html?fg…

13 years, 1 month

Re: [ros-dev] [ros-diffs] [akhaldi] 56731: [CMAKE/MIDL] * Alter the way we handle the dlldata generation with midl. This works around the warnings we get about multiple rules to generate proxy.dlldata.c. * Brought to yo by ...

by Timo Kreuzer

Did you test dependency checking? Am 14.06.2012 13:06, schrieb akhaldi(a)svn.reactos.org: > Author: akhaldi > Date: Thu Jun 14 11:06:23 2012 > New Revision: 56731 > > URL:http://svn.reactos.org/svn/reactos?rev=56731&view=rev > Log: > [CMAKE/MIDL] > * Alter the way we handle the dlldata generation with midl. This works around the warnings we get about multiple rules to generate proxy.dlldata.c. > * Brought to yo by Peter Kummel. > > Modified: > trunk/reactos/cmake/midl-support.cmake > > Modified: trunk/reactos/cmake/midl-support.cmake > URL:http://svn.reactos.org/svn/reactos/trunk/reactos/cmake/midl-support.cma… > ============================================================================== > --- trunk/reactos/cmake/midl-support.cmake [iso-8859-1] (original) > +++ trunk/reactos/cmake/midl-support.cmake [iso-8859-1] Thu Jun 14 11:06:23 2012 > @@ -38,16 +38,17 @@ > get_includes(_includes) > get_defines(_defines) > set(_chain_dependency "") > + set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/proxy.dlldata.c PROPERTIES GENERATED TRUE) > foreach(_idl_file ${ARGN}) > get_filename_component(_name_we ${_idl_file} NAME_WE) > add_custom_command( > - OUTPUT ${_name_we}_p.c ${_name_we}_p.h proxy.dlldata.c > + OUTPUT ${_name_we}_p.c ${_name_we}_p.h > COMMAND midl ${_includes} ${_defines} ${IDL_FLAGS} /client none /server none /proxy ${_name_we}_p.c /h ${_name_we}_p.h /dlldata proxy.dlldata.c ${CMAKE_CURRENT_SOURCE_DIR}/${_idl_file} > DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/${_idl_file} ${_chain_dependency}) > list(APPEND _chain_dependency ${CMAKE_CURRENT_BINARY_DIR}/${_name_we}_p.c) > list(APPEND _chain_dependency ${CMAKE_CURRENT_BINARY_DIR}/${_name_we}_p.h) > + set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/proxy.dlldata.c PROPERTIES OBJECT_DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/${_idl_file}) > endforeach() > - set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/proxy.dlldata.c PROPERTIES GENERATED TRUE) > endfunction() > > function(add_rpc_files _type) > > >

13 years, 1 month

Re: [ros-dev] buildbot exception in ReactOS on Windows_AMD64_1 VBox-Test

by caemyr＠myopera.com

Looks like the crash had locked up the VM hard: loader.c:1019: Test failed: wrong section data (..\..\dll\ntdll\ldr\ldrutils.c:1322) LDR: LdrpMapDll Relocating Image Name C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ldr3C.tmp (10000000 -> 00011000) (..\..\dll\ntdll\ldr\ldrutils.c:1361) Overlapping DLL: Dynamically Allocated Memory loader.c:599: Test failed: got 0x4 != expected 0x1 loader.c:601: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY loader.c:627: Test failed: got 0x4 != expected 0x1 loader.c:629: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY loader.c:645: Test failed: got 0x4 != expected 0x1 loader.c:647: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY (..\..\ntoskrnl\mm\ARM3\expool.c:274) Entry BlockSize 2, tag fPsR. NextEntry PreviousSize 0, tag *** Fatal System Error: 0x00000019 (0x00000005,0xB0A0EB18,0x00000116,0xB0A0EB08) [7hEntered debugger on embedded INT3 at 0x0008:0x8091ba34. kdb:> bt Eip: <NTOSKRNL.EXE:11ba35 (..\..\lib\rtl\i386\debug_asm.S:46 (_RtlpBreakWithStatusInstruction@0))> Frames: <NTOSKRNL.EXE:80445 (../../ntoskrnl/ke/bug.c:1081 (KeBugCheckWithTf@24))> <NTOSKRNL.EXE:80581 (../../ntoskrnl/ke/bug.c:1405 (KeBugCheckEx@20))> <NTOSKRNL.EXE:964e2 (../../ntoskrnl/mm/ARM3/expool.c:211 (ExpCheckPoolHeader@4))> <NTOSKRNL.EXE:966d3 (../../ntoskrnl/mm/ARM3/expool.c:303 (ExpCheckPoolBlocks@4))> <NTOSKRNL.EXE:96fa5 (../../ntoskrnl/mm/ARM3/expool.c:2215 (ExFreePoolWithTag@8))> <NTOSKRNL.EXE:9755a (../../ntoskrnl/mm/ARM3/expool.c:2359 (ExFreePool@4))> <NTOSKRNL.EXE:bf8da (../../ntoskrnl/mm/freelist.c:556 (MmDereferencePage@4))> <NTOSKRNL.EXE:bf541 (../../ntoskrnl/mm/balance.c:130 (MmReleasePageMemoryConsumer@8))> <NTOSKRNL.EXE:473b (../../ntoskrnl/cc/view.c:913 (CcFreeCachePage))> <NTOSKRNL.EXE:c1501 (../../ntoskrnl/mm/marea.c:745 (MmFreeMemoryArea@16))> <NTOSKRNL.EXE:413c (../../ntoskrnl/cc/view.c:962 (CcRosInternalFreeCacheSegment))> <NTOSKRNL.EXE:6f3d (../../ntoskrnl/cc/view.c:1145 (CcRosDeleteFileCache@8))> <NTOSKRNL.EXE:755f (../../ntoskrnl/cc/view.c:1210 (CcRosDereferenceCache@4))> <NTOSKRNL.EXE:cb47c (../../ntoskrnl/mm/section.c:2672 (MmpDeleteSection@4))> <NTOSKRNL.EXE:da087 (../../ntoskrnl/ob/oblife.c:211 (ObpDeleteObject@8))> <NTOSKRNL.EXE:da11b (../../ntoskrnl/ob/oblife.c:238 (ObpReapObject@4))> <NTOSKRNL.EXE:41e42 (../../ntoskrnl/ex/work.c:162 (ExpWorkerThreadEntryPoint@4))> <NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))>--- Press q to abort, any other key to continue --- <f88b3db8> <NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))> <NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145 (ExpWorkerThreadEntryPoint@4))> <NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))> <f88b7db8> <NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))> <NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145 (ExpWorkerThreadEntryPoint@4))> <NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))> <f88bbdb8> <NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))> <NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145 (ExpWorkerThreadEntryPoint@4))> <NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))> <f889bdb8> <NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))> <NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145 (ExpWorkerThreadEntryPoint@4))>--- Press q to abort, any other key to continue --- <NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))> <415c6d6d> Couldn't access memory at 0x5C6C6E76! kdb:> On Thu, Jun 7, 2012, at 06:23 PM, buildbot(a)reactos.org wrote: > The Buildbot has finished a build on builder Windows_AMD64_1 VBox-Test > while building ReactOS. > Full details are available at: > http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/5866 > > Buildbot URL: http://build.reactos.org/ > > Buildslave for this Build: Windows_AMD64_2 > > Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger) > Build Source Stamp: 56702 > Blamelist: ekohl > > BUILD FAILED: exception test > > sincerely, > -The Buildbot > -- With best regards Caemyr

13 years, 2 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev June 2012