Ros-dev

ros-dev@reactos.org

5789 discussions

by Aleksey Bragin

Hello, during recent discussion, a topic about mailing lists appeared. According to Pierre, we have 6 totally unused mailing lists, which are: ros-cis ros-errors ros-kernel ros-svn-diffs ros-translate ros-foundation I propose to delete all those, maybe except for ros-foundation. Any opinions? WBR, Aleksey Bragin.

13 years, 4 months

[ros-diffs] [rharabien] 55576: [COMCTL32] - Sync to Wine 1.3.37

by James Tabor

Hi, Did the diff patch in ComCtl32 get into the sync? We have that 2nd stage keyboard bug again at the start of setup and when it has finished.. James

13 years, 4 months

Re: [ros-dev] [ros-diffs] [cgutman] 55569: [USBDRV] - Terminate the NT4 USB driver

by Aleksey Bragin

Historical commit, deserving a nice rev number too! (hmm, 69 maybe viewed by some as nice too, but better let's focus on the "555" part ;)) On 12.02.2012 22:34, cgutman(a)svn.reactos.org wrote: > Author: cgutman > Date: Sun Feb 12 18:34:05 2012 > New Revision: 55569 > > URL: http://svn.reactos.org/svn/reactos?rev=55569&view=rev > Log: > [USBDRV] > - Terminate the NT4 USB driver > > Removed: > trunk/reactos/drivers/usb/nt4compat/ > >

13 years, 4 months

Testman blacklisting

by Kamil Hornicek

Hi, as requested I added a blacklisting ability to testman. The purpose of this is to have some meaningful comparison between test runs without completely disabling randomly behaving test sets. This means that blacklisted test are still being run, logged and included in the Totals summary. They won't affect the newly added "nonblacklisted summary" only. The last thing needed before we can actually benefit from this is to go through the tests, find those that give random results and either fix them or add them to the blacklist. Please use this wiki page http://www.reactos.org/wiki/Testman_blacklist to forge the list. Anyone with web repo commit access (that includes me) can then update the config itself. WBR, Kamil

13 years, 4 months

Announcement RosBE 2.0 for Windows

by Daniel Reimer

Hi, ok... last but not least, RosBE for Windows Version 2.0 is out too. This is one of the last steps to the upcoming cmake switch with dumping rbuild fully and forever. The setup files can be found here: http://www.reactos.org/wiki/Build_Environment Setup is the same good known NSIS based one for now. Just remove the old BE and let it install it over. CMAKE usage instructions are here:http://reactos.org/wiki/CMake Big thanks for this release goes to Heis and Colin from the Unix BE team, Amine for not killing me taking so long for a release and dralnix and blight_ for doing the first steps to a advanced BE years ago. Miss you, guys ^^ As for Unix one, I fully dump the support for any earlier Version of RosBE Windows starting from NOW. Best regards, Daniel

13 years, 4 months

RosBE-Unix 2.0 released

by Pierre Schweitzer

Hi, finally, we are getting closer and closer to CMake switch. RosBE-2.0 release brings supports for CMake and all the changes made in the tool chain. You can find it here: https://sourceforge.net/projects/reactos/files/RosBE-Unix/2.0/ To install it, simply extract the tar.bz2, and then run the RosBE-Builder.sh script. For instructions about how to use CMake in ReactOS, have a look to that wiki page: http://reactos.org/wiki/CMake Regarding this release, I would like to thank Colin Finck who did everything for it, but who have been obliged to let me release his work due to his busy life. RosBE 1.5 is not supported any longer. And I invite everyone to switch to CMake (with RosBE2.0 Windows/Linux). Rbuild deletion is now a matter of days. The countdown for Rbuild deletion has started. Regards, Pierre

13 years, 4 months

Re: [ros-dev] [ros-diffs] [tkreuzer] 55518: [FREELDR] - Enable new heap code and cleanup the heap, releasing unused memory, before starting reactos - Gives our kernel about 4MB additional memory, which - at the current leak...

by Aleksey Bragin

I must say, hpoussin proposed to get rid of bget in favor of rtl/heap.c, and I criticized his idea because I had no trust in the old heap code. Would reusing the new code be an option? Or you already invented the "mini-heap" which works good enough? WBR, Aleksey. On 10.02.2012 0:01, tkreuzer(a)svn.reactos.org wrote: > Author: tkreuzer > Date: Thu Feb 9 20:01:10 2012 > New Revision: 55518 > > URL: http://svn.reactos.org/svn/reactos?rev=55518&view=rev > Log: > [FREELDR] > - Enable new heap code and cleanup the heap, releasing unused memory, before starting reactos > - Gives our kernel about 4MB additional memory, which - at the current leak rate - means around 8 minutes longer before it runs out of memory :) > - Using the temp heap for all temporary allocations should increase the amount of saved space > > Removed: > trunk/reactos/boot/freeldr/freeldr/mm/heap.c > trunk/reactos/boot/freeldr/freeldr/rtl/bget.c >

13 years, 4 months

GSoC 2012

by Colin Finck

Hi all, The Google Summer of Code 2012 project registration phase is starting in three weeks. Are we going to apply again after our success last year? Who will be available as administrators and mentors? Is anybody already collecting task ideas? Cheers, Colin

13 years, 4 months

Automated tests on Real HardWare + USB-trunk tests

by Jan Blomqvist Kinander

It is time to get automated tests made on real hardware up and running. I have started a project to get ReactOS to run on a FUJITSU SIEMENS ESPRIMO E5925 (wich already installs and runs from CD and HDD) however, to get automated tests going we need to be able to script stuff and feed it with iso:s, this I have planned to do with Intel AMT / vPro technology. ( http://en.wikipedia.org/wiki/Intel_Active_Management_Technology ). The goal is to have all builds tested on real HW and to get ReactOS to be a usable system for real HW to be able to kill as many bugs as possible and make different HW setups to work. This will be unnecessary before we go beta in the future. I have a bunch of debug lists from this actual HW, made and added links to them below, some of them are from the USB-trunk branch. IDE-r: http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture02.txt USB-trunk Real HW debug dumps: http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB01.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB02.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB03.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB04.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB05.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB06.txt http://dl.dropbox.com/u/37916523/ESPRIMO%20E5925%20capture%20USB06a.txt http://dl.dropbox.com/u/37916523/Compaq%20EVO%20D51s%20capture%20USB01.txt http://dl.dropbox.com/u/37916523/AMD%20VIA%20capture%20USB01.txt ________________________________________________ Jan Blomqvist Kinander (Jaix Bly) Tel: +46 472 269932, Fax: +46 472 260980 Cell: +46 704 283980, E-Mail: jan.blomqvist(a)reactos.org

13 years, 4 months

Re: [ros-dev] [ros-diffs] [janderwald] 55447: [DISK_NEW] - Fix compilation of new disk driver - Patch by Alex Ionescu

by Jérôme Gardou

Le 06/02/2012 07:50, janderwald(a)svn.reactos.org a écrit : > > +if(ARCH MATCHES i386) > + add_target_compile_flags(disk "-mrtd -fno-builtin -Wno-unused-variable -Wno-pointer-sign") > +endif() > + > Hey! Those look very GCC centric. The corresponding flag for MSVC to -mrtd would be /Gz. As for other flags, I'm unsure of what -fno-builtin would correspond to, and others are only for warnings. Cheers. Jérôme.

13 years, 4 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