Ros-dev February 2012

ros-dev@reactos.org

38 participants
51 discussions

Developer meeting
by mikey sibert 24 Feb '12

24 Feb '12

I won't be able to go to the meeting maybe I will get some new drivers tested but I lost my usb card and need to find it.

2 3

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 23 Feb '12

23 Feb '12

0x19 bugcheck with CM corruption. Test reran. On Wed, Feb 22, 2012, at 10:30 PM, buildbot(a)reactos.org wrote: > The Buildbot has detected a failed 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/4897 > > 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: 55816 > Blamelist: sginsberg > > BUILD FAILED: failed test > > sincerely, > -The Buildbot > > > -- With best regards Caemyr

1 0

Re: [ros-dev] [ros-diffs] [sginsberg] 55813: Some misc fixes to Prefast. [DDK] - ndis.h Don't use local variables with the same name as function parameters. [PSDK] - access.idl Remove incorrect annotation - usbioctl.h Not r...
by Timo Kreuzer 23 Feb '12

23 Feb '12

These are not correct. Am 22.02.2012 21:58, schrieb sginsberg(a)svn.reactos.org: > Author: sginsberg > Date: Wed Feb 22 20:58:20 2012 > New Revision: 55813 > > > > Modified: trunk/reactos/include/psdk/usbioctl.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/psdk/usbioctl.h?re… > ============================================================================== > --- trunk/reactos/include/psdk/usbioctl.h [iso-8859-1] (original) > +++ trunk/reactos/include/psdk/usbioctl.h [iso-8859-1] Wed Feb 22 20:58:20 2012 > @@ -295,34 +295,34 @@ > USHORT DeviceAddress; > ULONG NumberOfOpenPipes; > USB_CONNECTION_STATUS ConnectionStatus; > - USB_PIPE_INFO PipeList[0]; > + USB_PIPE_INFO PipeList[ANYSIZE_ARRAY]; > } USB_NODE_CONNECTION_INFORMATION, *PUSB_NODE_CONNECTION_INFORMATION; > > > typedef struct _USB_DESCRIPTOR_REQUEST { > @@ -334,7 +334,7 @@ > USHORT wIndex; > USHORT wLength; > } SetupPacket; > - UCHAR Data[0]; > + UCHAR Data[ANYSIZE_ARRAY]; > } USB_DESCRIPTOR_REQUEST, *PUSB_DESCRIPTOR_REQUEST; > > #if (_WIN32_WINNT>= 0x0501) > @@ -358,7 +358,7 @@ > USHORT DeviceAddress; > ULONG NumberOfOpenPipes; > USB_CONNECTION_STATUS ConnectionStatus; > - USB_PIPE_INFO PipeList[0]; > + USB_PIPE_INFO PipeList[ANYSIZE_ARRAY]; > } USB_NODE_CONNECTION_INFORMATION_EX, *PUSB_NODE_CONNECTION_INFORMATION_EX; > > C_ASSERT(sizeof(USB_NODE_CONNECTION_INFORMATION_EX) == sizeof(USB_NODE_CONNECTION_INFORMATION));

1 0

Monthly meeting - February
by Aleksey Bragin 23 Feb '12

23 Feb '12

Hello, Let me invite you to the monthly status meeting taking place last Thursday of this month, 23rd of February, 19:00 UTC. The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in the channel #meeting. Note that the IRC service will only be started shortly before the meeting. Your participation passwords will be emailed to you shortly before the meeting starts. If someone still is not getting passwords sent before a meeting - please email Colin or Pierre before the meeting started to get one. In order to save time, let's choose who is going to be the minute taker on the upcoming meeting. Volunteers welcome. Proposed agenda for the meeting: 1. Release status: 0.3.15 2. New website status and migration plans. 3. CMake migration and finally abandoning RBuild. 4. 0.3.14 release party. More suggestions are welcome as usual. With the best regards, Aleksey Bragin.

4 3

change in email
by mikey sibert 23 Feb '12

23 Feb '12

i changed email to this one microsoft windows live is better than google. now i saved the best part for last, go her for a list of win32 api functions: http://j00ru.vexillium.org/w32k_syscalls/ it will help a lot in the development of reactos and make a lot mor programs run on then system

5 6

http://j00ru.vexillium.org/ntapi/
by mikey sibert 23 Feb '12

23 Feb '12

go here it might work i don't know it all runs on my pc.

1 0

system call list
by mikey sibert 23 Feb '12

23 Feb '12

can you send i list of the ones you have implemented

1 0

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

2nd stage pool corruption at the end, CM assert at subsequent reboots. I restarted the test and it worked fine the second time. On Wed, Feb 22, 2012, at 05:28 PM, buildbot(a)reactos.org wrote: > The Buildbot has detected a failed 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/4888 > > 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: 55808 > Blamelist: sginsberg > > BUILD FAILED: failed test > > sincerely, > -The Buildbot > > > -- With best regards Caemyr

1 0

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

VBox was locked up. Usurp: could you look into it? VBox window is stuck with Stopping status. Perhaps sysreg should kill the whole process and restart it, just to be safe? Best regards On Wed, Feb 22, 2012, at 12:15 PM, buildbot(a)reactos.org wrote: > The Buildbot has detected a failed 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/4882 > > Buildbot URL: http://build.reactos.org/ > > Buildslave for this Build: Windows_AMD64_2 > > Build Reason: The web-page 'force build' button was pressed by 'osiejka': > > Build Source Stamp: 55804 > Blamelist: > > BUILD FAILED: failed test > > sincerely, > -The Buildbot > > > -- With best regards Caemyr

1 0

Re: [ros-dev] [ros-diffs] [jgardou] 55770: [NTOSKRNL/MM] - finally, release user shared data at process address space cleanup. - release PDE pages that might not be freed at process end. - Let the caller handle PDE release ...
by Jérôme Gardou 22 Feb '12

22 Feb '12

Le 21/02/2012 01:32, jgardou(a)svn.reactos.org a écrit : > Author: jgardou > Date: Tue Feb 21 00:32:24 2012 > New Revision: 55770 > > URL: http://svn.reactos.org/svn/reactos?rev=55770&view=rev > Log: > [NTOSKRNL/MM] > - finally, release user shared data at process address space cleanup. > - release PDE pages that might not be freed at process end. > - Let the caller handle PDE release when deleting a PTE > - restore Richard's ASSERT : All user PDE pages are now freed! Addendum to log : When a page maps a Prototype PTE, we can't know if it must be deleted before dropping shared reference. Modify ASSERT accordingly. Restore the ASSERTion that only page fault should provocate the creation of the PDE and modify PDE refcounting in pageout code accordingly.

2 1

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 February 2012