![[Valid RSS]](images/valid-rss-rogers.png "Valid RSS")
This is a valid RSS feed.
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
<?xml version="1.0" encoding="utf-8" standalone="yes" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <channel> <title>Front Page on ReactOS Website</title> <link>https://reactos.org/</link> <description>Recent content in Front Page on ReactOS Website</description> <generator>Hugo -- gohugo.io</generator> <language>en-us</language> <lastBuildDate>Thu, 01 Feb 2024 00:00:00 +0000</lastBuildDate> <atom:link href="https://reactos.org/index.xml" rel="self" type="application/rss+xml" /> <item> <title>1st-stage GUI setup, Part 3 - December 2023: First tests</title> <link>https://reactos.org/blogs/gui-setup-part3-first-testing-problems/</link> <pubDate>Thu, 01 Feb 2024 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gui-setup-part3-first-testing-problems/</guid> <description>Greetings!Welcome to the third blog of the series &ldquo;1st-stage GUI setup&rdquo;: September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests In this third blog post, I will cover my work done during the month of December 2023: testing the whole 1st-stage GUI setup, together with the partially wine-synced setupapi dll.Finishing and testing the partitioning page UI The first week was devoted to finally putting together the code for manipulating partitions from the user interface, using the new workflow, and testing it.</description> </item> <item> <title>1st-stage GUI setup, Part 2 - October-November 2023: Making partitioning UI work</title> <link>https://reactos.org/blogs/gui-setup-part2-partitioning/</link> <pubDate>Wed, 31 Jan 2024 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gui-setup-part2-partitioning/</guid> <description>Greetings!Welcome to the second blog of the series &ldquo;1st-stage GUI setup&rdquo;: September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests As you may have noticed, I have been quite silent about my work and not regularly writing blog posts about what I have done so far. Well, I am more concerned about getting actual code written and working before discussing about it, instead of doing that about half-done not-yet-tested code; much like what the GUI setup was during these previous months.</description> </item> <item> <title>1st-stage GUI setup, Part 1 - September 2023: Partly Wine-syncing setupapi</title> <link>https://reactos.org/blogs/gui-setup-part1-setupapi/</link> <pubDate>Mon, 04 Dec 2023 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gui-setup-part1-setupapi/</guid> <description>Greetings to all ReactOS followers! As many of you certainly are aware by now, I have been officially hired by ReactOS Deutschland e.V. to develop the graphical version of the 1st-stage ReactOS installer (&ldquo;1st-stage GUI setup&rdquo;).This is the first blog of the series &ldquo;1st-stage GUI setup&rdquo;: September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests During this first month of September 2023, my goal was to partly sync the code of the setupapi.</description> </item> <item> <title>Newsletter 103 - Late 2023 news</title> <link>https://reactos.org/blogs/newsletter-103/</link> <pubDate>Sun, 05 Nov 2023 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-103/</guid> <description>Salutations from the ReactOS project team! In previous posts, we talked about the ReactOS releasing process and the development status of the project, as well as the hiring of our long-term developer Hermès Bélusca-Maïto (HBelusca). We are making an effort to publish at least 3 newsletters per year, depending on how the development workflow goes. In this newsletter we will highlight some of the contributions made by project developers and contributors, as well as future plans and headlines.</description> </item> <item> <title>Hermès Bélusca-Maïto hired full-time to work on the ReactOS GUI Setup</title> <link>https://reactos.org/project-news/hermes-belusca-hired-full-time/</link> <pubDate>Sun, 01 Oct 2023 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/hermes-belusca-hired-full-time/</guid> <description>Our team proudly announces that ReactOS Deutschland e.V. has hired Hermès Bélusca-Maïto to work full-time on the ReactOS GUI Setup for the next 5 months, starting September 2, 2023.Hermès is a long-time contributor and developer who worked on the project since 2012. He has several skills and expertise into various components of ReactOS, notably being the Client/Server Runtime Subsystem (CSRSS), Console Server Subsystem (CONSRV), NTVDM, and others.His upcoming goal is to finish the first-stage ReactOS GUI setup, which offers an alternative to the classic first-stage text-mode setup (also called USETUP).</description> </item> <item> <title>Newsletter 102 - 2022/2023 news</title> <link>https://reactos.org/blogs/newsletter-102/</link> <pubDate>Tue, 27 Jun 2023 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-102/</guid> <description>Hello ReactOS followers and enthusiasts! It has been quite a long time since we published the 101th newsletter and so far no further updates have been posted since then. While the ReactOS Twitter account does provide announcements, posts about working applications and such from time to time, much of what is happening with the project as a whole isn&rsquo;t mentioned. Most of what we are going to talk about is the current situation with releases and overall ReactOS development.</description> </item> <item> <title>Google Summer of Code 2022 - Call for contributors</title> <link>https://reactos.org/project-news/google-summer-of-code-2022/</link> <pubDate>Sun, 13 Mar 2022 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/google-summer-of-code-2022/</guid> <description>We are proud to announce that ReactOS has been accepted into the 2022 Google Summer of Code program.The GSOC program is a great opportunity for a fresh contributors looking to join the Open Source and Free Software movement.This year we are looking for new contributors who want to enhance skills in kernel development and NT architecture. Our team consists of skilled mentors who are going to guide eager students with ReactOS architecture and development practices.</description> </item> <item> <title>ReactOS will be on Chemnitz Linux Days 2022 (Online event)</title> <link>https://reactos.org/project-news/clt-2022-invitation/</link> <pubDate>Mon, 07 Mar 2022 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/clt-2022-invitation/</guid> <description>ReactOS will participate with an own booth on CLT 2022. It will be held on this Saturday and Sunday. Starts at 9:30 CET and ends at ~18:00 CET on both days.The whole thing will be held online and to make you at least feel a bit like you are there in real they once more use the WorkAdventure platform.We plan to show ReactOS of course and stuff that works.</description> </item> <item> <title>ReactOS 0.4.14 released</title> <link>https://reactos.org/project-news/reactos-0414-released/</link> <pubDate>Thu, 16 Dec 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0414-released/</guid> <description>The ReactOS Team is pleased to announce the release of version 0.4.14. As with every other release, we&rsquo;re regularly noting improvements and updates to keep you in touch with what is being done in ReactOS. In this release, improvements range from FreeLoader fixes, Shell features, kernel fixes, NetKVM VirtIO bringup, further work on the Xbox port and support for NEC PC-9800.Note that it took us over a year to get this release in shape and fix regressions.</description> </item> <item> <title>Newsletter 101 - July 2021 news</title> <link>https://reactos.org/blogs/newsletter-101/</link> <pubDate>Sun, 01 Aug 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-101/</guid> <description>Hello ReactOS followers! This report covers changes in the project during February-July 2021. And we definitely have some things to highlight!amd64 build is getting more stable Timo Kreuzer (tkreuzer) worked hard on various parts of the kernel and HAL, fixing issues here and there. Structured Exception Handling (SEH) support for the amd64 architecture was finished, various bugs around the kernel are fixed. A major issue with interrupt handling in HAL was also fixed in May, which finally allowed a semi-stable boot in a virtual environment.</description> </item> <item> <title>Welcome GSoC 2021 Students!</title> <link>https://reactos.org/project-news/welcome-gsoc-2021-students/</link> <pubDate>Tue, 18 May 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/welcome-gsoc-2021-students/</guid> <description>Another year, another round of Google Summer of Code! The ReactOS Project is participating in Google Summer of Code 2021 and welcomes the selected students.He Yang is a successful student from GSoC 2020, who is going to continue his dive into user-mode ReactOS this year by working on iernonce.dll. That library is responsible for RunOnceEx, a prominent Windows feature to run multiple commands once after a system reboot. Implementing that feature will benefit software depending on it.</description> </item> <item> <title>Newsletter 100 - January 2021 news</title> <link>https://reactos.org/blogs/newsletter-100/</link> <pubDate>Sat, 06 Feb 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-100/</guid> <description>Hello ReactOS followers! This is an attempt to re-instate the Newsletter, which informed you about recent developments. The previous Newsletter 99 was in 2013!This month we were mostly focused on the kernel work, merging pull requests and fixing regressions.Memory manager and Common cache work Being in development for almost six month, this work by Jérôme Gardou finally landed in the master branch. This change refactors many aspects of the Section Objects feature in NT-compatible kernel, making it more compatible with Windows.</description> </item> <item> <title>Download</title> <link>https://reactos.org/download/</link> <pubDate>Sat, 23 Jan 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/download/</guid> <description>Discover our latest and greatest ReactOS 0.4.14 Download Boot CD Alternatively, you can download LiveCD How to choose? If you wish to install ReactOS on your machine, then Boot CD is the right option for you. Boot CD will direct you to a setup environment, please follow the instructions given on the screen. Live CD is useful if you don't plan to keep ReactOS on your computer for a longer period of time.</description> </item> <item> <title>ReactOS in 2020</title> <link>https://reactos.org/project-news/reactos-in-2020/</link> <pubDate>Sat, 02 Jan 2021 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-in-2020/</guid> <description>Despite all the turbulence, it has been quite a productive year for ReactOS. Many bugs and instabilities were resolved, many more have been introduced. This year we hired two kernel developers full-time, this happened for the first time in the project&rsquo;s history.The post highlights some of the changes which may be interesting to the community.Shell changes Shell hasn&rsquo;t seen much attention recently, due to most of the work being concentrated in the kernel, but there are still some useful fixes and feature implementations:</description> </item> <item> <title>Jérôme Gardou hired full-time to work on the memory manager</title> <link>https://reactos.org/project-news/jerome-gardou-hired-full-time/</link> <pubDate>Mon, 26 Oct 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/jerome-gardou-hired-full-time/</guid> <description>I proudly announce that ReactOS Deutschland e.V. has hired Jérôme Gardou to work full-time on the ReactOS kernel&rsquo;s memory manager for the next 3 months.Jérôme is a ReactOS veteran who has been contributing to the project since 2009. He has deep expertise into nearly all parts of ReactOS, ranging from various user-mode components (mostly related to low-level graphics) over their kernel-mode counterparts and down to bare-metal components like the kernel memory manager.</description> </item> <item> <title>Porting Syzkaller to ReactOS Final Evaluation - GSoC 2020</title> <link>https://reactos.org/blogs/porting-syzkaller-to-reactos-final/</link> <pubDate>Tue, 01 Sep 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/porting-syzkaller-to-reactos-final/</guid> <description>Hello everyone, I am Suraj K Suresh, the one working on the GSoC project of &ldquo;Porting Syzkaller to ReactOS&rdquo;. It&rsquo;s been 3 whole months since GSoC has begun and this is the last evaluation period. During the last 3 months, I worked on various parts of Syzkaller and getting them up and running on ReactOS and Windows with the help of my Mentors. This blog post will be a wrap-up post of the GSoC project.</description> </item> <item> <title>Detect kernel information disclosure by Bochspwn-reloaded - GSoC 2020 - Final report</title> <link>https://reactos.org/blogs/gsoc-2020-memory-disclosure-final-report/</link> <pubDate>Mon, 31 Aug 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2020-memory-disclosure-final-report/</guid> <description>After 3 months since the last blog, I found and pull the patches of 12 memory disclosure bugs: [NTOS:PS] Fix stack memory disclosure in PsGetContextThread: merged [Win32SS][USER] Fix stack memory disclosure in NtUserBuildPropList: merged [MOUNTMGR] Fix pool memory disclosure in QueryPointsFromMemory: merged [Win32SS][GDI] Fix pool memory disclosure in NtGdiGetGlyphOutline: merged [DRIVERS] Fix pool memory disclsoure in CreateDiskDeviceObject of disk driver: closed [NTGDI] Fix stack memory disclosure in NtGdiGetTextMetricsW: merged [NTOS:KE] Fix stack memory disclosure in KiInitializeUserApc: merged [NTOS:IO] Fix pool memory disclosure in IopQueueTargetDeviceEvent: merged [Win32SS][GDI] Fix pool memory disclosure in NtGdiGetOutlineTextMetricsInternalW: merged [WIN32SS][NTUSER] Fix uninitialized memory cause memory disclosure used for KeUserModeCallback: merged [FILESYSTEMS] Fix pool memory disclosure in filesystem drivers supporting FS_INFORMATION_CLASS.</description> </item> <item> <title>Rapps Enhancement final report - GSoC 2020</title> <link>https://reactos.org/blogs/gsoc-2020-rapps-final-report/</link> <pubDate>Sat, 29 Aug 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2020-rapps-final-report/</guid> <description>Hi, I&rsquo;m He Yang (@kernel.bin), one of the GSoC-2020 students of ReactOS. How time flies, three months have passed and now GSoC is coming to an end. During the last three months, I&rsquo;ve been working on rapps, and I&rsquo;ve made some small progress on it: improving rapps by increasing it&rsquo;s functionality, stability, and make the code more well-organized.During GSoC, I&rsquo;ve acquired a lot of coding skills and knowledge about Win32.</description> </item> <item> <title>Syzkaller - Fuzzing ReactOS in 2020</title> <link>https://reactos.org/blogs/fuzzing-reactos/</link> <pubDate>Sun, 09 Aug 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/fuzzing-reactos/</guid> <description>Hello everyone. In this blog post, I will be talking about the steps to set up Syzkaller for ReactOS locally and start fuzzing. If you have been following the blog posts on the ReactOS website then you would have noticed that this is my Google Summer of Code 2020 Project. Now that Coding period 2 has officially come to an end and the work is nearing completion, this post will help others in setting up the fuzzer get started with fuzzing.</description> </item> <item> <title>Rapps Enhancement stage 1 & 2 - GSoC 2020</title> <link>https://reactos.org/blogs/gsoc-2020-rapps-stage12/</link> <pubDate>Sat, 08 Aug 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2020-rapps-stage12/</guid> <description>Hi, I&rsquo;m He Yang (@kernel.bin), one of the GSoC-2020 students of ReactOS. Two months have passed since GSoC started, and during these two months, I&rsquo;ve made some progress on ReactOS Application Manager (RAPPS), the project I&rsquo;m working on.In this blog, I will list out what I&rsquo;ve accomplished in these two months, and what I&rsquo;m planning to do in the next month.The work I&rsquo;ve done in Stage 1&amp;2 Stage 1 During stage 1, I mainly focused on screenshot and icon support and various small improvements.</description> </item> <item> <title>June 2020 meeting minutes</title> <link>https://reactos.org/project-news/june-2020-meeting-minutes/</link> <pubDate>Thu, 30 Jul 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/june-2020-meeting-minutes/</guid> <description>2020-06-2519:00 UTCMattermost meeting channelProceedings Meeting started at 19:01 by Colin Finck. Point 1: Achievements and Future Outlook Point 2: GSoC 2020 Status Point 3: Channel moderation Point 4: 0.4.14 release status Point 5: Unifying our contribution guidelines and handling Pull Requests Point 1: Achievements and Future Outlook Amine Khaldi worked on the built-in PCH CMake, the flex/bison PR and some other minor tasks.Can Taşan continued to test Microsoft Office 2003 on ReactOS and caught two regressions.</description> </item> <item> <title>Victor Perevertkin hired full-time to work on the storage stack</title> <link>https://reactos.org/project-news/victor-perevertkin-hired-full-time/</link> <pubDate>Tue, 14 Jul 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/victor-perevertkin-hired-full-time/</guid> <description>I am proud to announce that ReactOS Deutschland e.V. has hired Victor Perevertkin to work full-time on the ReactOS storage stack for the next 3 months.Victor has been a proven contributor to various ReactOS components since 2018. He already got deep into the kernel side of things when writing Btrfs boot sector code in his GSoC debut, later managed the integration of a new USB stack, and recently touched nearly all parts of ReactOS when preparing it for the major upgrade to a new compiler toolchain.</description> </item> <item> <title>Porting Syzkaller to ReactOS (Evaluation-1) - GSoC 2020</title> <link>https://reactos.org/blogs/porting-syzkaller-to-reactos-1-gsoc2020/</link> <pubDate>Tue, 30 Jun 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/porting-syzkaller-to-reactos-1-gsoc2020/</guid> <description>Hey, I am Suraj K Suresh (@Freakston), In this post I&rsquo;m going to be listing out what I&rsquo;ve completed in Coding period-1 of GSoC.Status The initial part of setting up Syzkaller and being able to fuzz ReactOS is done. The link to grab ReactOS compatible syzkaller is as follows: Github.The detailed instruction on setting it up can be found here.Work-done Boot ReactOS with UBSan enabled. The branch which has UBSan enabled can be found in extravert34&rsquo;s fork of ReactOS.</description> </item> <item> <title>Detect kernel information disclosure by Bochspwn-reloaded - GSoC 2020 - First week</title> <link>https://reactos.org/blogs/gsoc-memory-disclosure-week-1/</link> <pubDate>Thu, 04 Jun 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-memory-disclosure-week-1/</guid> <description>Introduction Hello, I am Nguyen Trung Khanh (@khanhnt) from Vietnam and I am one of the GSoC students of ReactOS.My project is running ReactOS on bochspwn-reloaded to list and fix all the bugs which were found by the tool. Additionally, I have a week to implement detection of uninitialized memory use.The first week Before GSoC, I did compile bochspwn-reloaded and run ReactOS on it so my work in the first week is pretty easy.</description> </item> <item> <title>Porting Syzkaller to ReactOS - GSoC 2020</title> <link>https://reactos.org/blogs/porting-syzkaller-to-reactos-gsoc-2020/</link> <pubDate>Thu, 04 Jun 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/porting-syzkaller-to-reactos-gsoc-2020/</guid> <description>Hey, I am Suraj K Suresh (@Freakston), one of the GSoC students of ReactOS.This is the first time I&rsquo;ve applied for GSoC and my mentors for the project are Victor Perevertkin and Timo Kreuzer.My project is &ldquo;Porting Syzkaller to ReactOS&rdquo;. The project is getting one of the most famous Linux fuzzers to fuzz ReactOS. The project will lead to improvement of the kernel codebase by detecting code crashes.</description> </item> <item> <title>Rapps Enhancement - GSoC 2020</title> <link>https://reactos.org/blogs/gsoc-2020-rapps/</link> <pubDate>Thu, 04 Jun 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2020-rapps/</guid> <description>Hello, I am He Yang (@kernel.bin) from China. This year, I signed up for GSoC, and I&rsquo;m very glad to be given the chance to work with the ReactOS team.My mentors for the project are Mark Jansen and Ioannis Adamopoulos. It&rsquo;s a great honor to have two mentors to guide me.My project is &ldquo;Application manager RAPPS&rdquo;. RAPPS is used by almost everyone using ReactOS, thus making it essential to get RAPPS easy-to-use, powerful and bug-free.</description> </item> <item> <title>ReactOS Build Environment 2.2 released</title> <link>https://reactos.org/project-news/rosbe-22-released/</link> <pubDate>Fri, 01 May 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/rosbe-22-released/</guid> <description>The ReactOS Build Environment (RosBE), our curated set of compilers and build tools, has just received a major upgrade.After more than 7 years of using the same and now ancient GCC 4.7.2, ReactOS is finally going to be built with the help of a modern compiler (GCC 8.4.0). Among other things, the new version better detects programming mistakes like improperly sized buffers, and comes with improved error messages to pinpoint such mistakes to the corresponding position in code.</description> </item> <item> <title>March 2020 meeting minutes</title> <link>https://reactos.org/project-news/march-2020-meeting-minutes/</link> <pubDate>Tue, 14 Apr 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/march-2020-meeting-minutes/</guid> <description>2020-03-2619:00 UTCMattermost meeting channelProceedings Meeting started at 19:05 by Colin Finck. Point 1: Achievements and Future Outlook Point 2: GSoC 2020 Status Point 3: Drop one theme from the default package Point 4: Hire a developer for dev-web interface and/or devops for our infrastructure Point 5: GitHub PR situation Point 1: Achievements and Future Outlook Stanislav Motylkov is currently preparing a cumulative update for his SMBIOS parser code in sysdm.</description> </item> <item> <title>ReactOS 0.4.13 released</title> <link>https://reactos.org/project-news/reactos-0413-released/</link> <pubDate>Fri, 10 Apr 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0413-released/</guid> <description>The ReactOS Team is pleased to announce the release of version 0.4.13. As with prior releases, keywords are noted representing the release itself and highlighting key improvements. In this particular case, the 0.4.13 version shows the results of significant hard work to bring improvements to the USB stack, further development on the Xbox port boot process, an Explorer File Search for the Shell module, as well as many other changes.</description> </item> <item> <title>Gallery</title> <link>https://reactos.org/gallery/</link> <pubDate>Wed, 25 Mar 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/gallery/</guid> <description>Applications Manager File Search VLC Neverball Teeworlds AssaultCube Epiphany XnView LibreOffice Writer Picodrive PuTTY ReactOS on VirtualPC 2007 HexEdit</description> </item> <item> <title>Contribute to ReactOS</title> <link>https://reactos.org/contributing/</link> <pubDate>Sun, 22 Mar 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/contributing/</guid> <description>The ReactOS Project always seeks new qualified contributors from all skill levels. No matter if you are a developer, tester, editor or designer, your contribution is highly appreciated. Please see below for all available positions and contact us via Mattermost or the mailing lists.Every year we participate in Google Summer of Code which is a program by Google that lets you work with us during the summer to work on a major project.</description> </item> <item> <title>The New ReactOS Website</title> <link>https://reactos.org/project-news/the-new-reactos-website/</link> <pubDate>Sat, 21 Mar 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/the-new-reactos-website/</guid> <description>Today, I am pleased to announce the launch of the new ReactOS website.Several old and new ReactOS members have worked on it since Hackfest 2018 with the goal of providing a lean website with a focus on development activity and contributions.It was born out of frustration with the old site, which made following ReactOS progress unnecessarily difficult. With its CMS also long past its due date, it was decided to create a modern ReactOS website from scratch using the excellent Hugo static site generator.</description> </item> <item> <title>What is ReactOS?</title> <link>https://reactos.org/what-is-reactos/</link> <pubDate>Sat, 21 Mar 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/what-is-reactos/</guid> <description>ReactOS is an operating system.Our own main features are: ReactOS is able to run Windows software ReactOS is able to run Windows drivers ReactOS looks-like Windows ReactOS is free and open source What to do next? Joining &amp; Following ReactOS Progress Interested in ReactOS development Check out the gallery How can ReactOS help me? Being part of a Worldwide Community, as ReactOS is, will boost your own personal skills to a highest new level.</description> </item> <item> <title>Legal Disclosure</title> <link>https://reactos.org/legal/</link> <pubDate>Tue, 17 Mar 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/legal/</guid> <description>Responsible for the content of these pages is:ReactOS Deutschland e.V.Am Bach 1133378 Rheda-WiedenbrückGermanyPlease be advised that the contacts below do not provide support for ReactOS.E-Mail: deutschland@reactos.orgWebsite: https://ev.reactos.orgReactOS Deutschland e.V. is a registered charitable Association under German law.Represented by Board members Matthias Kupfer (President), Daniel Reimer (Vice President), Pierre Schweitzer (Vice President), Colin Finck (Treasurer).Further legal information is provided below in German as required by German law.</description> </item> <item> <title>Intellectual Property Guideline</title> <link>https://reactos.org/intellectual-property-guideline/</link> <pubDate>Sun, 23 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/intellectual-property-guideline/</guid> <description>Preface The ReactOS&trade; Project is an international group of developers whose goal is to create a work-alike version of the Microsoft Windows operating system. In light of recent activity in the free software world relating to copyright and patent concerns, the administrators of the ReactOS Project feel that a general guideline would be helpful for developers and potential contributors. For questions regarding this guideline, please e-mail Colin Finck. Please note that none of this should be construed as legal advice, as any sort of warranty regarding the project&#39;s products, or anything else save a statement of policy on the part of the project.</description> </item> <item> <title>Donate</title> <link>https://reactos.org/donate/</link> <pubDate>Sun, 09 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/donate/</guid> <description>We need your help! ReactOS is not supported by any company or government. Donations are the only way to maintain the project's server infrastructure, and provide us with a way to farm out development tasks which our unpaid devs don't always have the time to complete.We really rely on you to donate your time or money, and are grateful for all of your support!PayPal and Wire Transfers are tax deductible.</description> </item> <item> <title>ReactOS Architecture</title> <link>https://reactos.org/architecture/</link> <pubDate>Sat, 08 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/architecture/</guid> <description>Interested in ReactOS development? Becoming a ReactOS developer is both simple and rewarding. The codebase allows developers of all different backgrounds and skillsets to find something that interests them, and allows them to get going quickly using our excellent build environment.The challenge of working on a mainstream operating system is something many people are interested in, however the opportunities to do so are rather limited. Linux and BSD are the obvious choices, but not everyone wants to work in a unix environment or are put off by the vast scale of unix communities and the large choice on offer.</description> </item> <item> <title>January 2020 meeting minutes</title> <link>https://reactos.org/project-news/january-2020-meeting-minutes/</link> <pubDate>Fri, 07 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/january-2020-meeting-minutes/</guid> <description>2020-01-3019:00 UTCMattermost meeting channelRegular meetings are now resumed, and so are the meeting minutes. The meetings are currently planned to be held bi-monthly going forward.Proceedings Meeting started at 19:01 by Colin Finck.Point 1: Our GSoC 2020 Application Point 2: RosBE 2.2 and what's blocking it Point 3: ReactOS 0.4.13 and what's blocking it Point 4: FOSDEM: Planning for the upcoming weekend in Brussels Point 1: Our GSoC 2020 Application The deadline for GSoC 2020 is the 5th of february.</description> </item> <item> <title>FAQ</title> <link>https://reactos.org/faq/</link> <pubDate>Sat, 01 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/faq/</guid> <description>Following What is ReactOS? ReactOS is a free and open source operating system written from scratch. Its design is based on Windows in the same way Linux is based on Unix, however ReactOS is not Linux. ReactOS looks and feels like Windows, is able to your run Windows software and your Windows drivers, and is familiar to Windows users.Free and open source? Free and Open Source. Free as &ldquo;you can download it for free&rdquo;, and open source.</description> </item> <item> <title>Joining</title> <link>https://reactos.org/joining/</link> <pubDate>Sat, 01 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/joining/</guid> <description>Joining &amp; Following ReactOS Progress! Tracking the progress and development of an Operating System is an exciting and educational experience. You can get a glimpse into how things work behind the scenes, see bugs fixed in a daily basis, peek into or get involved in ReactOS developer discussions, or even join Community efforts. Daily updates Communicating Mailing list Joining Daily updates through Facebook and Twitter. ReactOS on Facebook ReactOS on Twitter Be Part of the ReactOS Community!</description> </item> <item> <title>Mailing Lists</title> <link>https://reactos.org/mailing-lists/</link> <pubDate>Sat, 01 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/mailing-lists/</guid> <description>The ReactOS Project maintains several mailing lists to coordinate development and send out announcements.The current active lists are: Announcement List - Subscribe | Unsubscribe | Information | ArchivesOfficial announcements General List - Subscribe | Unsubscribe | Information | ArchivesGeneral discussion about ReactOS Developers List - Subscribe | Unsubscribe | Information | ArchivesDiscussions regarding ReactOS development A list of all current and former mailing lists can be found here.</description> </item> <item> <title>Thank you!</title> <link>https://reactos.org/thank-you/</link> <pubDate>Sat, 01 Feb 2020 00:00:00 +0000</pubDate> <guid>https://reactos.org/thank-you/</guid> <description>Thank you for your contribution! ReactOS is a non-profit organization and we&rsquo;ll ensure that your money is properly placed into ReactOS development. We are seeking ReactOS Recurrent Donors in order to ensure a steady development.If you need a receipt please contact deutschland@reactos.org</description> </item> <item> <title>ReactOS 0.4.12 released</title> <link>https://reactos.org/project-news/reactos-0412-released/</link> <pubDate>Mon, 23 Sep 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0412-released/</guid> <description>The ReactOS team is pleased to announce the release of version 0.4.12. As always a multitude of improvements have been made to all parts of the OS, though userland components saw special emphasis this time around. Kernel improvements Filesystem drivers require a great deal of support to function correctly, and there is arguably no truer test of ReactOS&rsquo; FS infrastructure than being able to run Microsoft&rsquo;s own FS drivers.</description> </item> <item> <title>GSoC 2019 - File Search (Final Report)</title> <link>https://reactos.org/blogs/gsoc-2019-file-search-final-report/</link> <pubDate>Mon, 26 Aug 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-file-search-final-report/</guid> <description>This is a summary of all the work that has been completed this summer on the file search project.All contributed code can be found in this GitHub pull request.Summary Here is a list of the main features: Quickly open it from the Start menu or with the keyboard shortcut Windows + F Search is case-insensitive and recurses all sub-folders Support for UTF-16 encoded text files File name filtering with support for wildcards "</description> </item> <item> <title>GSoC 2019 - Developer Web Interface for ReactOS (Final Report)</title> <link>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-final-report/</link> <pubDate>Tue, 20 Aug 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-final-report/</guid> <description>Introduction Developer Web Interface for ReactOS is a web tool to support the development of ReactOS. The main goal of this project is to develop a platform for ReactOS developers to easily track Commits, Builds and Test details. The web Interface makes API calls to various endpoints of GitHub, BuildBot and Testman API and interrelates them and renders a simplified view of Commit, Build and Test details at one place, so developers don&#39;t have to visit different sites to view different details, our web Interface collects all details and displays at one place.</description> </item> <item> <title>Installation</title> <link>https://reactos.org/installation/</link> <pubDate>Mon, 19 Aug 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/installation/</guid> <description>This page is not finished yet. You can help by improving it: This needs to be included or linked somewhereInstalling ReactOS is very much like installing Windows XP. However, due to it still undergoing heavy development, a few pointers are helpful when first getting started.Installation Platform ReactOS currently supports running on x86 processors with x64 support still in development. In additional to real hardware, ReactOS also supports running on a variety of virtual machine platforms.</description> </item> <item> <title>Installing ReactOS</title> <link>https://reactos.org/installing-reactos/</link> <pubDate>Mon, 19 Aug 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/installing-reactos/</guid> <description>This page is not finished yet. You can help by improving it: This needs to be included or linked somewhereAs ReactOS is still in alpha stage development, we encourage would-be testers to first try it out on a virtual machine before taking the plunge with real hardware. Of course regardless of whether you do a physical or virtual install there are some basic requirements to keep in mind. x86 processor, Pentium-class or newer 96MB of RAM, 256MB recommended 650MB of free space minimum, 5GB+ recommended if you intend to do testing VGA compatible graphics card, VESA BIOS 2.</description> </item> <item> <title>Participation</title> <link>https://reactos.org/participation/</link> <pubDate>Mon, 19 Aug 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/participation/</guid> <description>This page is not finished yet. You can help by improving it: This needs to be linked somewhere, and the content needs to be updatedGetting Involved with ReactOS There are many different ways to get involved with ReactOS. Immense time and effort went into creating the NT family of operating systems, including Windows XP and 2003. As ReactOS aspires to be a replacement for Windows, the same amount of resources would ensure the rapid progress of the project.</description> </item> <item> <title>GSoC 2019 - Developer Web Interface for ReactOS (Week 3 & 4)</title> <link>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-week-3-4-0/</link> <pubDate>Wed, 10 Jul 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-week-3-4-0/</guid> <description>Hello Everyone !! Until week 2 we made API calls to the Branches and Commits Endpoint of the GitHub API and rendered it. So at the end of week 2, we were able to fetch Top 5 commits from any of the branches as required. Week 3 UI Improvement Till week 2 we just had a simple table showing a few very basic information about the commits. So we designed a collapsible Panel which can contain all information required from the API.</description> </item> <item> <title>Inside ReactOS Deutschland e.V. - Annual Report 2018</title> <link>https://reactos.org/project-news/inside-reactos-deutschland-ev-annual-report-2018/</link> <pubDate>Sun, 23 Jun 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/inside-reactos-deutschland-ev-annual-report-2018/</guid> <description>The Annual Report 2018 of ReactOS Deutschland e.V., the non-profit organization supporting the ReactOS Project, has just been finished.In the past, these reports have exclusively been published on the ReactOS Deutschland e.V. subsite, but only got little attention there. Hence, the latest report is now released on the main ReactOS website.In our quest for transparency, we hope that the report offers an insight into the foundation's activities in 2018 and the plans for 2019.</description> </item> <item> <title>GSoC 2019 - RAPPS</title> <link>https://reactos.org/blogs/gsoc-2019-rapps/</link> <pubDate>Tue, 11 Jun 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-rapps/</guid> <description>Introduction Hello everyone, This is Akshay Patil, 3rd-year B.E CS student from VIIT Pune, lately working on RAPPS. The Google Summer of code, abbreviated as GSoC is an annual program in which Google pairs University Students to work with open source organizations and then awards stipends to students who are able to meet project milestones. This Summer I am working with ReactOS to improve RAPPS. ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.</description> </item> <item> <title>GSoC 2019 - File Search (Update 1)</title> <link>https://reactos.org/blogs/gsoc-2019-file-search-update-1/</link> <pubDate>Sat, 08 Jun 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-file-search-update-1/</guid> <description>Introduction Hello, My name is Brock Mammen and I am a student for Google Summer of Code 2019. This is my second year as a GSoC student, but it is my first year contributing to ReactOS. My project is to create a search extension for the ReactOS shell. I am excited to learn more about how the shell works and how to use ATL and COM to create user interfaces.</description> </item> <item> <title>GSoC 2019 - Developer Web Interface for ReactOS (Community Bonding and week 1,2)</title> <link>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-community-bonding-and-week-12/</link> <pubDate>Fri, 07 Jun 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2019-developer-web-interface-reactos-community-bonding-and-week-12/</guid> <description>Introduction Hey Everyone, I'm Ayush Kumar Sinha, A 2nd Year CS undergraduate from VIT Vellore, India and a GSoC student this year under ReactOS : )How I got to know about the project While scrolling through the list of accepted Orgs of 2018 (with filters like web, C++, javascript)I bumped into ReactOS. Hey!! they are building Windows-like OS from scratch, Sounds cool :). But the project ideas look quite hard with my existing C/C++ skills.</description> </item> <item> <title>New Discussion Platform</title> <link>https://reactos.org/project-news/new-discussion-platform/</link> <pubDate>Wed, 13 Mar 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-discussion-platform/</guid> <description>After decades on IRC and around 3 months of internal testing, the ReactOS Project has officially switched to a self-hosted Mattermost server as its main discussion platform.Mattermost is a modern open-source solution for team communication, eliminating many of the limits of IRC: Ever missed an opportunity to contact a person, because that person wasn't on IRC at the same time as yourself? Ever thought &quot;A picture is worth a thousand words&quot;, but were too lazy to look up an image hosting service, publish your image there, and then post a link to IRC?</description> </item> <item> <title>February 2019 meeting minutes</title> <link>https://reactos.org/project-news/february-2019-meeting-minutes/</link> <pubDate>Sun, 10 Mar 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/february-2019-meeting-minutes/</guid> <description>2019-02-2819:00 UTCMattermost meeting channelProceedings Meeting started at 19:01 by Colin Finck. Point 1: Status Reports Point 2: Final decision on Mattermost Point 3: Google Summer of Code 2019 Point 4: 0.4.11 Point 5: Chemnitzer Linux-Tage 2019 Point 1: Status Reports Alexander Rechitskiy tried to get the source code of a network card driver from Intel, but got the response that they can't provide an open source license for it.</description> </item> <item> <title>ReactOS 0.4.11 released</title> <link>https://reactos.org/project-news/reactos-0411-released/</link> <pubDate>Mon, 04 Mar 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0411-released/</guid> <description>The ReactOS team is pleased to announce the release of version 0.4.11. This version has seen substantial work done to the kernel, helping improve overall system stability.Kernel Improvements While the term kernel is used as a sort of catch-all term, in truth the range of functionality that it encapsulates is quite wide. One case in point is the kernel&rsquo;s responsibility for managing file I/O. A mistake here can cause subtle data corruption to more obvious hard crashes.</description> </item> <item> <title>ReactOS participating in Google Summer of Code 2019</title> <link>https://reactos.org/project-news/reactos-participating-google-summer-code-2019/</link> <pubDate>Thu, 28 Feb 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-participating-google-summer-code-2019/</guid> <description>The ReactOS Project is proud to announce its participation in Google Summer of Code 2019. The Summer of Code program offers students interested in operating systems the unique opportunity to dive into ReactOS development over the course of 3 months and get paid by Google for completed tasks. ReactOS has successfully participated in Summer of Code multiple times in the past. Completed projects include better filesystem support, an improved Application Manager, and a more stable network stack - just to name a few.</description> </item> <item> <title>December 2018 meeting minutes</title> <link>https://reactos.org/project-news/december-2018-meeting-minutes/</link> <pubDate>Sun, 24 Feb 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/december-2018-meeting-minutes/</guid> <description>2018-12-2019:00 UTC#meetingProceedings Meeting started at 19:15 by Colin Finck. Point 1: Status Reports Point 2: NT6+ strategy Point 3: Compilers upgrade Point 1: Status Reports Amine Khaldi reported that he worked on Wine syncs.Colin Finck finished the backup of all our old servers/VMs and could finally terminate the contracts for 3 servers we had in use more or less unchanged for 5 years.</description> </item> <item> <title>January 2019 meeting minutes</title> <link>https://reactos.org/project-news/january-2019-meeting-minutes/</link> <pubDate>Sun, 24 Feb 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/january-2019-meeting-minutes/</guid> <description>2019-01-2419:00 UTCMattermost meeting channelProceedings Meeting started at 19:00 by Colin Finck, which is our first on Mattermost! Point 1: Status Reports Point 2: Mattermost Point 3: Google Summer of Code 2019 Point 4: TeamCity Point 1: Status Reports Alexander Rechitskiy did several bug reports and rechecked old bug reports. He conducted an experiment on crowdfunding work of Katayama Hirofumi MZ. Apart from that, he also did PR work.</description> </item> <item> <title>November 2018 meeting minutes</title> <link>https://reactos.org/project-news/november-2018-meeting-minutes/</link> <pubDate>Sun, 24 Feb 2019 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/november-2018-meeting-minutes/</guid> <description>2018-11-2919:00 UTC#meetingProceedings Meeting started at 19:01 by Colin Finck. Point 1: Status Reports Point 2: Web and Infrastructure Projects Point 3: Jira tickets workflow Point 4: ReactOS 0.5 Planning Point 5: ReactOS Deutschland e.V. Update and ReactOS Hackfest(s) 2019 Point 6: All-in-one ISOs combining Live-CD and GUI Installer Point 1: Status Reports Aleksey Bragin mostly dropped by to say hi. But he also mentioned he was getting ready for some infrastructure work together with Colin.</description> </item> <item> <title>ReactOS 0.4.10 released</title> <link>https://reactos.org/project-news/reactos-0410-released/</link> <pubDate>Tue, 06 Nov 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0410-released/</guid> <description>The ReactOS project is pleased to announce the release of version 0.4.10, the latest of our quarterly cadence of releases. The project has seen an increasing emphasis on consistency and stability over the past few months, an emphasis the rapid release schedule helps reinforce to provide a better end-user experience. Even as new pieces of functionality are added, all this would be for naught if a user could not access them reliably.</description> </item> <item> <title>August 2018 meeting minutes</title> <link>https://reactos.org/project-news/august-2018-meeting-minutes/</link> <pubDate>Sun, 23 Sep 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/august-2018-meeting-minutes/</guid> <description>2018-08-3019:00 UTC#meetingProceedings Meeting started at 19:05 by Colin Finck. Point 1: Status Reports Point 2: Slack / Mattermost Point 1: Status Reports Andreas Bjerkeholt did some translation work. He also got started coding for zipfldr with help from Mark, and fixed button states. He plans to continue work on zipfldr in the future.Colin Finck tackled one of the ideas from the Hackfest idea list together with Mark Jansen, namely the move of the website to a static site generator.</description> </item> <item> <title>GSoC 2018 - Final report</title> <link>https://reactos.org/blogs/gsoc-2018-final-report/</link> <pubDate>Fri, 17 Aug 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2018-final-report/</guid> <description>Introduction WinBtrfs is a feature-complete IFSD (Installable File System Driver) for NT operating systems, written by Mark Harmstone. This driver is checked into the ReactOS source code for some time already. My main goal for this GSoC project was to implement all missing features (and fix bugs, of course) in ReactOS that prevents booting from BTRFS file system.Links All work is merged into gsoc2018_all branch in my ReactOS fork on GitHub.</description> </item> <item> <title>July 2018 meeting minutes</title> <link>https://reactos.org/project-news/july-2018-meeting-minutes/</link> <pubDate>Thu, 16 Aug 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2018-meeting-minutes/</guid> <description>2018-08-0219:00 UTC#meetingProceedings Meeting started at 19:01 by Colin Finck. Point 1: Status Reports Point 2: Upcoming Hackfest Point 3: Splitting off ReactOS components into Git submodules Point 4: Celebrating 20 years of ReactOS Point 1: Status Reports Alexander Rechitskiy did some PR work for ReactOS and spread info about recent developments and the 0.4.9 release.Aleksandar Andrejevic mentioned he is thinking about continuing his audio work.</description> </item> <item> <title>GSoC 2018 - booting from BTRFS works!</title> <link>https://reactos.org/blogs/gsoc-2018-booting-btrfs-works/</link> <pubDate>Sun, 29 Jul 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2018-booting-btrfs-works/</guid> <description>Hi, all!Here is what happened since last post:Freeloader is now able to read files and follow symlinks from btrfs partition. One major issue is left here - case sensitivity. BTRFS is case-sensitive file system, so paths like /ReactOS/System32, /reactos/system32, /ReactOS/system32 are different here. But in Windows world most software is written assuming that case does not matter during path lookup. This thing is solved in WinBtrfs driver, but for Freeloader it can be a bit tricky.</description> </item> <item> <title>ReactOS 0.4.9 released</title> <link>https://reactos.org/project-news/reactos-049-released/</link> <pubDate>Mon, 23 Jul 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-049-released/</guid> <description>The ReactOS Project is pleased to announce the release of version 0.4.9, the latest in our accelerated cadence targeting a release every three months.While a consequence of this faster cycle might mean fewer headliner changes, much of the visible effort nowadays comes in the form of quality-of-life improvements in how ReactOS functions. At the same time work continues on the underlying systems which provide more subtle improvements such as greater system stability and general consistency.</description> </item> <item> <title>June 2018 meeting minutes</title> <link>https://reactos.org/project-news/june-2018-meeting-minutes/</link> <pubDate>Sun, 22 Jul 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/june-2018-meeting-minutes/</guid> <description>2018-06-2819:00 UTC#meetingProceedings Meeting started at 19:04 by Mark Jansen, as Colin Finck was running late. Point 1: Status Reports Point 2: ReactOS Hackfest on August 16-21 Point 3: 0.4.9 release on July 14 Point 4: Website developer/maintainer Point 1: Status Reports Amine Khaldi is doing the usual, Wine syncs and anything he can help with.Colin Finck has been working on authentication modules for RosLogin and the final migration script.</description> </item> <item> <title>GSoC 2018 - boot sector finished</title> <link>https://reactos.org/blogs/gsoc-2018-boot-sector-finished/</link> <pubDate>Tue, 10 Jul 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2018-boot-sector-finished/</guid> <description>Hi all! Sorry, haven’t written anything for a while. Let me tell you what have been done since last post. BTRFS boot sector TL;DR: It works! I’ve been able to load main bootloader code from freeldr.sys into memory, transfer control to it and get on error message (freeldr.sys can’t find its config file - I haven’t written second-stage BTRFS code yet). It was not that easy because we are in x86 real mode when running boot sector thus only about 1mb of memory is available.</description> </item> <item> <title>Website upgraded</title> <link>https://reactos.org/project-news/website-upgraded/</link> <pubDate>Wed, 04 Jul 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/website-upgraded/</guid> <description>Today, the ReactOS Website has been migrated to a new Login system and all components have been upgraded to their latest versions.In the course of that, the user database has also been moved and cleaned from accounts that have never been used.Such large migrations hardly go without issues, so if you notice anything wrong, please report a bug in our JIRA bugtracker.You are also advised to change your password in the Self-Service, even if it's just to the same one.</description> </item> <item> <title>GSoC 2018 weeks 3-4 - understanding BTRFS internals</title> <link>https://reactos.org/blogs/gsoc-2018-weeks-3-4-understanding-btrfs-internals/</link> <pubDate>Thu, 14 Jun 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2018-weeks-3-4-understanding-btrfs-internals/</guid> <description>Hi all!This two weeks I was diving into btrfs structures and on-disk layout. Writing an ASM program from scratch is not that simple so I decided to convert a VirtualBox image with BTRFS filesystem in it to raw file and write a python script to parse and show internal filesystem structures. It was also useful for understanding how files are stored in FS, because information on btrfs.</description> </item> <item> <title>May 2018 meeting minutes</title> <link>https://reactos.org/project-news/may-2018-meeting-minutes/</link> <pubDate>Wed, 06 Jun 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/may-2018-meeting-minutes/</guid> <description>2018-05-3119:00 UTC#meetingProceedings Meeting started at 19:03 by Colin Finck Point 1: Status Reports Point 2: Improving our handling of PRs and JIRA reports Point 3: Google Summer of Code Point 4: Changes affecting base addresses Point 5: Miscellaneous Point 1: Status Reports Amine Khaldi is doing the usual, Wine syncs and anything he can help with.Colin Finck finished his university studies after almost 7 years!</description> </item> <item> <title>GSoC 2018 - Project BTRFS Boot</title> <link>https://reactos.org/blogs/gsoc-2018-weeks-1-2/</link> <pubDate>Tue, 29 May 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-2018-weeks-1-2/</guid> <description>Introduction Hi all!My name is Victor Perevertkin and I am the only GSoC student in ReactOS project this year :)This is my first GSoC and I was very excited when I realized that I was selected and there will be four mentors for me. I will definitely learn a lot from this internship!My project is both simple and complicated. I want to add to ReactOS an option to install on and boot from BTRFS partitions.</description> </item> <item> <title>April 2018 meeting minutes</title> <link>https://reactos.org/project-news/april-2018-meeting-minutes/</link> <pubDate>Tue, 01 May 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/april-2018-meeting-minutes/</guid> <description>2018-04-2619:00 UTC#meetingProceedings Meeting started at 19:01 by Colin Finck Point 1: Status Reports Point 1: Status Reports Aleksandar Andrejevic had nothing to report, except that he now has some free time. He is currently looking at where he left off.Amine Khaldi is doing what he usually does, addressing anything he can help with, working on the Wine staging syncs etc.Colin Finck helped getting 0.</description> </item> <item> <title>ReactOS 0.4.8 released!!</title> <link>https://reactos.org/project-news/reactos-048-released/</link> <pubDate>Sat, 14 Apr 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-048-released/</guid> <description>The ReactOS Project is pleased to announce the release of version 0.4.8 as we continue to work on releasing every three months.As you may know, our previous 0.4.7 version was the first one developed in our Git/GitHub repository. 0.4.8 is the nice sequel and a good way to measure the GitHub impact on the ReactOS project. Since ReactOS reached GitHub, it has been forked 248 times. A nice amount understanding ReactOS is not a framework or a library, but a final product.</description> </item> <item> <title>March 2018 meeting minutes</title> <link>https://reactos.org/project-news/march-2018-meeting-minutes/</link> <pubDate>Tue, 03 Apr 2018 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/march-2018-meeting-minutes/</guid> <description>2018-03-2919:00 UTC#meetingProceedings Meeting started at 19:08 by Colin Finck Point 1: Status Reports Point 2: GSoC Point 3: 0.4.8 Status and Release Planning Point 4: Hackfest Point 5: USB Patches Point 6: Code of Conduct Point 1: Status Reports Aleksey Bragin has been busy with his full time job as CTO. He doesn't have enough time for ReactOS, and suggests to elect a new Project Coordinator.</description> </item> <item> <title>ReactOS 0.4.7 released!</title> <link>https://reactos.org/project-news/reactos-047-released/</link> <pubDate>Wed, 06 Dec 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-047-released/</guid> <description>The ReactOS Project is pleased to announce the release of version 0.4.7 as we continue to work on releasing every three months.We’re especially pleased to present this release as the very first one that’s been developed in our new Git/GitHub repository. Moving from Subversion to GitHub has proven to be an invaluable way to reach new testers, users and improve the overall awareness of the ReactOS project.To highlight the impact we’ve had since we moved to GitHub two months ago, ReactOS now leads the Win32Api and OsDev categories in Github, overtaking many amazing and well established projects.</description> </item> <item> <title>The day after: ReactOS in the OpenSourceLisbon...</title> <link>https://reactos.org/project-news/day-after-reactos-opensourcelisbon/</link> <pubDate>Mon, 16 Oct 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/day-after-reactos-opensourcelisbon/</guid> <description>28th September was a sunny and amazing day for us, the open source lovers. During the whole day, the Universidade Nova de Lisboa held the #OpenSourceLx event. The biggest and free open source event in Portugal.Projects and companies as Syone, RedHat, Microsoft, Elastic, FSF, IpBrick, among others, were offering simultaneous talks during the event. In this edition ReactOS was invited to talk about the project evolution during 45 minutes in the "</description> </item> <item> <title>ReactOS Repository migrated to GitHub</title> <link>https://reactos.org/project-news/reactos-repository-migrated-github/</link> <pubDate>Tue, 03 Oct 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-repository-migrated-github/</guid> <description>Today, the ReactOS Source Code has been migrated from a central Subversion instance to a decentralized Git repository. Together with that, ReactOS joins the list of projects using the popular GitHub service for developing software. We expect that this move greatly improves the way we collaborate on ReactOS development and reduces the barriers for newcomers. Just fork our repository on GitHub, commit your changes and send us a Pull Request!</description> </item> <item> <title>Join ReactOS in Open Source Lisbon 2017</title> <link>https://reactos.org/project-news/join-reactos-open-source-lisbon-2017/</link> <pubDate>Sat, 23 Sep 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/join-reactos-open-source-lisbon-2017/</guid> <description>As you may know ReactOS, during this year, has been already shown in Belgium, Germany and Spain in several open source events. We're always looking forward to be part of new events and reach new countries. ReactOS has been selected by the Open Source Lisbon organization to be part of their event on 28th September. An amazing opportunity to reach a new country ( this is our first time ever in Portugal ) from the hand of the biggest open source FREE event in Portugal.</description> </item> <item> <title>ReactOS 0.4.6 released</title> <link>https://reactos.org/project-news/reactos-046-released/</link> <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-046-released/</guid> <description>The ReactOS Project is pleased to release version 0.4.6 as a continuation of its three month cadence. 0.4.6 is a major step towards real hardware support. Several dual boot issues have been fixed and now partitions are managed in a safer way avoiding corruption of the partition list structures. ReactOS Loader can now load custom kernels and HALs. Printing Subsystem is still greenish in 0.4.6, however Colin Finck has implemented a huge number of new APIs and fixed some of the bugs reported and detected by the ReactOS automated tests.</description> </item> <item> <title>GSoC NTFS 2017 - Work Summary</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-work-summary/</link> <pubDate>Tue, 29 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-work-summary/</guid> <description>This is a detailed summary of the work I've performed over the course of Google Summer of Code 2017. This was a continuation of my GSoC project from last year.Code Submitted You can check out my branch with SVN at https://svn.reactos.org/reactos/branches/GSoC_2016/NTFSYou can find a list of commits made to my branch during GSoC 2017 at this link.I also worked on this project after GSoC last year and before the coding period officially began this year.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition Final Report</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-final-report/</link> <pubDate>Mon, 28 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-final-report/</guid> <description>Introduction ReactOS App Manager (RAPPS) is an app used in ReactOS to download apps, tested by ReactOS team and community. It also manages apps that are installed - you can view apps that are present on your system and uninstall them. The goal of this project was to improve RAPPS and add some very useful features.Here is a video presenting it's features: Quick Links SVN branch link Unified diff as a Gist Commits Overview Table of contents Introduction Building Testing Changes made during development Application List Improvements Bulk installing Script installation Other improvements Future work Conclusions Building Building RAPPS is no different as building parts of ReactOS.</description> </item> <item> <title>GSoC’17 : Project Taskbar Shell Extensions for ReactOS | Final Report</title> <link>https://reactos.org/blogs/gsoc17-project-taskbar-shell-extensions-reactos-final-report/</link> <pubDate>Sun, 27 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc17-project-taskbar-shell-extensions-reactos-final-report/</guid> <description>Hello, everyone! It&rsquo;s me, Shriraj (a.k.a sr13).The time has come to summarize all the work I have done in this Summer of Code with ReactOS and complete this journey of my first ever GSoC, though my story with ReactOS is just beginning!TL;DR of Project Taskbar Shell Extensions: # Designed &amp; Implemented the Quick Launch Toolbar for ReactOS. # Designed &amp; Added support for Battery Status in notification area (System Tray).</description> </item> <item> <title>GSoC xHCI: Final Submission</title> <link>https://reactos.org/blogs/gsoc-xhci-final-submission/</link> <pubDate>Fri, 25 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-xhci-final-submission/</guid> <description>Links: Link to my work:https://svn.reactos.org/svn/reactos/branches/GSoC_2017/usbxhci/reactos/drivers/usb/usbxhci/Link to check out using svn:https://svn.reactos.org/reactos/branches/GSoC_2017/usbxhci/reactos/All the commits log:https://svn.reactos.org/svn/reactos/branches/GSoC_2017/usbxhci/?view=loghttps://code.reactos.org/changelog/~br=GSoC_2017/reactos/branches/GSoC_2017/usbxhci?max=30&amp;view=feIntroduction: My aim is to develop driver for xHCI which is compatible with ReactOS. For the development I&rsquo;ve used Windows 2003 server edition running on Vmware Workstation. The first link points to the folder in which all main code and header files are present. To view any file, click on it and in the log; against any revision, click on view/download to see the code.</description> </item> <item> <title>GSOC Project TSE Week 11 : Last but not the least...</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-11-last-not-least/</link> <pubDate>Sun, 20 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-11-last-not-least/</guid> <description>Hello, everyone! 0/As you can see in the title, this is officially the last week of coding but not the least as we still have a week left until final evaluation period ends. As we are coming close towards the end of GSoC, you all might feel sad as I won't be able to share about my work anymore... :`( But hold your hankies, fellas, GSoC might end soon but my journey with ReactOS is just beginning.</description> </item> <item> <title>GSoC NTFS 2017 Update 10</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-10/</link> <pubDate>Sat, 19 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-10/</guid> <description>Home stretch! Just a matter of days before Google opens up the GSoC final submission! I'll be using every minute I have available to me in the interim.Splitting A B-Tree Node Have I finally finished my magnum opus, allowing for file creation without limits on the number of files? Well, the bad news is, no, I still have more work to do on this. The good news, however, is I have this working in ReactOS!</description> </item> <item> <title>GSoC xHCI: PCS and CCS</title> <link>https://reactos.org/blogs/gsoc-xhci-pcs-and-ccs/</link> <pubDate>Thu, 17 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-xhci-pcs-and-ccs/</guid> <description>Finally the driver is generating multiple interrupt without any issues. Whenever a device is connected or disconnected an interrupt is being generated. In windows 2003 server edition, when a device is attached windows is recognizing that some unknown device is attached and also in the device manager we can see attached devices though they are not initiated. This is a crucial step, as now any USB device can be safely initiated.</description> </item> <item> <title>GSoC NTFS 2017 Update 9</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-9/</link> <pubDate>Sat, 12 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-9/</guid> <description>Last week went pretty well! :)In my last post, I talked about how I needed to refactor some code to fix a bug. I'm really happy with how this turned out.Refactoring As I mentioned before, the driver has a struct called an NTFS_ATTR_CONTEXT which keeps track of information related to attributes. The main purpose of the structure is to keep vital information about the attribute cached in memory, but it's also just a convenient way to pass information about attributes between functions and the driver relies on it quite extensively.</description> </item> <item> <title>GSOC Project TSE Week 10</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-10/</link> <pubDate>Sat, 12 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-10/</guid> <description>Hi, everyone! 0/Tick-Tock is coming to an end, and the next week is perhaps the last week of coding before final evaluation starts! ;P But let's be calm and discuss what happened last week. And as promised, I managed to get some demonstrable snaps this time. So, here we go!As told in my last blog, we got some flashy new icons for the stobject modules I worked on.</description> </item> <item> <title>xHCI : A life lesson learnt</title> <link>https://reactos.org/blogs/xhci-life-lesson-learnt/</link> <pubDate>Mon, 07 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/xhci-life-lesson-learnt/</guid> <description>Recently I’ve worked on Scratchpad allocation. Scratchpad buffers are PAGESIZE blocks of system memory which the xHCI uses to store its internal state. xHCI can request 0 to 1024 buffers. Number of buffers required is given in the HCSPARAMS1 register. Each buffer is a PAGESIZE block aligned to PAGESIZE boundary. Scratchpad buffer array is an array which contains addresses of the scratchpad buffers. Its size is equal to the number of maximum scratchpad buffers required by the hardware.</description> </item> <item> <title>GSOC Project TSE Week 9</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-9/</link> <pubDate>Sat, 05 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-9/</guid> <description>Hey there, its Shriraj here! 0/We are already in week 9 of this 12-week journey of GSoC! Soon about to take the final lap, but wait we have a lot to do before that. This time too I don't have any pics as such to show visible progress, but yeah let's see through words what I managed to do last week. ;PWhat I did Last week? As I told in my last blog, we are currently working to find the appropriate enumeration filters required for safely removable devices, but as that feature is being tested on a standalone console app, I was free to prepare the stobject of ReactOS to welcome the hotplug!</description> </item> <item> <title>GSoC NTFS 2017 Update 8</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-8/</link> <pubDate>Thu, 03 Aug 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-8/</guid> <description>Hello World!I know it hasn't been very long since the last update. The last few updates were late, but I'm trying to get back into good habits like committing often and blogging on time. :)Last time, I talked about how ReactOS was corrupting my test volume by trying to create files I wasn't ready for it to create. I was indeed able to fix that by booting into Windows and creating the folder and files ReactOS kept trying to make.</description> </item> <item> <title>GSoC NTFS 2017 Update 7</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-7/</link> <pubDate>Mon, 31 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-7/</guid> <description>Hi everyone! Last week I left off with an example of creating files, showing you how an index node fills up with file names. Once the node in a B-Tree gets too full, it needs to be split. I've been working on this for a while and I was expecting that I'd have an example of this working. I even delayed writing this post because I was so sure this feature was almost ready.</description> </item> <item> <title>GSOC Project TSE Week 8 : Phase 3</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-8-phase-3/</link> <pubDate>Mon, 31 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-8-phase-3/</guid> <description>Hey there! 0/Sorry for posting my blog late this time :P. Was kinda busy with my family duties, besides some errands. Also, my college is starting from this week. As devs, we are better coders than writers but yeah, as a GSoC norm, blogging is a healthy habit which keeps us updated. ;)About this phase Let's keep it short this time, as I told in my last blog we are officially in the final phase of the project.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition Volume 5</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-5/</link> <pubDate>Sat, 29 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-5/</guid> <description>It's very good when things go as planned. And they do! The BULK INSTALL&nbsp;is here! Let's have a look. Checkboxes are useful Now you can select a bunch of apps in the app bar. In the statusbar you can see selected app count. Selection drops when the categories are switched.&nbsp;Using "Select/Deselect button" will select all apps in the current view.&nbsp;Install all apps at once Pressing "</description> </item> <item> <title>GSoC xHCI status update</title> <link>https://reactos.org/blogs/gsoc-xhci-status-update-0/</link> <pubDate>Fri, 28 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-xhci-status-update-0/</guid> <description>In this post I’m going to detail my work progress. In the past week I’ve decided to clean up the code. Some parts of the code was re-written as functions. After that I’ve started working on the USB port status function. When an interrupt is generated the code is getting stuck in a loop. I’m trying to figure out what caused it. As we’ve discussed in the previous blog post.</description> </item> <item> <title>GSoC NTFS 2017 Update 6</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-6/</link> <pubDate>Mon, 24 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-6/</guid> <description>Hello again! :)Last week, I finished the code that writes a B-Tree node to disk. Specifically, it lets me write the node to an index buffer within the index allocation of the parent directory. Don't worry if that doesn't make sense, I'll explain it more below.From a user's perspective, this means that the driver now has the ability to create dozens of files. My tester will create 39 files before filling the index node.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition Volume 3 and 4</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-3-and-4/</link> <pubDate>Fri, 21 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-3-and-4/</guid> <description>Whoosh! Two weeks flew by in no time! Fortunately, I've done many things and have some screenshots to show!Before we start, I have an anouncement: I'm going to Hackfest and FroSCon this August! I may not be very useful there, but I can discuss things related to the project, meet my mentor Mark Jansen and other devs. I will also learn from the ReactOS developers and FrOSCon workshops. &nbsp;</description> </item> <item> <title>GSOC Project TSE Week 7</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-7/</link> <pubDate>Thu, 20 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-7/</guid> <description>Hello World!! ;DIf you had read my last blog then you already know that we are in "Phase 2". And whats exciting is this phase zoomed past at such a speed that in the upcoming week I am starting "Phase 3". (Spoiler Alert! XP) But, let us hold our horses and let me describe what happened in Phase 2. For a TL;DR you can just check the Task 2.</description> </item> <item> <title>XHCI Ring Data Structures </title> <link>https://reactos.org/blogs/xhci-ring-data-structures/</link> <pubDate>Tue, 18 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/xhci-ring-data-structures/</guid> <description>xHC functioning mostly depends on different ring data structures. In this blog post I’m going to detail what a ring is in XHCI and various implementations by Linux and Haiku. A ring is a circular queue of data structures. There are three kinds of rings in xHC. 1. Command ring2. Event Ring3. Transfer Ring These rings are the basis of communication with the Controller. Command Ring is used to send commands to the controller.</description> </item> <item> <title>GSoC NTFS 2017 Update 5</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-5/</link> <pubDate>Thu, 13 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-5/</guid> <description>Last week I got back to writing B-Tree code. Sadly, the week flew by before I could come up with anything screenshot-able. I've been updating the B-Tree code to accommodate index allocations, and trees of arbitrary depth. I'm mostly done with this but I still have to finish the code that saves an index buffer to the index allocation. Once I do that, I should be able to demonstrate creating dozens of files in a directory.</description> </item> <item> <title>GSOC Project TSE Week 6 : Phase 2</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-6-phase-2/</link> <pubDate>Thu, 13 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-6-phase-2/</guid> <description>Hey, guys!Six weeks have passed since I started my journey of coding with ReactOS. It was a wonderful time full of learning, coding, and fun. In terms of productivity, this week was not that great as compared to weeks before. But I can say it was an essential decision making and learning week. So I started this week, by resuming the task of patching up the remaining issues of CR-122.</description> </item> <item> <title>GSoC: USBxHCI driver development work status</title> <link>https://reactos.org/blogs/gsoc-usbxhci-driver-development-work-status/</link> <pubDate>Thu, 13 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-usbxhci-driver-development-work-status/</guid> <description>Welcome to my third blog post. Sorry for the missed blog post from last week. I was stuck over an issue which kept me occupied. With the help of community I finally got over it. I had to calculate an address by adding a value taken from another register to the base address. This led to a typecast issue. Due to huge number of steps required to generate interrupt I didn't suspect the problem to be where it is initially.</description> </item> <item> <title>ReactOS Hackfest 2017 and FrOSCon17!</title> <link>https://reactos.org/project-news/reactos-hackfest-2017-and-froscon17/</link> <pubDate>Fri, 07 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-hackfest-2017-and-froscon17/</guid> <description>The ReactOS Team is proud to announce that ReactOS has been selected to be present in the FrOSCon17 event.&nbsp; FrOSCon 2017 FrOSCon is a free software and open source event organized by the University of Applied Sciences Bonn-Rhein-Sieg (Germany) full of talks, workshops and booths. Entry is absolutely free so there is no excuse not to meet the ReactOS team live. This event takes place on 19th and 20th August so feel free to book your flights or plan a nice weekend to visit our booth there.</description> </item> <item> <title>GSoC NTFS 2017 Update 4</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-4/</link> <pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-4/</guid> <description>I won't lie; it's been a slow week, feature-wise.I guess you could say that last week was all about finding and fixing bugs and errors with the driver. During the first half of the week, I upgraded my automated tester to test file creation, and I fixed a couple of bugs it turned up. I used the second half of the week for addressing issues raised by CR-123.</description> </item> <item> <title>GSOC Project TSE Week 5</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-5/</link> <pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-5/</guid> <description>Hey there! 0/Last time you must have seen some snapshots of where the QuickLaunch has reached. Seeing the UI and some functionalities in the snaps must have given you a feeling that it's complete and finished. But, Nah... a lot of work is left, besides debugging so that Dr. Watson would finally be free of his postmortems!! XPComing straight to the point, this week the best thing was about 'Code Reviews'.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition Volume 2.1</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-21/</link> <pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-21/</guid> <description>You may wonder why this post is not labeled "Volume 3". Well, thanks to the training week of the military dept. of our university this week wasn't very productive in terms of features. Nevertheless, this short post is here to keep you updated.This week I was working on refactoring the code and improving code. This will help me progress faster and addd new feature more easily. It is not the only reason: RAPPS was initially written in C and had been converted to C++.</description> </item> <item> <title>GSoC NTFS 2017 Update 3</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-3/</link> <pubDate>Thu, 29 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-3/</guid> <description>All continues to go well :). Two weeks ago, I started writing code to parse B-Trees, which are representative of how NTFS organizes its directories on disk.It works like this: First, the index of a directory is read and converted to a B-Tree in memory. Next, a key for the new file is inserted into the tree. Finally, the tree is converted back to an index root attribute which is written to disk.</description> </item> <item> <title>GSOC Project TSE Week 4</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-4/</link> <pubDate>Thu, 29 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-4/</guid> <description>Hi, everyone!! So you all are still with me? Good!! ;)As I had told last week, that this week will be rather an exciting one, and yes it indeed was. And the reason is, finally, you all will see a working (prototype) of the quick launch band. (yay!!) Let me go through chronologically, what I did this week. The first thing was to Implement the IShellFolderBand. This is a very important interface as it helps to initialize the IShellFolder and PIDL (via its InitializeSFB method) required to enumerate the folder objects.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition Volume 2</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-2-2/</link> <pubDate>Thu, 29 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-volume-2-2/</guid> <description>Another week - another update! This time I worked on the license info, update checking and other improvements to my work. These changes bring up many under-the-hood changes.Dont worry, these changes may not look huge. I'm adding features and then worry about the visuals :)&nbsp; But first things first. Let's have a look. Before After &nbsp;Update check RAPPS can now suggest and update if the version installed is less than in the database.</description> </item> <item> <title>xHC Operational Model Overview</title> <link>https://reactos.org/blogs/xhc-operational-model-overview/</link> <pubDate>Thu, 29 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/xhc-operational-model-overview/</guid> <description>In this post I’m going to give some details on the working of xHC along with my progress. In my opinion Driver development is for the most part thoroughly studying the documentation. I’m working towards my next major target i.e., Implementing Control transfer. In this process I’ve faced some unforeseen issues. From the previous USB models and the available driver code my estimates of xHC turned out to be inadequate.</description> </item> <item> <title>GSOC Project TSE Week 3</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-3/</link> <pubDate>Mon, 26 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-3/</guid> <description>Hey there! Great to see you all in my 4th blogpost of this series. ;)So far, so good!! No blockers and nothing to worry about, and just being around reactos community is pure fun. Coming straight to the point, this week I continued what I had left last time and that was the james band... err.. i mean CISFBand!! XPAfter forwarding the methods of the built in system CISFBand and testing its integrity within live virtual machine, the next thing to do was to replace this system CISFBand with my own implementation of it.</description> </item> <item> <title>RAPPS Enchancements: GSoC 2017 Edition</title> <link>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-0/</link> <pubDate>Sat, 24 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rapps-enchancements-gsoc-2017-edition-0/</guid> <description>Introduction My name is Alexander Shaposhnikov, i'm a GSOC student from Ukraine working on ReactOS App Manager (RAPPS) project. Last two weeks was extrodinary hard - university work took all the time. Fortunately it was dealt with and I'm working at full capacity. I don't like to write stories in the blog so I'll keep this blog short and informative. And with screenshots!Changes During this 3 weeks I've made some changes to visual part and to the RAPPS DB.</description> </item> <item> <title>GSoC NTFS 2017 Update 2</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-2/</link> <pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-2/</guid> <description>All is going well :). Since the last update, I've checked off a minor TODO related to file creation: increasing the size of the master file table, if needed. Every time the mft grows, it creates several empty file records at a time. In the past, I was using this to my advantage, and was only creating files in empty slots that already existed. Every time I got an error saying there wasn't enough space for a new file, I'd boot into Windows, create a file (which would increase the mft size), and get back to testing.</description> </item> <item> <title>Interrupt mechanism: eHCI vs xHCI</title> <link>https://reactos.org/blogs/interrupt-mechanism-ehci-vs-xhci/</link> <pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/interrupt-mechanism-ehci-vs-xhci/</guid> <description>This blog post is first one of a series of posts which will deal with various topics related to xHCI (usb 3.0). I'm Rama Teja one of the participants in GSOC 2017. My project is to develop xHCI driver for ReactOS with the help of my mentor Thomas Faber. In the xHCI documentation given by Intel there are three major topics i.e., Register Interface, Data Structures and Operational model. The hardware controller's register interface is used to send commands to it or get the status etc.</description> </item> <item> <title>GSOC Project TSE Week 2</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-2/</link> <pubDate>Tue, 20 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-2/</guid> <description>Hello friends, its Shriraj again. ;)Its already second week of the coding period, and I was enjoying my time as a beginner dev in reactos. Learning new things every now and then and just being on irc is a sheer fun. So as decided last time, we had an official gsoc meeting on #reactos-gsoc. I explained and summarized what I was able to do last week. Also planned what Ill be doing next.</description> </item> <item> <title>GSoC NTFS 2017 Update 1</title> <link>https://reactos.org/blogs/gsoc-ntfs-2017-update-1/</link> <pubDate>Thu, 15 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-ntfs-2017-update-1/</guid> <description>Hello everyone! My name is Trevor Thompson. I'm a computer science major at Blue Ridge Community College living in Virginia. This is my second time participating in Google Summer of Code. I'm very happy to be working on ReactOS' NTFS driver again!Recap When I started last year, ReactOS could read files from an NTFS volume, but had no write support whatsoever. After GSoC last year, the driver in my branch could overwrite existing files.</description> </item> <item> <title>GSOC Project TSE Week 1</title> <link>https://reactos.org/blogs/gsoc-project-tse-week-1/</link> <pubDate>Thu, 15 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-project-tse-week-1/</guid> <description>Hi, its me Shriraj. :)This is my second blog on my GSoC project TSE(Taskbar Shell Extension).So, finally coding period began, and I was excited enough to pump out some code boiling within my mind! Sir Giannis (aka gadamopoulos) and Sir Sylvain (aka sdever) are my mentors in this project. In this first week, basically mentor Giannis showed me how to step into this huge codebase of reactos and helped me to get started by providing the canvas for my code.</description> </item> <item> <title>My first ever GSOC!!</title> <link>https://reactos.org/blogs/my-first-ever-gsoc/</link> <pubDate>Tue, 13 Jun 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/my-first-ever-gsoc/</guid> <description>#Introduction: Hi, I am shriraj (aka sr13), currently pursuing my B.Tech in CSE (Computer Science and Engineering) @ National Institute of Technology Goa, India. I am not just studying CSE but I like to play and experiment with CSE. Programming is just another hobby and I knew that its one of my forte the moment I had felt my first 'Hello World!!' with 'C'. (OK, that might be a little exaggeration XD, but yeah you can tell it when you start enjoying the subject so much that you felt code is better art than a poem.</description> </item> <item> <title>April 2017 meeting minutes</title> <link>https://reactos.org/project-news/april-2017-meeting-minutes/</link> <pubDate>Wed, 24 May 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/april-2017-meeting-minutes/</guid> <description>2017-04-2720:00 UTC#reactos-meetingProceedings Meeting started at 20:09 by Colin Finck Point 1: Status Reports Point 2: Release 0.4.5 Point 3: Vadim's USB work integration Point 3: Server infra discussion Point 1: Status Reports Aleksey_Bragin: He was mostly busy with server infrastructure and minor org things. Of course, he has ~30 students this year who are doing their work using ReactOS. So at least quite a few testers are testing it on a weekly basis.</description> </item> <item> <title>February 2017 meeting minutes</title> <link>https://reactos.org/project-news/february-2017-meeting-minutes/</link> <pubDate>Wed, 24 May 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/february-2017-meeting-minutes/</guid> <description>2017-02-2320:00 UTC#reactos-meetingProceedings Meeting started at 20:25 by Aleksey Bragin Point 1: Status Reports Point 2: USB status Point 3: Office status and NTLM Point 4: Tree restructure Point 1: Status Reports Aleksey Bragin: His main achievement for this month was finally installing the ReactOS hardware infrastructure together with Colin and Christoph. They brought the mothership back online, configured networks even better, as now he has fully separated networks at his house.</description> </item> <item> <title>January 2017 meeting minutes</title> <link>https://reactos.org/project-news/january-2017-meeting-minutes/</link> <pubDate>Wed, 24 May 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/january-2017-meeting-minutes/</guid> <description>2017-01-2620:00 UTC#reactos-meetingProceedings Meeting started at 20:16 by Colin Finck Point 1: FOSDEM participation Point 2: Status of scholarships Point 3: GSoC USB branch merging Point 3: Vadim's USB stack Point 1: FOSDEM participation Colin Finck started this topic giving recent information about FOSDEM participation and who will be there right now. He criticised the current planning a bit because noone knew if someone will be at the FOSDEM booth or not until very recently.</description> </item> <item> <title>October 2016 meeting minutes</title> <link>https://reactos.org/project-news/october-2016-meeting-minutes/</link> <pubDate>Wed, 24 May 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/october-2016-meeting-minutes/</guid> <description>2016-10-2720:00 UTC#reactos-meetingProceedings Meeting started at 20:31 by Aleksey Bragin Point 1: Status Reports Point 2: Hiring developers Point 3: GSoC merging Point 1: Status Reports Aleksey Bragin: He sold his startup, got a CTO position in a company which bought his startup, and ideally he should have more time, but it's not the case right now. So basically he was busy whole October and he started doing some research into software image processing for optical tech (his students, not him)</description> </item> <item> <title>ReactOS 0.4.5 Released</title> <link>https://reactos.org/project-news/reactos-045-released/</link> <pubDate>Thu, 18 May 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-045-released/</guid> <description>The ReactOS Project is pleased to release version 0.4.5 as a continuation of its three month cadence. Beyond the usual range of bug fixes and syncs with external dependencies, a fair amount of effort has gone into the graphical subsystem. Thanks to the work of Katayama Hirofumi and Mark Jansen, ReactOS now better serves requests for fonts and font metrics, leading to an improved rendering of applications and a more pleasant user experience.</description> </item> <item> <title>ReactOS has been accepted for GSOC'17</title> <link>https://reactos.org/project-news/reactos-has-been-accepted-gsoc17/</link> <pubDate>Mon, 27 Feb 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-has-been-accepted-gsoc17/</guid> <description>The ReactOS Team is proud to announce that Google has once again selected the ReactOS project to be part in the upcoming 2017 Google Summer of Code.This is the first time ReactOS has been accepted for GSOC two years consecutively, setting an important landmark in ReactOS’ history. No doubt the amazing work of the ReactOS mentors and students in the 2016 program contributed to make this possible.The GSOC program is a great opportunity to join recognized and skilled mentors with eager and skilled students alike.</description> </item> <item> <title>Word 2010 support Part 6: New progress</title> <link>https://reactos.org/blogs/word-2010-support-part-6-new-progress/</link> <pubDate>Mon, 27 Feb 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-part-6-new-progress/</guid> <description>Hello everyone, I'm summarizing here my latest progress towards making Word 2010 running in ReactOS. After having paused a little my ReactOS development during the first two weeks of February (due to personal matters), I started reviewing Samuel Serapión's NTLM code (in the "sspi-bringup" branch) and first focused on trying to convert his NTLM tests into something that can be included into our apitest framework. This is still work-in-progress because his original tests are interactive, and I need to find the good way of turning them into automated tests and finding a way to store the test results (for comparison purposes), as the tests are modeled around a client/server architecture.</description> </item> <item> <title>ReactOS 0.4.4 Released</title> <link>https://reactos.org/project-news/reactos-044-released/</link> <pubDate>Thu, 16 Feb 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-044-released/</guid> <description>Today marks the fifth release of the ReactOS 0.4.x series, as well as the fifth following the 3 month release cycle started by 0.4.0 itself. Progress has continued steadily, with a great deal of work going on in the background to improve ReactOS' general usability and stability. Many of these improvements were on display at the FOSDEM convention in Brussels that took place on the 4th and 5th of this month.</description> </item> <item> <title>ReactOS at FOSDEM 2017</title> <link>https://reactos.org/project-news/reactos-fosdem-2017/</link> <pubDate>Mon, 30 Jan 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-fosdem-2017/</guid> <description>The ReactOS project will be attending FOSDEM 2017 in Brussels, on Feburary 4th and 5th. The team will be represented by Colin Finck and Hermès BÉLUSCA-MAÏTO in the K Building, manning a joint booth with Adrien Destugues and François Revol from the HaikuOS project, which ReactOS has long had amicable relations with. Be sure to drop by and say hello to the gang, grab some CDs, and if the stars align play a few games.</description> </item> <item> <title>Word 2010 support Part 5: NTLM & FOSDEM 2017 preparation</title> <link>https://reactos.org/blogs/word-2010-support-weekly-report-part5-ntlm-fosdem-2017-preparation/</link> <pubDate>Mon, 30 Jan 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-weekly-report-part5-ntlm-fosdem-2017-preparation/</guid> <description>Hello everyone! As you've seen my activity in the blogs has been reduced quite a lot since beginning January,so here is a summary of what I did during the month of January.First two weeks of January (until ~= 15) In my previous report of last time, I explained that what blocked my progress on Word 2010 was the absence of NTLM authentication support for the installation to continue & finish.</description> </item> <item> <title>Developer Contract</title> <link>https://reactos.org/project-news/developer-contract/</link> <pubDate>Mon, 09 Jan 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/developer-contract/</guid> <description>The ReactOS Project is pleased to announce that it is appointing Giannis Adamopoulos as a paid developer. Many of you will recall that Giannis was one of the developers heavily responsible for getting the explorer-new shell into trunk, working extensively on the shell32 library that it depended upon. The objective of his current appointment is also shell related, and is specifically to work out the remaining issues in proper theme support, an oft requested feature by the community and one of the milestones of the Community Edition distribution.</description> </item> <item> <title>Word 2010 support – Weekly report - Part 4: Update + Authentication failed!</title> <link>https://reactos.org/blogs/word-2010-support-weekly-report-part4-update-authentication-failed/</link> <pubDate>Wed, 04 Jan 2017 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-weekly-report-part4-update-authentication-failed/</guid> <description>Hi everyone, let me first wish you a happy new year 2017! During the second half of last month (December) I did not have much time to work on ReactOS, hence the fact I could not write more reports for you to read. I was however able to test some stuff I started to work on during last November. I have started to familiarize and play a bit with the user-profile APIs inside userenv.</description> </item> <item> <title>Word 2010 support – Weekly report – Part 3: Installation progress</title> <link>https://reactos.org/blogs/word-2010-support-weekly-report-part3-installation-cont/</link> <pubDate>Tue, 06 Dec 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-weekly-report-part3-installation-cont/</guid> <description>Hello everybody. Today I am going to summarize my progress on Word 2010 installation so far, concerning the main two problems I did encounter: setting a correct environment block for services, and understanding why the SLInitialize function fails, leading to the failure of the Word 2010 installation. The third problem, namely correctly stopping services, will be addressed in a subsequent report. Reading the two previous weekly reports: "Part 1: Installation"</description> </item> <item> <title>Word 2010 support – Weekly report – Part 2: Installation (cont.)</title> <link>https://reactos.org/blogs/word-2010-support-weekly-report-part2-installation-cont/</link> <pubDate>Sun, 20 Nov 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-weekly-report-part2-installation-cont/</guid> <description>In this second report I continue my investigations on the Word 2010 installation. Last time we saw that our services (and in particular the "Office Software Protection Platform" OSPPSVC service) were started without a complete environment block, and as a result some needed environment variables were missing, causing e.g. OSPPSVC to fail opening some of its files. We now analyse what happens after my local fix (NOTE: I have not committed the fix yet, as I validate it in my local installation first).</description> </item> <item> <title>Word 2010 support – Weekly report – Part 1: Installation</title> <link>https://reactos.org/blogs/word-2010-support-weekly-report-part1-installation/</link> <pubDate>Sat, 19 Nov 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/word-2010-support-weekly-report-part1-installation/</guid> <description>Hello everyone, I am Hermès Bélusca-Maïto. This is my first week report, as part of the part-time scholarship that I started two weeks ago, that consists in making ReactOS being able to support Word 2010. Preliminaries Before starting anything with Word 2010 I needed to prepare a testing environment. Because I am a native Windows user, I use a ReactOS trunk build made with the MSVC compiler.</description> </item> <item> <title>ReactOS 0.4.3 Released</title> <link>https://reactos.org/project-news/reactos-043-released/</link> <pubDate>Wed, 16 Nov 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-043-released/</guid> <description>The ReactOS Project is pleased to announce the release of another incremental update, version 0.4.3. This would be fourth such release the project has made this year, an indication we hope of the steady progress that we have made. Approximately 342 issues were resolved since the release of 0.4.2, with the oldest dating all the way back to 2006 involving text alignment.Notable in this release is the switching to a new winsock library that had been started several years ago by Alex Ionescu and imported into trunk by Ged Murphy.</description> </item> <item> <title>ReactOS hires a new developer. Discover what's coming!</title> <link>https://reactos.org/project-news/reactos-hires-new-developer-we-re-hiring/</link> <pubDate>Tue, 08 Nov 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-hires-new-developer-we-re-hiring/</guid> <description>Ever since the IGG campaign was over, working on the ReactOS Community Edition has been one of our main priorities. Today we make another promising step towards achieving that goal.Although the IGG campaign was not a success, we were really proud of raising half of the needed funds. Nonetheless, and thanks to your valuable contributions, it was the most successful crowdfunding campaigns ReactOS has ever had.The IGG crowdfunding impact, your impact, on ReactOS is quite noticeable: A whole reworked shell thanks to hiring Giannis Adamopoulos then David Quintana (who among us misses the old shell!</description> </item> <item> <title>August 2016 meeting minutes</title> <link>https://reactos.org/project-news/august-2016-meeting-minutes/</link> <pubDate>Mon, 03 Oct 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/august-2016-meeting-minutes/</guid> <description>2016-08-2520:04 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 20:11 by Amine Khaldi Point 1: Status Reports Point 2: GSoC Point 3: 0.4.3 Release Plans GENERAL INFORMATIONStarting with this month meetings will be open to public. You may watch, but all non-devs are muted by default. If the meeting is set to invite-only when you try to join then we first discuss some private points before we open it to public.</description> </item> <item> <title>July 2016 meeting minutes</title> <link>https://reactos.org/project-news/july-2016-meeting-minutes/</link> <pubDate>Mon, 03 Oct 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2016-meeting-minutes/</guid> <description>2016-07-2820:00 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 20:11 by Amine Khaldi Point 1: Status Reports Point 2: 0.4.2 Release Plans Point 1: Status Reports Aleksey Bragin: He starts to get more free time now and tests ROS quite often recently. ReactOS keeps his C coding skills in shape right now which would be forgotten otherwise with all the .net C# he has to do. He plans to fix some release blockers soon.</description> </item> <item> <title>September 2016 meeting minutes</title> <link>https://reactos.org/project-news/september-2016-meeting-minutes/</link> <pubDate>Mon, 03 Oct 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/september-2016-meeting-minutes/</guid> <description>2016-09-2920:00 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 20:22 by Aleksey Bragin Point 1: Status Reports Point 2: 0.4.3 Release Plans Point 1: Status Reports [TheFlash]: He's still working on both the Sound Blaster driver and NTVDM VESA support, but right now he has to finish his M.Sc. thesis, so there will be a delay.Amine Khaldi: He's been looking after some long standing tasks we wanted to get into the 0.</description> </item> <item> <title>Google Summer of Code 2016 Conclusion</title> <link>https://reactos.org/blogs/google-summer-code-2016-conclusion/</link> <pubDate>Wed, 07 Sep 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-summer-code-2016-conclusion/</guid> <description>It's been a long but ultimately rewarding journey to the completion of Google Summer of Code 2016 for the ReactOS Project. As a project that seeks to implement an open source operating system based off of the NT architecture and compatible with both NT device drivers and Win32 applications, ReactOS faces some rather distinct challenges compared to other open source OS projects. With an emphasis on compatibility and familiarity, interest in the project has increased substantially after the major revamps the other family of NT operating systems has underwent over the past few years.</description> </item> <item> <title>Inside ReactOS Deutschland e.V.: Donations and how to automate them</title> <link>https://reactos.org/blogs/inside-reactos-deutschland-ev-donations-and-how-automate-them/</link> <pubDate>Thu, 25 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/inside-reactos-deutschland-ev-donations-and-how-automate-them/</guid> <description>Hi all! This is my first blog post designed to shed some light on the foundation behind ReactOS.Just like many other big Open-Source projects, ReactOS is backed by a foundation supporting the project financially and organizationally. I have been the treasurer of ReactOS Deutschland e.V. since its establishment in 2009 and as such, it has been my duty to do the tedious accounting of all donations. While most of that is happening in the background, you see the results from time to time when I update the public Donors page.</description> </item> <item> <title>Google SoC lwIP Conclusion</title> <link>https://reactos.org/blogs/google-soc-lwip-conclusion/</link> <pubDate>Tue, 23 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-conclusion/</guid> <description>My Google Summer of Code project proposal stated that I would add TCP support to the network branch of ReactOS, which sought to integrate lwIP 1.4.1 as the protocol level network driver for the operating system, to ultimately be tested by replacing the network driver in an installation of Windows Server 2003 with my driver. The full proposal can be found here. At the time of my proposal, I underestimated the amount of effort a fully working network driver would take.</description> </item> <item> <title>NTFS Write Support GSoC - Work Summary</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-work-summary-draft/</link> <pubDate>Tue, 23 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-work-summary-draft/</guid> <description>This is a detailed summary of the work I've performed during GSoC.Highlights Wrote numerous functions which allow for NTFS write-support. Expanded ReactOS' NTFS driver with the ability to overwrite files and change a file's size. Identified and repaired several bugs related to reading files from NTFS. Fixed ReactOS' LargeMCB implementation, facilitating support for four file systems, NTFS included (See CORE-11002). Diagnosed and fixed a regression using log files (See CORE-11707).</description> </item> <item> <title>Google SoC lwIP Report Week 13</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-13/</link> <pubDate>Mon, 22 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-13/</guid> <description>In this final week, I tried to do as much as possible to get my driver to some sort of usable state for simple network C programs.&nbsp;My first task this week was to fix a problem with port freeing. When a TCP connection dies, its lwIP PCB would sometimes remain, preventing new sockets from binding to the ports they are taking up. After a lot of tracing, I discovered that an lwIP internal semantic was at play.</description> </item> <item> <title>GSoC final report for USB project.</title> <link>https://reactos.org/blogs/gsoc-final-report-usb-project-0/</link> <pubDate>Mon, 22 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/gsoc-final-report-usb-project-0/</guid> <description>Here is my final blog post in terms of GSoC, but definitely not the last one in terms of contribution to ReactOS. I’ll try to share conclusion of my work done during this summer.&nbsp;First of all links &nbsp;Here are the links to GIT and SVN repositories containing my commits. These repos are identical, so for review or fork you can choose the one that is more eligible for you.</description> </item> <item> <title>NTFS Write Support GSoC - Week 12</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-12/</link> <pubDate>Thu, 18 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-12/</guid> <description>I said in my last update that I was aware GSoC was coming to an end, but in truth I don't think I realized just how close the end was coming. I need to be completely finished in much less than a week from now!Near the middle of the week, I was mostly finished with the code to create a new file record in memory. This progressed quickly, thanks to the time I put into diagnostic output and researching the file records that Windows creates.</description> </item> <item> <title>ReactOS 0.4.2 Released</title> <link>https://reactos.org/project-news/reactos-042-released/</link> <pubDate>Tue, 16 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-042-released/</guid> <description>The ReactOS Project is pleased to announce the release of version 0.4.2, again within three months of the previous release. The team sincerely hopes that this new rapid release cycle will hold for future releases as well. If there is one word to describe progress on the project, it would be steady. The project is reaching a point where rapid releases are viable, where disruption from introduction of major components or restructuring has been greatly reduced from the tumultuous early years and even as recently as the late 0.</description> </item> <item> <title>Google SoC lwIP Report Week 12</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-12/</link> <pubDate>Mon, 15 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-12/</guid> <description>In week 10, I had completed a major rewrite of my driver. In week 11, I dove into the problem of lwIP not being thread-safe once again. While I was able to deal with most of the individual bugs that kept popping up, each one was taking me more time to solve due to the haphazard nature of my previous fixes. At the beginning of last week, it was quickly becoming more apparent that I would need to rework most of my code once again if I wanted to have any hope of circumventing the multithreeading issue once and for all.</description> </item> <item> <title>Controlling (not just) Ctrl+C</title> <link>https://reactos.org/blogs/controlling-not-just-ctrlc/</link> <pubDate>Sat, 13 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/controlling-not-just-ctrlc/</guid> <description>Probably one of the funniest moments while developing is when you realize that something that "looks easy" is not as straight forward as it seemed at first sight.The task was "really easy": Just creating a console app which (1)loops infinitely, (2)doing some tasks and (3) which breaks when the user decides to stop it (4)printing some valuable info before exiting."Naaah, this is easy. I just need a while/for/do-while/whatever infinite loop, a printf message asking the user to press a specific key to stop it, then a getch() to capture the key in order to break/stop the loop, and finally another printf to print the valuable info: PROFIT!</description> </item> <item> <title>USB stack improvements GSoC - Week 11</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-11/</link> <pubDate>Wed, 10 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-11/</guid> <description>I spent last week moving from 2k3 to ROS. After doing final validation of my usbhub changes on 2k3, me and my mentor decided to move to some real world issues. I have setup my development and testing environment work with ROS instead of 2k3.VS-2015 as IDE for ROS First of all, I decided to use VS as IDE, to be able to use windbg as debugger. In that case I’ll have minimal changes on workflow I was using on 2k3 before.</description> </item> <item> <title>Google SoC lwIP Report Week 11</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-11/</link> <pubDate>Mon, 08 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-11/</guid> <description>This past week, I have primarily focused on thread-safety.&nbsp;Three weeks ago, I discovered that lwIP's core code is not thread-safe. When left unmodified, each lwIP thread will access several unprotected global linked lists as well as use a set of global variables to process any and all incoming packets. One option to solve this problem was to modify the core code so the global data was protected from concurrent access.</description> </item> <item> <title>NTFS Write Support GSoC - Weeks 9, 10, 11</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-weeks-9-10-11/</link> <pubDate>Fri, 05 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-weeks-9-10-11/</guid> <description>Wow, these weeks keep blazing by! Apologies for the missed updates; I've been faced with a family emergency for the past couple of weeks. My girlfriend's dad was in the hospital for 13 days after having a heart attack, getting a triple-bypass, then suffering from Ogilvie syndrome after surgery. He got out Saturday and is recovering. It's been a very long, scary time for my girlfriend and her family and she needed my support full-time.</description> </item> <item> <title>USB stack improvements GSoC - Week 10</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-10/</link> <pubDate>Tue, 02 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-10/</guid> <description>Since previous post I have done few tasks and learned a lot of things. Generally, I was reading and thinking about WDM’s PnP handling concepts. In general, I’ve improved my understanding of PnP and also learned about remove synchronization. Also I’ve investigated some corner cases and problems of WDM related remove synchronization topic. I think this learning is definitely a big investment into my future as NT driver developer.</description> </item> <item> <title>Google SoC lwIP Report Week 10</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-10/</link> <pubDate>Mon, 01 Aug 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-10/</guid> <description>Having rewritten all of the functions that I implemented and modified some of the functions that already existed before I started on this project at the end of last week, I now had to start flushing all of the bugs that invariably exist after a rewrite.&nbsp;The major issue I dealt with this past week revolved around properly handling a TDI_LISTEN.&nbsp;Part of the purpose for the rewrite was to reorganize my data so each TCP_CONTEXT struct represented a user socket or connection endpoint, and each ADDRESS_FILE struct only represented a local network address.</description> </item> <item> <title>Google SoC lwIP Report Week 9</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-9/</link> <pubDate>Mon, 25 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-9/</guid> <description>Last week ended with my realization that lwIP was not thread-safe, and me reading up on various ways to get around that.&nbsp;Last weekend, I spent a lot of time tinkering with lwIP's core code to see how hard it would be to make it thread-safe. I ultimately failed to actually make the library thread-safe, but I did learn a lot of things about lwIP that I hadn't known before I started digging into the source code in so much depth.</description> </item> <item> <title>SATA AHCI Driver GSoC - Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-update/</link> <pubDate>Mon, 25 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-update/</guid> <description>Links Short Brief Driver Testing Why no blog? Known Issues Short BriefSupported Features: Device Adapter Detection Non-Fatal Error Handling Adapter Srb PNP Request SCSIOP_INQUIRY : Device Inquiry SCSIOP_REPORT_LUNS : Report LUN SCSIOP_READ_CAPACITY : Device Geometry SCSIOP_TEST_UNIT_READY SCSIOP_READ : Device Read Request UnSupported Features: Fatal Error Handling SCSIOP_MODE_SENSE SCSIOP_WRITE NCQ : Native Command Queuing Cache and Priority Requests Driver TestingPlatform: Virtual Machine (Vmware)</description> </item> <item> <title>NTFS Write Support GSoC - Week 8</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-8/</link> <pubDate>Tue, 19 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-8/</guid> <description>Overwriting Files Continues This week has been pretty uneventful. I wrote a function to shrink the allocation size of an attribute and another to migrate a resident attribute to non-resident. The former seems to be working, the latter still needs some work. Looking Forward (Changing Direction) I'm only planning to spend another couple of days working on updating files, then I want to move on to file creation. There are several reasons motivating this thinking.</description> </item> <item> <title>Google SoC lwIP Report Week 8</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-8/</link> <pubDate>Mon, 18 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-8/</guid> <description>This past week started with me mindlessly chasing down memory bugs after having gotten WinDBG up and running. A particularly annoying bug involved an lwIP protocol control block being dereferenced by lwIP after it had been freed. I could not find a place in my drivere where I tried to use a dead PCB pointer, so I looked deeper. I did some stepping through of code, and read more of lwIP's source code.</description> </item> <item> <title>USB stack improvements GSoC - Week 8</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-8/</link> <pubDate>Mon, 18 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-8/</guid> <description>I have spent this week on improvements of realization and done stability fixes in usbhub PDO/FDO. &nbsp; I have prepared usbhub FDO's handling of removal and surprise-removal IRPs. We'll receive surprise-removal IRP on HUB unexpected removal, or on USB controller removal from PCI port. Here hub should "let know" all its children that their parent is removed and on next removal they also can be removed. For now this code path can't be tested because none of our host controllers can be removed now(they are failing query remove).</description> </item> <item> <title>NTFS Write Support GSoC - Week 7</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-7/</link> <pubDate>Wed, 13 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-7/</guid> <description>Assigning Clusters Part 2 I can't believe week seven has already passed! Adding assigned clusters to data runs turned out to be more challenging than I anticipated, but I made steady progress on it throughout the week and have it working now (as far as I can tell). Fixing the problems with LargeMcb.c in week 1 came full-circle, as I relied on a map control block to simplify my task considerably.</description> </item> <item> <title>USB stack improvements GSoC - Week 7</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-7/</link> <pubDate>Tue, 12 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-7/</guid> <description>I'll start this report from the good news. After starting GSoC's coding period, I was doing fixes and improvements of hub layer and was not repeating tests which was done by me in community bonding period (results provided in my first blog post). So by the end of this week I decided to test surprise-removal on VBox with 2k3 working with our USB stack. As result I saw that crashes on device removal (physical) are gone!</description> </item> <item> <title>Google SoC lwIP Report Week 7</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-7/</link> <pubDate>Mon, 11 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-7/</guid> <description>Last week ended with Art going through decompiled assembly to find a bug for me, because the stack trace in the kernel debugger was pointing me to the wrong line in the C source code. It turns out that the problem was a NULL pointer dereference in the RECEIVE callback. As always in programming, a lot of effort went into catching a small oversight.&nbsp;With that leftover bug from last week resolved, I moved on to my tasks for this week - more debugging, a code review done by Thomas Faber, and finally setting up WinDBG.</description> </item> <item> <title>NTFS Write Support GSoC - Week 6</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-6/</link> <pubDate>Wed, 06 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-6/</guid> <description>This week was rewarding, because I got some things done that I&#39;ve been wanting to do for a while.Assigning ClustersI wrote some code which can assign clusters by updating the $BITMAP file. As I mentioned last week, this is half of the equation for extending the allocation size of a non-resident file. I&#39;m still working on the other half, which involves storing the assigned clusters in data runs.</description> </item> <item> <title>USB stack improvements GSoC - Week 6</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-6/</link> <pubDate>Wed, 06 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-6/</guid> <description>This week I have continued fixes in PnP handling of our USB stack. I was focused on usbhub and done number of fixes there. Let me describe process from begining.Issue on MS's hidusb removal. As you may remember from previous post, now MS's usbccgp works under 2k3, sitting on the top of our ohci-hub pair. But that time I have also faced issue on it's removal. So to simplify debugging I have reproduced same issue with hidusb and saw the same behaviour under 2k3.</description> </item> <item> <title>Google SoC lwIP Report Week 6</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-6/</link> <pubDate>Sun, 03 Jul 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-6/</guid> <description>I closed out last week by drawing a flow chart in preparation for restructuring my code for some new state variables. For most of this week, I was figuring out details about, and implementing, this chart.&nbsp;One of new state variable I added in is one variable in the CONNECTION_CONTEXT struct, specifying what that particular connection is doing. This way, my driver can easily identify a socket as bound or not, whether it is currently connected, and what operations it is trying to perform.</description> </item> <item> <title>SATA AHCI Driver GSoC - Week 5 Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-5-update/</link> <pubDate>Wed, 29 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-5-update/</guid> <description>From beginning of week I started reading more stuffs (core) about AHCI and trying to plan a road map which I will follow after making first version of AHCI driver. Throughout the week I made some progress with Interrupt Handler and AHCI port programming. Though I have finished port programming routine and next I will complete Interrupt Handler followed by Srb functions.Port programming is still untested (fingers crossed), because I can't test it without Interrupt Handler routine (I can, but It will not give 100% surety) looking forward to get these two routines tested in this week.</description> </item> <item> <title>NTFS Write Support GSoC - Week 5</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-5/</link> <pubDate>Tue, 28 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-5/</guid> <description>Progress At the beginning of the week I finished cleaning up and committing the code I wrote related to extending a file's size. This took me a little longer than I expected and in the future I'm going to commit more often so I don't have this problem.From there I added support for truncating files, with a couple of caveats. This is significant because it allows for opening a file in Notepad.</description> </item> <item> <title>USB stack improvements GSoC - Week 5</title> <link>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-5/</link> <pubDate>Mon, 27 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-stack-improvements-gsoc-week-5/</guid> <description>After long period of investigation and debugging, this week I have commited first patches for review. And they make difference under 2k3 :)About fixes I've doneAs continuation of usbhub's PnP handler debug and testing, this week I have commited patches with fixes. The most important ones are described below (same description is given in commit messages too).&nbsp;PDO: Changed handling of IRP_MN_REMOVE_DEVICE On this IRP we should free recources and delete child's PDO ONLY if it isn't presented physically on the bus.</description> </item> <item> <title>Google SoC lwIP Report Week 5</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-5/</link> <pubDate>Sun, 26 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-5/</guid> <description>Going into week 5, I started with a code-complete but very much incorrect implementation of the TDI_SEND and TDI_RECEIVE IRQ handlers. My TCP_CONTEXT data structure and the existing ADDRESS_FILE data structure both did not contain a way to keep track of pending IRQs, so I had no way of keeping track of outstanding pending IRQs and what connection contexts they were supposed to be associated with. Without a clear scheme for keeping track of the information, IRP pointers invariably got lost.</description> </item> <item> <title>NTFS Write Support GSoC - Week 4</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-4/</link> <pubDate>Tue, 21 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-4/</guid> <description>Mid-term evaluations opened up yesterday, and naturally I've been super-busy this week, making sure I've earned my keep! ;)Getting the New Size Recognized in Windows Recall that I ended last week being able to extend a file's size in ReactOS, but Windows wasn't showing the newly written data when opening the file in notepad. My mentor Pierre and forum member Pathoswithin both suggested, independently, that my problems with extending a file might be caused by only increasing the size of the $DATA attribute and not also modifying the appropriate $FILE_NAME attribute associated with the file.</description> </item> <item> <title>SATA AHCI Driver GSoC - Week 4 Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-4-update-0/</link> <pubDate>Tue, 21 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-4-update-0/</guid> <description>This week I worked on AHCI IO Request Processing and FIS programming part. I implemented IO Queue, Slot distribution mechanism for AHCI requests. Updated Github's PR for next round of code review.Next I will be working on port programming i.e. telling the controller about the slots that I've allotted for IO request.Very soon we will have a running AHCI device driver :DI also added a notes.txt file which actually tracks my progress for every routine/support link</description> </item> <item> <title>USB 1.1 UHCI improvements GSoC - Week 4</title> <link>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-4/</link> <pubDate>Mon, 20 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-4/</guid> <description>TO LEARN HOW TO SWIM, YOU NEED TO GET INTO THE WATER. At the start of the week I was debugging the system crash on ROS's usbhub unload in Win2k3. I spent a lot of time asking questions and discussing topics related to WDM with my mentor Thfabba. He kind of kickstarted me, giving small tasks and then analyzing with me the results. During that sessions I have gathered many new tips related debugging and also started feeling much more confidently working with WDM.</description> </item> <item> <title>Google SoC lwIP Report Week 4</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-1-0/</link> <pubDate>Sat, 18 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-1-0/</guid> <description>This week, I started off chasing down how to handle TDI sending a new IRQ to create a connection context immediately after a connection has been accepted on the server end. At first, I thought it was for socket multiplexing. As I talked more with Art and looked more into the lwIP source code, I realized that this is an attempt by TDI to support backlogging. As such, this was not something I had to actively handle since lwIP has full backlogging support.</description> </item> <item> <title>Hello Telegram. A new #ReactOS channel</title> <link>https://reactos.org/project-news/hello-telegram-new-reactos-channel/</link> <pubDate>Fri, 17 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/hello-telegram-new-reactos-channel/</guid> <description>Hello Telegram! Technology keeps evolving and the ReactOS Community growing. We're proud to introduce a new way to keep in touch with ,and updated of, the latest #ReactOS news. The ReactOS project is probably one of the open source communities with a higher social network impact out there.Our ReactOS Twitter channel and ReactOS Facebook page are updated daily with the latest commits, news, and fixes thanks to a nifty integration with our development tools and, of course, some human care.</description> </item> <item> <title>SATA AHCI Driver GSoC - Week 3 Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-3-update/</link> <pubDate>Tue, 14 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-3-update/</guid> <description>I'll put my vision toward the version 1.0 of driver first. If we come to the uni_ata which is actually right now supporting React OS with SATA AHCI driver. uni_ata is actually operating SATA device in legacy mode of operation and with no support of NCQ. Although NCQ is not really necessary for now, because I think we are right now targeting to have hardware support as much as we can (this is as per my understanding).</description> </item> <item> <title>NTFS Write Support GSoC - Week 3</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-3/</link> <pubDate>Mon, 13 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-3/</guid> <description>Learning About NTFS I spent most of the week studying NTFS in-depth, and really learning about some of the things I glossed over before. This is something I had to do make meaningful progress with increasing file sizes. This involved (re-re-re-)reading the three relevant chapters in File System Forensic Analysis.Also, in order to retain and really understand the information, I&#39;ve started making a standalone app that lists files on an NTFS partition.</description> </item> <item> <title>USB 1.1 UHCI improvements GSoC - Week 3</title> <link>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-3/</link> <pubDate>Mon, 13 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-3/</guid> <description>This week I haven&rsquo;t spent much time on project, I was passing yearly final exams in my university. By the end of the week I have passed all my exams with excellence (which means that I&rsquo;ll keep my scholarship) and with peace of mind started working on my GSoC project.As I mentioned in previous post I have found some Issues in ROS USB stack driver&rsquo;s uninstall/unload flows, and started debugging.</description> </item> <item> <title>Google SoC lwIP Report Week 3</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-3/</link> <pubDate>Sun, 12 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-3/</guid> <description>In week 3, I discovered a lot more about how data is being passed around.After more in depth inspection of the memory, I realized that Winsock was passing on the correct IP address; I just wasn't aware of the data structure it was using. After modifying my driver to correctly extract the IP address from the IRP, my test server and client performed a successful TCP connection hand shake, with my client program exiting correctly.</description> </item> <item> <title>SATA AHCI Driver GSoC - Week 2 Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-2-update/</link> <pubDate>Tue, 07 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-2-update/</guid> <description>In the first week I gained enough knowledge to kick start the coding part. I started implementation with minimal featured design idea i.e. started implementation of non-optional routines first and in order they are being called by Storport/OS. Listed below DriverEntry: Registered the driver with very standard configurations (that I learned by WDK samples) and with non-optional (required entrypoint for Storport) Hw Routines. Standard configuration includes NeedPhysicalAddresses (TRUE)</description> </item> <item> <title>NTFS Write Support GSoC - Week 2</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-2/</link> <pubDate>Mon, 06 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-2/</guid> <description>This week I spent a few days hammering out all the problems I was having with MSVC builds, understanding exactly what was causing them, and updating configure.cmd so nobody else would have them in the future. See my forum post for the details. I've also been doing a lot of reading this week, both on the peculiarities of NTFS, and on Windows file system drivers. File System Forensic Analysis by Brain Carrier has been an incredible resource for the former, and Windows Nt File System Internals by Rajeev Nagar has been indispensable for the latter.</description> </item> <item> <title>USB 1.1 UHCI improvements GSoC - Week 2</title> <link>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-2/</link> <pubDate>Mon, 06 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-2/</guid> <description>The second week of coding period I spend on testing and debugging.As you may remember from previous post, there were all fails in UHCI test spreadsheet. This week I&#39;ve done same tests with all ROS&#39;s usb stack injected along with &quot;usbuhci.sys&quot; but this also not helped. So we can assume that UHCI is not working under 2k3. Also I&#39;ve found bug (crash) in UHCI driver uninstall flow. In case of EHCI, it is normally denying removal, but in case of UHCI I&#39;m seeing system crash coming from &quot;hub.</description> </item> <item> <title>Google SoC lwIP Report Week 2</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-2/</link> <pubDate>Fri, 03 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-2/</guid> <description>In my second week of working on this project, I have made some progress in linking the Winsock listen() and connect() calls to their lwIP implementations. As with last week, Art Yerkes has been a great souce of information whenever I get stuck on anything.&nbsp;I spent the first part of the week figuring out how to extract the information I need from the IRP my driver receives in order to pass it along to lwIP.</description> </item> <item> <title>SATA AHCI Driver GSoC - Week 1 Update</title> <link>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-1-update/</link> <pubDate>Thu, 02 Jun 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/sata-ahci-driver-gsoc-week-1-update/</guid> <description>To be honest I started working on project after my college finals i.e. 27th of May, Before that I tried to setup build environment and test bed in virtual machine running win2k3. I was totally new to NT driver development so I started my journey with reading storage stack model and NT driver development guide.In the first week I explored storage stack of NT 5.2 completely and presented my work plan to my mentor.</description> </item> <item> <title>USB 1.1 UHCI improvements GSoC - Week 1</title> <link>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-1/</link> <pubDate>Mon, 30 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/usb-11-uhci-improvements-gsoc-week-1/</guid> <description>Hi! My name is Vardan and during this GSoC I&#39;ll work on UHCI driver improvements.&nbsp;&nbsp;Why ROS?Now, when human is becoming more and more dependent on computer it becoming critical to have open-source OS on it. You can feel really secured only when you&lsquo;re able (allowed) to see any part of OS which can control all your data. For the student who is studying computer science, the best choice was Linux (especially when classroom computers working only under it).</description> </item> <item> <title>NTFS Write Support GSoC - Week 1 Update</title> <link>https://reactos.org/blogs/ntfs-write-support-gsoc-week-1-update/</link> <pubDate>Sun, 29 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntfs-write-support-gsoc-week-1-update/</guid> <description>Hi there! My name is Trevor Thompson and I'm working on NTFS write support for Google Summer of Code 2016. Status Update: I now know the basics of windbg. I'm surprised at how powerful this tool is! A few weeks ago, Pierre asked if I could take a look at largemcb.c and help him fix the bugs that were causing kmtest to fail the FsRtlMcb test. I didn't have a chance to look at it until now, but I felt like this would be a perfect opportunity to get some practice with windbg and get started with serious React OS development.</description> </item> <item> <title>Google SoC lwIP Report Week 1</title> <link>https://reactos.org/blogs/google-soc-lwip-report-week-1/</link> <pubDate>Fri, 27 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/google-soc-lwip-report-week-1/</guid> <description>Note: I am publishing these but each student is responsible for actually writing them.I am Zuodian Hu or, as I like to be called, Dian (pronounced the same as Dan). I just finished my junior year at the University of Wisconsin at Madison, where I am working on an electrical engineering and computer science double major. My personal interest lies in systems programming and digital logic. In addition to my classes, I play violin in the UW-Madison symphony orchestra and do programming for Wisconsin Robotics and the UW-Madison team competing in the NASA Robotics Mining Competition.</description> </item> <item> <title>ReactOS 0.4.1 Released</title> <link>https://reactos.org/project-news/reactos-041-released/</link> <pubDate>Tue, 17 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-041-released/</guid> <description>The ReactOS team is proud to announce the release of version 0.4.1 a mere three months after the release of 0.4.0. The team has long desired an increased release tempo and the hope is that this will be the first of many of faster iterations.Due to the brief period of time between the two releases, 0.4.1 is ultimately a refinement of what was in 0.4.0. That is not to say that there are no new features of course, and a few highlights of both categories are listed below.</description> </item> <item> <title>April 2016 meeting minutes</title> <link>https://reactos.org/project-news/april-2016-meeting-minutes/</link> <pubDate>Mon, 02 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/april-2016-meeting-minutes/</guid> <description>2016-04-2820:00 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 20:00 by Amine Khaldi Point 1: Status Reports Point 2: 0.4.1 Release plans Point 3: GSoC Point 1: Status Reports Aleksey Bragin: He did not have time to code, however he was putting some time into the infrastructure, which is working quite niceAmine Khaldi: He's been trying to catch a breath and recharge a bit, but he still worked on his usual tasks (jira, patches, handling newcomers, and especially our GSoC students, some commits like the SDK structure, the libpng sync and so on.</description> </item> <item> <title>March 2016 meeting minutes</title> <link>https://reactos.org/project-news/march-2016-meeting-minutes/</link> <pubDate>Mon, 02 May 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/march-2016-meeting-minutes/</guid> <description>2016-03-3120:00 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 20:00 by Aleksey Bragin Point 1: Status Reports Point 2: 0.4.1 Release plans Point 3: GSoC Point 1: Status Reports [TheFlash]: He's still busy with class projects (pursuing a master's degree) so he hasn't gotten around to working on ReactOS much. He did fix that NTVDM bug though. Once he's done with these projects he can start working on NTVDM VESA support.</description> </item> <item> <title>CLT 2016 - A short summary</title> <link>https://reactos.org/project-news/clt-2016-short-summary/</link> <pubDate>Sun, 27 Mar 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/clt-2016-short-summary/</guid> <description>Hello guys,After some days went past I will now sum up the main events of the CLT 2016 for you.The event took place from 19th - 20th March at Technische Universität of Chemnitz. This year the team was smaller than the years before and only Thomas Faber and me (for ppl that don't know me: Daniel Reimer) have made it. The hotel we booked was the Hoteloper Chemnitz.</description> </item> <item> <title>February 2016 meeting minutes</title> <link>https://reactos.org/project-news/february-2016-meeting-minutes/</link> <pubDate>Sun, 27 Mar 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/february-2016-meeting-minutes/</guid> <description>2015-11-2619:30 UTCirc.freenode.net, #reactos-meetingProceedings Meeting started at 19:33 by Aleksey Bragin Point 1: Status Reports Point 2: Website Reports Point 3: 0.4.1 and 0.5.0 Release plans Point 1: Status Reports [TheFlash]: He'll work on the ntvdm bugs he took over in jira and after that he'll help with rapps_new. He's pretty much given up on writing NTVDM sound card drivers for now due to licensing problems he can't bypass and/or combine with his ideals.</description> </item> <item> <title>ReactOS Participation in Google Summer of Code 2016</title> <link>https://reactos.org/project-news/reactos-participation-google-summer-code-2016/</link> <pubDate>Mon, 29 Feb 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-participation-google-summer-code-2016/</guid> <description>After five years the ReactOS Project is returning to the Google Summer of Code. On the heels of the 0.4.0 release the project's aim is on creating smoother user experiences and generally making the system feel more robust and pleasant to use. The team is looking for students interested in learning more about the NT architecture that underpins the most widely used desktop operating system in the world and who wants to take part in the creation of an open source implementation of it.</description> </item> <item> <title>ReactOS 0.4.0 Released</title> <link>https://reactos.org/project-news/reactos-040-released/</link> <pubDate>Tue, 16 Feb 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-040-released/</guid> <description>Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0. A great deal of work has gone into making this release happen and as we look back it is remarkable to consider how far the project has come since that release a decade ago. This release is both a celebration of and a testament to everything that the ReactOS team and community has achieved together.</description> </item> <item> <title>Discover the new ReactOS website</title> <link>https://reactos.org/project-news/discover-new-reactos-website2/</link> <pubDate>Mon, 08 Feb 2016 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/discover-new-reactos-website2/</guid> <description>As you may have noticed, the ReactOS website has been completely revamped. During the last year, the ReactOS Team has been focusing on entering the 0.4 era, the latest major alpha series before the 0.5 Beta. A common feeling among the ReactOS community was that our (now old) website was not good enough from content, design, and technology points of view to honor one of the greatest releases in the ReactOS history.</description> </item> <item> <title>Unexpected bug cascade - or how seemingly missing bugs in MSVC builds reveal actual bugs</title> <link>https://reactos.org/blogs/unexpected-bug-cascade-or-how-seemingly-missing-bugs-msvc-builds-reveal-actual-bugs/</link> <pubDate>Sun, 27 Dec 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/unexpected-bug-cascade-or-how-seemingly-missing-bugs-msvc-builds-reveal-actual-bugs/</guid> <description>I was looking into CORE-9105, a crash in wget.exe, but I couldn't reproducde it, so I asked Daniel whether he was using an MSVC build or a GCC build. He used a GCC build and I was using an MSVC build. So I tried with a GCC build and the bug appeared. So I looked at this thing with kdbg. And there the first bug showed up.Bug #1: KDBG and break points I set a breakpoint at a position that I wanted to step through and KDBG stopped there.</description> </item> <item> <title>A Very Bunny Christmas</title> <link>https://reactos.org/blogs/very-bunny-christmas/</link> <pubDate>Mon, 21 Dec 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/very-bunny-christmas/</guid> <description>See here for explanation of the Bunnies.When Z logged onto the ROS virtual net he was met with two unexpected things.&nbsp; Seeing as one involved an AI hivemind that the team still did not fully understand he decided to satisfy his curiosity with the other surprise.“Colin.”The German man glanced up.&nbsp; “Oh, hey Z.&nbsp; Wasn’t expecting you in today.”“Likewise,” Z said with a slight smirk.&nbsp; “Don’t you Europeans check out for the entire week before Christmas?</description> </item> <item> <title>November 2015 meeting minutes</title> <link>https://reactos.org/project-news/november-2015-meeting-minutes/</link> <pubDate>Sat, 19 Dec 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/november-2015-meeting-minutes/</guid> <description>2015-11-2619:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:18 by Aleksey Bragin Point 1: Status Reports Point 2: 0.4.0 Release plans Point 1: Status Reports [TheFlash]: He started working on the NTVDM Sound Blaster emulation, however he realized that he's completely unable to test anything sound-related on ReactOS. KVM doesn't support the only card we have (CMI8378) and the rest would require non-free drivers, the use of which he finds contradictory to his ideals.</description> </item> <item> <title>Introduction to NDIS Driver Development</title> <link>https://reactos.org/blogs/introduction-ndis-driver-development/</link> <pubDate>Thu, 17 Dec 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/introduction-ndis-driver-development/</guid> <description>Drivers come in many forms as does the hardware they control.&nbsp; Perhaps one of the simplest types of drivers to write for the NT kernel is an NDIS driver for network cards, simplest being in the context of kernel development.&nbsp; That simplicity comes from how the framework used for NIC drivers abstracts away some of the manual setup needed for drivers, eliminating a lot of boilerplate code and making it easier to get a handle on the actual hardware operations being performed.</description> </item> <item> <title>October 2015 meeting minutes</title> <link>https://reactos.org/project-news/october-2015-meeting-minutes/</link> <pubDate>Sun, 15 Nov 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/october-2015-meeting-minutes/</guid> <description>2015-10-2919:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:01 by Amine Khaldi Point 1: Release plans Point 2: Special Report: Shell Point 3: Special Report: CE plans Point 4: Developers reports Point 1 Amine Khaldi built up on an email he sent to ros-priv about planning a 0.4.0 release now that things start to get in shape for it. He started the topic with asking for opinions and questions regarding what's still left to do.</description> </item> <item> <title>September 2015 meeting minutes</title> <link>https://reactos.org/project-news/september-2015-meeting-minutes/</link> <pubDate>Sun, 18 Oct 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/september-2015-meeting-minutes/</guid> <description>2015-09-2419:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:01 by Aleksey Bragin Point 1: Status Reports Point 2: Website upgrade proposal (Aleksey and Victor) Point 3: MSPL licensed code in our repo Point 4: Switching to new build process (Amine and Daniel) Point 5: Oldest CPU arch supported by ReactOS Point 1 Aleksandar Andrejevic: He is currently working on NTVDM. Soon, he'll finish translating a FreeBasic-based GPL Sound Blaster emulator (written by Mysoft, aka Gregory Macario Harbs) to C and include it.</description> </item> <item> <title>June 2015 meeting minutes</title> <link>https://reactos.org/project-news/june-2015-meeting-minutes/</link> <pubDate>Thu, 17 Sep 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/june-2015-meeting-minutes/</guid> <description>2015-06-2519:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:08 by Aleksey Bragin Point 1: Status Reports Point 2: Hackfest Point 1 Aleksey Bragin: His work on LDR code starts to have good results and a first patch was attached to a JIRA ticket. One crash was experienced in the tests, but it's not sure that it's caused by the patch at all. All which still has to be done is some reviewing by others and some clean up.</description> </item> <item> <title>May 2015 meeting minutes</title> <link>https://reactos.org/project-news/may-2015-meeting-minutes/</link> <pubDate>Thu, 17 Sep 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/may-2015-meeting-minutes/</guid> <description>2015-05-2819:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:17 by Aleksey Bragin Point 1: Report on the BRICS Operating System project proposal Point 2: Request to feature our official Dell laptop in a video Point 3: New Website Point 4: Plans for 0.4.0 Point 1 Aleksey Bragin officially submitted two project proposals to the Russian IT ministry (which is in charge of the BRICS operating systems development).</description> </item> <item> <title>ReactOS Hackfest in Aachen</title> <link>https://reactos.org/project-news/reactos-hackfest-aachen/</link> <pubDate>Tue, 01 Sep 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-hackfest-aachen/</guid> <description>Day -1 (5th of August) As Aleksey arrived well before the hackfest started, Colin was kind enough to show the city in its full glory on a very hot day: the cathedral, springs, restaurants and cafes, and definitely the RWTH university buildings spread across the city. The most relevant was the temporary seminar building where a large room was dedicated for the Hackfest. It turned out to be a clean and modern equipped building which is indeed temporary and will be demolished once the real building is finished, so ReactOS is not the only one to utilize temporary hacks until full implementation is done :).</description> </item> <item> <title>ReactOS printing for the first time!</title> <link>https://reactos.org/blogs/reactos-printing-first-time/</link> <pubDate>Sat, 25 Jul 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/reactos-printing-first-time/</guid> <description>As some of you may already know, my university gave me the unique opportunity to choose a ReactOS topic for my bachelor thesis. Three months ago, my decision fell on the Printing Stack, which was totally non-existing in ReactOS at that time. Since then, you can watch my daily progress in the colins-printing-for-freedom branch.The Printing Stack as found in modern Windows&reg; versions is a beast of its own. Microsoft&reg; never wanted to sacrifice backwards compatibility with each new Windows version, so the widely used higher level GDI Printing APIs (like StartDoc or EndDoc found in gdi32.</description> </item> <item> <title>The First Ever ReactOS Hackfest!</title> <link>https://reactos.org/blogs/first-ever-reactos-hackfest/</link> <pubDate>Sat, 20 Jun 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/first-ever-reactos-hackfest/</guid> <description>Join us for the very first ReactOS Hackfest from Friday, 7th August to Wednesday, 12th August 2015, in the German city of Aachen. Discover Germany's most-Western city in the direct neighborhood of Belgium and the Netherlands. Within the historical city center, Aachen offers a scientific environment and a high density of pubs. Let's catch this atmosphere to code the week away and achieve great results as a team! It is now time to plan your trip!</description> </item> <item> <title>ReactOS as a second OS in Russian government's software freedom effort</title> <link>https://reactos.org/project-news/reactos-second-os-russian-governments-software-freedom-effort/</link> <pubDate>Fri, 19 Jun 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-second-os-russian-governments-software-freedom-effort/</guid> <description>The Russian Federation along with the BRICS nations are pursuing measures to rid vendor lock-in of strategically important software (http://minsvyaz.ru/en/events/33237/) and substitute such software with free/open software (http://minsvyaz.ru/en/events/32967/). As such an initiative would provide considerable benefits beyond that of any singular agenda, Aleksey Bragin decided to take part in that on behalf of ReactOS Foundation. Since October 2014 he has been a member of the Operating Systems workgroup formed by the Ministry of Telecom and Mass Communications (so-called "</description> </item> <item> <title>ReactOS gets a Youtube Channel</title> <link>https://reactos.org/project-news/reactos-gets-youtube-channel/</link> <pubDate>Thu, 18 Jun 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-gets-youtube-channel/</guid> <description>ReactOS is proud to announce the ReactOS Community&nbsp;YouTube&nbsp;Channel!Its main goal is to share all of the videos of ReactOS in one main spot. This way, the entire ReactOS community, and the whole world, will be able to see the progress of ReactOS and what it can do. We hope for this channel to become a central place for all the community's contributions in terms of videos.The ReactOS Community YouTube Channel can also be used as PR to the world.</description> </item> <item> <title>Rounding and integer math</title> <link>https://reactos.org/blogs/rounding-and-integer-math/</link> <pubDate>Sat, 16 May 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/rounding-and-integer-math/</guid> <description>It sometimes happens that in your program you need to divide integer values and then round the result.Something like&nbsp;&nbsp;&nbsp; int result = lrint((double)int_a / (double)int_b);But sometimes it is desirable to not use floating point math at all. The question is: Can we do the same calculation with integer math and get exactly the same result?Let&#39;s simplify our case, by limiting to unsigned values (for signed values it is very similar, only the formulas get a bit more complex).</description> </item> <item> <title>April 2015 Meeting Minutes</title> <link>https://reactos.org/project-news/april-2015-meeting-minutes/</link> <pubDate>Sun, 03 May 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/april-2015-meeting-minutes/</guid> <description>2015-04-3019:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:09 by Aleksey Bragin Point 1: Developer Briefings Point 2: ReactOS Hackfest 2015 Point 1 Aleksandar Andrejevic: During the last month, Aleksandar has been fixing bugs in various parts of NTVDM, and is planning on fixing more bugs in the near future.Amine Khaldi: Amine was continuing the wine sync effort, while assisting and guiding some new comers that showed up recently, to make sure they contribute to the most urgent needs.</description> </item> <item> <title>ReactOS Shop Grows!!</title> <link>https://reactos.org/blogs/reactos-shop-grows/</link> <pubDate>Thu, 23 Apr 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/reactos-shop-grows/</guid> <description>One of the most important ways to maintain our ReactOS development is through Donations, another way is through helping us reach out to new and cool developers by sharing these news! We're proud to share that our Shop is not just including the USB stick, but also.. 6 new and crazy pieces! A must have: An awesome ReactOS mug for your breakfast or evening coffee which can't look better. Do you see how that black background makes ReactOS orb shine?</description> </item> <item> <title>How do security issues happen?</title> <link>https://reactos.org/blogs/how-do-security-issues-happen/</link> <pubDate>Wed, 11 Feb 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/how-do-security-issues-happen/</guid> <description>If you are a Windows user, you may be used to seeing a bunch of updates pop up around the second Tuesday of every month that purport to fix "critical security issues." Microsoft's continuous effort to fix these vulnerabilities in its operating system consumes a lot of resources, but it is well worth it to the users: in a world of ever-increasing cyber security threats, no hole in our computers' defenses should be left open to potential attackers.</description> </item> <item> <title>Post-vacational resolutions (A.K.A. Present and future of my ReactOS contract)</title> <link>https://reactos.org/blogs/post-vacational-resolutions/</link> <pubDate>Mon, 26 Jan 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/post-vacational-resolutions/</guid> <description>Hello everyone!You will have noticed the long delay since my last report, and may be wondering what has happened. I will try to explain.The last report was published on the 24th, right before christmas eve, when my vacation started. I took my vacation so that I could rest, clear my head, and regain energy so that I could resume my work in January at full speed. Over the christmas days, I had time for resting, games, hobbies, and family, and this gave me a lot of time to think.</description> </item> <item> <title>Security issue on the ReactOS infrastructure</title> <link>https://reactos.org/project-news/security-issue-reactos-infrastructure-2015/</link> <pubDate>Wed, 21 Jan 2015 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/security-issue-reactos-infrastructure-2015/</guid> <description>Dear all, On the 20th of January, we discovered a vulnerability affecting our infrastructure. This vulnerability has been immediately fixed after its discovery. Unfortunately, it was a vulnerability present for years on the infrastructure. This vulnerability was affecting our main users database. This means that our complete user database may have leaked, including user name, password (hashed) and email address. We do not have any evidence that the database actually leaked.</description> </item> <item> <title>Decorating the shell tree</title> <link>https://reactos.org/blogs/decorating-shell-tree/</link> <pubDate>Wed, 24 Dec 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/decorating-shell-tree/</guid> <description>Hello everyone,Because Christmas was so close to the weekend, I decided to delay the report a few days, and release it on time for the holidays, and this way include in the report everything that has happened over the weekend and the beginning of this week.The past week began by reviewing some patches that were pending for a LONG time. Sadly, most of them were too bit-rotten to be applicable as-is, so I had to contact the patches’ authors and request an update.</description> </item> <item> <title>On Patches</title> <link>https://reactos.org/blogs/on-patches/</link> <pubDate>Mon, 15 Dec 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/on-patches/</guid> <description>Before I begin, I should make clear that for all intents and purposes I am not a "developer" on the project. I have actually tried very hard to avoid falling into that role, as most people who do become developers end up getting sucked into that work to the point where of the time they do dedicate to the project, they tend to not have any left over to do other work that the project needs.</description> </item> <item> <title>Unclean cleanups</title> <link>https://reactos.org/blogs/unclean-cleanups/</link> <pubDate>Sat, 13 Dec 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/unclean-cleanups/</guid> <description>Hello, everyone!I think the best way to explain how this week started is by recreating a conversation that happened on IRC (shortened and cleaned so that it looks more serious and professional then the typical IRC conversation):gadamopoulos: Oh gigaherz, we have bugs due to the conversion to c++. Pretty obvious ones. CTaskBand is a mess: punkSite is ambigouous, as member and parameter.gigaherz: I tried to find all of those, did I miss some?</description> </item> <item> <title>Funny title not found</title> <link>https://reactos.org/blogs/funny-title-not-found/</link> <pubDate>Sun, 07 Dec 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/funny-title-not-found/</guid> <description>Hello everyone,If you remember from last week, my top priority was to investigate the crash when pasting files, but because Giannis insisted a bit that I should fix the merged folders usage so that the windows classes can be used instead of our own, I went back to the merged folders, and started looking at why the windows classes didn’t work. The first thing I had to fix was a misunderstanding of the return value of the filtering callback, which returns S_FALSE if the item is shown, and S_OK if the item has to be filtered away.</description> </item> <item> <title>Dislocated localizations</title> <link>https://reactos.org/blogs/dislocated-localizations/</link> <pubDate>Mon, 01 Dec 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/dislocated-localizations/</guid> <description>Hello and sorry for yet another delay!As you will most probably know (and if you don’t, you should take a look at the news on the front page!), the shell branch was merged last Wednesday evening, as a thanksgiving gift from the project to all the contributors. As things happen when a big merge is done and people with varied configurations start testing, it wasn’t 5 minutes that the first big “oh shit” bug report came in.</description> </item> <item> <title>Explorer Shell Merged</title> <link>https://reactos.org/project-news/explorer-shell-merged/</link> <pubDate>Wed, 26 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/explorer-shell-merged/</guid> <description>To all the community members, we of the ReactOS Project present an early Thanksgiving present in the form of the merging of the explorer_new branch into trunk. It has been a long road with explorer_new's development having stretched many years. It is only fitting that we also celebrate the people who contributed so much to bringing this to fruition, some of whom we pay specific thanks to below.The first such person actually never touched explorer_new, but his contribution should not be overlooked.</description> </item> <item> <title>Patching Patches and Testing Tests</title> <link>https://reactos.org/blogs/patching-patches-testing-tests/</link> <pubDate>Mon, 24 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/patching-patches-testing-tests/</guid> <description>Hello and sorry for the delay.This past week has been rather strange. My goal was to add some quick tests to ensure that my implementation was matching Windows’ behaviour, and then send the changes to WINE. But as I was adding more details to test, I was finding more mismatches between Windows and ReactOS (well, WINE code). Annoyingly, most of the mismatches are in the code not related to my changes, and on top of that, a few of the returned values had unexpected content.</description> </item> <item> <title>Network development branch</title> <link>https://reactos.org/blogs/network-development-branch/</link> <pubDate>Mon, 17 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/network-development-branch/</guid> <description>People following the SVN logs may have noticed Jerome Gardou creating a network rework branch and ripping out massive chunks of the current code. To explain what prompted this requires a bit of history and background. Many years ago Cameron Gutman imported the lightweight IP (lwIP) library so that ReactOS could take advantage of its TCP implementation for the network stack. It was only used for TCP however, meaning ReactOS was still relying on its existing implementation for things like UDP and ICMP.</description> </item> <item> <title>Translatable emptyness and Long-winded Shortcuts</title> <link>https://reactos.org/blogs/translatable-emptyness-long-winded-shortcuts/</link> <pubDate>Sat, 15 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/translatable-emptyness-long-winded-shortcuts/</guid> <description>Hello and welcome back to my weekly report.As I said in the last report, I ended the week trying to fix the start menu closing on a second click. The realization that Windows doesn’t close the shell menus on mouse up, allowed me to simplify some of the logic, but the issue still resisted my attempts.After some very long hours trying to figure out where the code went wrong, I realized the order of the events was actually wrong.</description> </item> <item> <title>Post-Incrementing the C</title> <link>https://reactos.org/blogs/post-incrementing-c/</link> <pubDate>Mon, 10 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/post-incrementing-c/</guid> <description>Hello again, people.Wow so another week has passed, and the whole weekend too. I feel a bit like I was sucked into a temporal distortion, because I can’t really tell where all these hours have gone. Heck, I almost forgot to write the report! Thankfully, the cold I spoke about last week, it didn’t complicate itself, so I have been able to work over the week.I suppose many of you didn’t wait for the surprise and looked at the commit logs, or read the comment thread for the “spoilers”.</description> </item> <item> <title>ReactOS 0.3.17 Released</title> <link>https://reactos.org/project-news/reactos-0317-released/</link> <pubDate>Wed, 05 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0317-released/</guid> <description>The ReactOS Project is pleased to release version 0.3.17. A major new feature for this release is the inclusion of NTVDM, which provides support for a wide range of 16bit applications, a long requested feature by the community. NTVDM is still undergoing work but we felt that it was ready enough to provide a sneak peak to the wider community. In addition, the leadup to the 0.3.17 release saw a very impressive round of testing by the community.</description> </item> <item> <title>October 2014 Meeting Minutes</title> <link>https://reactos.org/project-news/october-2014-meeting-minutes/</link> <pubDate>Tue, 04 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/october-2014-meeting-minutes/</guid> <description>2014-10-3019:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:05 by Aleksey Bragin. Point 1: Developer Briefings Point 2: 0.3.17 Point 3: 0.4.0 and Future Releases Point 1 Amine Khaldi has been working on wine syncs and shell bringup testing. Christoph von Wittich has been making minor fixes as he finds time. David Quintana has been resolving the last of the serious memory leaks and considers the branch close to ready for merging back into trunk.</description> </item> <item> <title>Two Steps from [the S]hell</title> <link>https://reactos.org/blogs/two-steps-from-shell/</link> <pubDate>Mon, 03 Nov 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/two-steps-from-shell/</guid> <description>Hello everyone, and sorry for the delay.I caught a bad cold (that may or may not be complicated with a throat infection -- we'll see) so I was lacking the necessary concentration to write this report earlier.As Z98 said last weekend, it has been some very busy days for all the team. I want to reiterate all the appreciation for the help given by everyone. There is just so much debugging I can do without my head exploding, and finding leaks tends to cross that line.</description> </item> <item> <title>Plugging Leaks</title> <link>https://reactos.org/blogs/plugging-leaks/</link> <pubDate>Mon, 27 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/plugging-leaks/</guid> <description>David is currently a tad busy getting the shell branch ready for the big merge, so I am taking over his usual report this time. Last week was a flurry of activity as David, Giannis, and a community member who wishes to be identified as "V" (those of you in IRC will know who he is, but he requested that we refrain from posting his nick and I expect the rest of the community to honor his request) investigated the large number of memory leaks that explorer_new suffered from.</description> </item> <item> <title>Developer Contract for Jerome Gardou</title> <link>https://reactos.org/project-news/developer-contract-jerome-gardou/</link> <pubDate>Mon, 20 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/developer-contract-jerome-gardou/</guid> <description>This is somewhat belated, but for the past month Jérôme Gardou has been working under a development grant issued by ReactOS Deutschland e.V. Jerome has been active working on the memory manager and his fixes were instrumental to getting a modern Java runtime to work. Other efforts with the Common Cache will help pave the way for adding support for more advanced and modern filesystems to ReactOS. Jerome's contract saw him pay special attention to the three applications, Chrome, Java, and Microsoft Office, voted on for support in the Community Edition, and several fixes were made to the network stack as he sought to stabilize Chrome.</description> </item> <item> <title>MIAOW Open Source GPU</title> <link>https://reactos.org/blogs/miaow-open-source-gpu/</link> <pubDate>Mon, 20 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/miaow-open-source-gpu/</guid> <description>About a year ago I basically disappeared from the project, showing up only very intermittently to write up snippets of text as requested by the team. The reason was I was ramping up for my master's project, an attempt to put a GPU design on an FPGA. For those of you who do not know what FPGAs are, think of them as chips that you can modify the digital logic on to change its functionality.</description> </item> <item> <title>Circular leaks</title> <link>https://reactos.org/blogs/circular-leaks/</link> <pubDate>Sun, 19 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/circular-leaks/</guid> <description>Hello again!As I mentioned in the last report, I had been writing tests to find the problems in SHFileOperation. All I knew was that in some situations it would end without fully writing some file, so I wrote tests moving, copying and deleting a folder structure, and comparing the copy with the original. I tried with empty files first, then with files of random sizes, then with really big files, and also with a lot of files of relatively small size.</description> </item> <item> <title>PITA bugs part 5</title> <link>https://reactos.org/blogs/pita-bugs-part-5/</link> <pubDate>Thu, 16 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pita-bugs-part-5/</guid> <description>I mentioned in my last rant about annoying bugs that I do firmware development for the LHC triggers. In addition to that however, as one of the people with experience doing low level embedded programming on the team, I can get tapped to work on a variety of other systems. Recently I was asked to update an old AVR microcontroller codebase that was written for a proprietary toolchain to use AVR-GCC.</description> </item> <item> <title>View Popups and Unreliable Operations</title> <link>https://reactos.org/blogs/view-popups-and-unreliable-operations/</link> <pubDate>Sat, 11 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/view-popups-and-unreliable-operations/</guid> <description>Hello!It’s this time of the week again where I have to sit down and try to remember everything I have been doing over the week.I began the week by looking at some older pending bugs. First, I looked at an issue where using the branch with the vmware audio driver installed would crash stobject.dll and because it’s loaded into explorer-new, the rest of the desktop and taskbar. I couldn’t reproduce this issue, so I moved on.</description> </item> <item> <title>Inter-process miscommunication</title> <link>https://reactos.org/blogs/inter-process-miscommunication/</link> <pubDate>Fri, 03 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/inter-process-miscommunication/</guid> <description>Hello again!This week has been strange. It has mostly been a series of disappointments, but it ended in some really good news.I started this week by implementing the parser for the shell DDE commands. The syntax is simple, so the parser itself didn’t take long to finish. I tested it and debugged it in Windows at first, and when I was satisfied that the code was working the way I wanted it, I moved the functions into their rightful place inside shell32, and proceeded to test the function in ReactOS.</description> </item> <item> <title>ReactOS Joins Open Invention Network</title> <link>https://reactos.org/project-news/reactos-joins-open-invention-network/</link> <pubDate>Fri, 03 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-joins-open-invention-network/</guid> <description>The ReactOS Foundation officially joins the Open Invention Network! The Open Invention Network is a shared defensive patent pool with the mission to protect Linux. Launched in 2005, OIN has strong industry support with backing from Google, IBM, NEC, Philips, Red Hat, Sony and SUSE (a business unit of Novell). ReactOS is just a small piece in this big opensource world and even if we're not a Linux project, helping to protect the opensource spirit is, and will always be, a must for us.</description> </item> <item> <title>Moonshot Finale</title> <link>https://reactos.org/blogs/moonshot-finale/</link> <pubDate>Wed, 01 Oct 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/moonshot-finale/</guid> <description>The virtual conference room was deathly quiet as Colin and Z finished their report.&nbsp; The gathered represented the core of the project’s decision makers as well as a few of the relevant developers and alumni.&nbsp; All of them were gapping in some fashion or another at the two men standing before them.&nbsp; The first one to verbally react was KJK, who burst out laughing.&nbsp; The others looked somewhat incredulously at him until he managed to recompose himself.</description> </item> <item> <title>September 2014 Meeting Minutes</title> <link>https://reactos.org/project-news/september-2014-meeting-minutes/</link> <pubDate>Tue, 30 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/september-2014-meeting-minutes/</guid> <description>2014-09-2519:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:00 by Ziliang Guo. Point 1: Developer Briefings Point 2: Jira Point 3: Website Point 1 Aleksey Bragin had been ill for a bit, which was also why the previous meeting was canceled. Alexander Rechitskiy has been working to promote ReactOS to various organizations. Daniel Reimer has been testing a variety of games and multimedia applications, trying to restore sound that was broken due to a Wine sync of DSound not playing nicely with ReactOS' sound stack.</description> </item> <item> <title>Locked at Sharing</title> <link>https://reactos.org/blogs/locked-at-sharing/</link> <pubDate>Sun, 28 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/locked-at-sharing/</guid> <description>Hello again!You may remember from last week I said I would need more information in order to implement the mechanism browseui uses to open new windows in an existing process.Well, spoiler alert if you haven’t read the SVN log: I got the information, and I wrote an implementation.First of all, it turns out message 1037 is related to the rooted idlists. Since rooting is completely unimplemented at all the levels down to the implementation of the idlists, I stopped trying to figure out that message, and instead focused on the important one, 1035.</description> </item> <item> <title>Moonshot Part 3</title> <link>https://reactos.org/blogs/moonshot-part-3/</link> <pubDate>Tue, 23 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/moonshot-part-3/</guid> <description>The answer to the mystery about the bunnies’ extracurricular activities came soon enough, in no small part thanks to the amount of time the two spent investigating.&nbsp; The bunnies were extremely useful helper utilities and if they were suffering from a bug, it needed fixing otherwise the project would risk losing one of its more useful tools.&nbsp; By the end of these events the bunnies would be considered one of the core assets underpinning the entire project.</description> </item> <item> <title>Shared memory messages</title> <link>https://reactos.org/blogs/shared-memory-messages/</link> <pubDate>Sun, 21 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/shared-memory-messages/</guid> <description>Hello!Another weekend, another report.The week was slightly shorter for me due to having the project defense on Tuesday, so I spent most of Monday preparing for the presentation, and most of Tuesday afternoon recovering from it. If you are curious, I got a 9.5/10 on the project. ;PIn the context of the shell, this week I mostly continued my investigations on the IPC mechanism used by browseui to open new windows in the existing process.</description> </item> <item> <title>Lines of commands</title> <link>https://reactos.org/blogs/lines-of-commands/</link> <pubDate>Fri, 12 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/lines-of-commands/</guid> <description>Hello again!When I said last week’s report would be short, I was still planning to write a few lines about what I had been doing on the spare time from the university project, but by the time the weekend came I was way too mentally exhausted to actually do it. Then I started refreshing my mind with what I was in the middle of doing, and by Sunday night I had the explorer command line parser working more or less as intended (it still has a few places where it doesn’t behave exactly like Windows’ parser, but it’s close enough for what we need).</description> </item> <item> <title>Memory Manager Development</title> <link>https://reactos.org/blogs/memory-manager-development/</link> <pubDate>Tue, 09 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/memory-manager-development/</guid> <description>The legacy memory manager in ReactOS has many idiosyncrasies and architectural quirks, issues that have dogged the project for many years now. The ARM team began a rewrite, colorfully named Another Rewrite of the Memory Management Module (ARM3), that partially supplanted the old memory manager but a big chunk of responsibility still lie with it, namely in the form of MEMORY_AREA. Simply put, MEMORY_AREA was the means by which memory address ranges were tracked, tracking which is necessary for things like handling paging.</description> </item> <item> <title>Moonshot Part 2</title> <link>https://reactos.org/blogs/moonshot-part-2/</link> <pubDate>Tue, 02 Sep 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/moonshot-part-2/</guid> <description>The incident that ultimately aroused the suspicion of the project technically occurred first but the analysis was concluded afterwards so it was generally treated as the second checkpoint in the road to the revelation.&nbsp; The initial reaction hovered between heavy uncertainty and cautious concern, a concern that only grew over time. The briefing with the various governmental representatives came and went and was as excruciatingly pointless and braindead as Z had presumed.</description> </item> <item> <title>Parsing the commands</title> <link>https://reactos.org/blogs/parsing-the-commands/</link> <pubDate>Sat, 30 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/parsing-the-commands/</guid> <description>Hello, Everyone!I mentioned last week, that I had started looking at the DDE server support, and it would take a while.What I forgot to mention, is that the deadline for handing over my final project at university is next Friday, and the defense for the project a couple weeks after that. Ideally, if me &amp; the other guys working on the project had done everything on schedule, we’d just be finishing off the documentation and we’d be almost ready, but as projects go, it’s always when the deadline looms close that you remember everything you were supposed to have been doing.</description> </item> <item> <title>PSEH Data Corruption</title> <link>https://reactos.org/blogs/pseh-data-corruption/</link> <pubDate>Wed, 27 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pseh-data-corruption/</guid> <description>An extremely rare data corruption issue caused by the Portable Structured Exception Handling library was discovered recently, one that is rather interesting in all the factors to come into play to bring it about. PSEH was a library created by KJK::Hyperion and massively overhauled by Timo Kreuzer for its third iteration, intended to bring Structured Exception Handling to GCC. SEH is natively supported by Microsoft's compilers and underpins a lot of error handling on Windows and so was necessary for proper compatibility between ReactOS' components and Windows'.</description> </item> <item> <title>Dynamic menus and miscounted references</title> <link>https://reactos.org/blogs/dynamic-menus-miscounted-references/</link> <pubDate>Sat, 23 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/dynamic-menus-miscounted-references/</guid> <description>Hello everyone,I know I promised weekly reports but it’s summer time and, although I haven’t really been out on vacation, I have been taking my schedule a lot more loosely than usual.After fixing the stobject compilation, I set my sights on the file browser menus. I began by trying to figure out how the Windows shell manages the menus, and I realized that most of the actual work was done in the WM_INITMENUPOPUP message handler.</description> </item> <item> <title>July 2014 Meeting Minutes</title> <link>https://reactos.org/project-news/july-2014-meeting-minutes/</link> <pubDate>Fri, 22 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2014-meeting-minutes/</guid> <description>2014-07-0319:00 UTCdev.reactos.org, #meeting Proceedings Meeting started at 19:01 by Aleksey Bragin. Point 1: Developer Briefings Point 2: Community Edition Update Point 1 Aleksandar Andrejevic reported that he was unfortunately unable to make much progress with the memory manager and is reverting back to fixing issues with NTVDM. Aleksey Bragin noted that he still had some patches for ARWINSS that needed to be merged in. David Quintana reported that had implemented support for shell service objects and added a skeleton component that contains the system tray for things like volume control, battery icon, USB disconnection, and the like.</description> </item> <item> <title>Moonshot Part 1</title> <link>https://reactos.org/blogs/moonshot-part-1/</link> <pubDate>Fri, 22 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/moonshot-part-1/</guid> <description>These days when asked what a moonshot was, most people would respond with blank looks and then ask if it had something to do with the moon.&nbsp; A few more knowledgeable persons might respond that it referred to the Apollo program.&nbsp; Still others would say it referred to any project whose chances of success were low or might take a very long time to show demonstrable success.&nbsp; The Reactive Operator System fell squarely in that third category and it was with some irony that with every success it achieved its future goals became ever loftier.</description> </item> <item> <title>ReactOS at Kieler Linux Tage 2014</title> <link>https://reactos.org/project-news/reactos-kieler-linux-tage-2014/</link> <pubDate>Mon, 11 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-kieler-linux-tage-2014/</guid> <description>The ReactOS Project will be at the Kieler Linux Tage convention, running September 19th to the 20th in Kiel. Several of the developers will be present and Colin Finck will be presenting the project at a talk on the 20th at 11AM local time. So stop by if you are in the area and say hi to the developers.</description> </item> <item> <title>Contributions: UltraVNC 1.0.5</title> <link>https://reactos.org/blogs/contributions-ultravnc/</link> <pubDate>Mon, 04 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/contributions-ultravnc/</guid> <description>Thanks to Oldman, we're proud to announce that UltraVNC 1.0.5 is now running in ReactOS.UltraVNC is a powerful, easy to use and free remote pc access software that can display the screen of another computer (via internet or network) on your own screen. The program allows you to use your mouse and keyboard to control the other PC remotely. It means that you can work on a remote computer, as if you were sitting in front of it, right from your current location.</description> </item> <item> <title>Shell Service Objects</title> <link>https://reactos.org/blogs/shell-service-objects/</link> <pubDate>Sat, 02 Aug 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/shell-service-objects/</guid> <description>Hello everyone! Long time no see!As some of you will probably know by now, I had a cooking accident, wherein my hand was splashed by very hot olive oil. I will skip the shameful details, but I want to say that for the next 10 days, I was unable to code properly.After those first 10 days, my bandage was replaced by a lighter dressing, which allowed me more mobility in my hand, and I began looking at my TODO list, for something “lighter” to pass the time.</description> </item> <item> <title>Merged Folders and undocumented interfaces</title> <link>https://reactos.org/blogs/merged-folders-undocumented-interfaces/</link> <pubDate>Sat, 12 Jul 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/merged-folders-undocumented-interfaces/</guid> <description>Hello, and welcome to my weekly report. I apologize for not having a report last weekend, so this week’s report will be longer than usual.Reading the issues in the community-powered Shell TODO List got me thinking about some issues that I previously thought were too complex for phase 1. Biggest of all, was the implementation of the CMergedFolder class structure. This set of classes is almost completely undocumented, and I suspect it has multiple features that don’t really fit together.</description> </item> <item> <title>June 2014 Meeting Minutes</title> <link>https://reactos.org/project-news/june-2014-meeting-minutes/</link> <pubDate>Wed, 09 Jul 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/june-2014-meeting-minutes/</guid> <description>Due to scheduling conflicts (World Cup) the June meeting was moved to July 3rd.2014-07-0319:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:22 by Aleksey Bragin. Point 1: Developer Briefings Point 2: Development Focus Point 1 Developers went over brief summaries of their current work and their intended plans. Aleksandar Andrejevic has been working on the memory manager and intends to complete the transition from using the old MEMORY_AREA to virtual address descriptors.</description> </item> <item> <title>The TODO list, collaborative edition</title> <link>https://reactos.org/blogs/todo-list-collaborative-edition/</link> <pubDate>Sat, 28 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/todo-list-collaborative-edition/</guid> <description>Hello! Welcome back to my weekly status report. I want to finally start writing the reports on Fridays, so it hasn’t been that many days since the last report, and there was a holiday in the middle of this week and some craziness you may already be aware of, so this report may end up either shorter than usual, or at least different. Sorry about that!I started the week by looking back at older “known issues”.</description> </item> <item> <title>PITA bugs part 4</title> <link>https://reactos.org/blogs/pita-bugs-part-4/</link> <pubDate>Thu, 26 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pita-bugs-part-4/</guid> <description>Most of the developers already know this, but my current job is as an engineer working on firmware and software for the trigger system of the Large Hadron Collider (yes, the thing that discovered the Higgs boson). Triggers are basically filters that take in the raw data coming out of the LHC and whittle down the noise to figure out what data is worth keeping and what can be discarded.</description> </item> <item> <title>Spilling the Wine</title> <link>https://reactos.org/blogs/spilling-the-wine/</link> <pubDate>Mon, 23 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/spilling-the-wine/</guid> <description>After the frustration of last week, I decided to take one last look at Deleaker, and try to figure out why it crashes in ReactOS during COM registration.The problem is, looking at the disassembly made it clear that the code is obfuscated. The functions start in one address, and then they jump all over the place, creating a mesh of small function chunks that even the best disassemblers seem unable to follow.</description> </item> <item> <title>Contributions: Command & Conquer: Red Alert 2</title> <link>https://reactos.org/blogs/contributions-command-conquer-red-alert-2/</link> <pubDate>Mon, 16 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/contributions-command-conquer-red-alert-2/</guid> <description>Thanks to BlackFox, we are proud to announce that "C&amp;C: Red Alert 2" is now running in ReactOS.So if you have a "lazy evening" just give it a try and enjoy the Allied or the Soviet campaigns!A GamePro reviewer said about this game: "Command &amp; Conquer: Red Alert 2 is the best 2D real-time strategy game since Starcraft".&nbsp;&nbsp;The ReactOS Menu is shown just to prove this is not a Windows capture but a ReactOS one.</description> </item> <item> <title>Machining Virtually</title> <link>https://reactos.org/blogs/machining-virtually/</link> <pubDate>Sat, 14 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/machining-virtually/</guid> <description>As I said in the last report, the week began by setting up a development environment in a Windows Server 2003 VM.I had to install Visual Studio 2010 and RosBE, and then download and compile the source code to verify that everything was working correctly. When I tried to compile, I realized two things. First, that vs2010 is much buggier than I remembered, and second, that compiling in a Virtual Machine with one cpu core is very very slow.</description> </item> <item> <title>Indiegogo Summary</title> <link>https://reactos.org/project-news/indiegogo-summary/</link> <pubDate>Fri, 13 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/indiegogo-summary/</guid> <description>The final count: 348 credits, 243 votes, 54 Wall of Fame, and $25,141 with over 500 backers from over two dozen countries.Even if the funding goal was not met, the response from the community has been phenomenal and we are grateful for all the support, not just in backing the campaign but also in spreading the word. Thanks to the Campaign, ReactOS and the Community Edition has been shown off by countless blogs, open source news feeds, community sites, and personal pages.</description> </item> <item> <title>ReactOS infrastructure goes fully HTTPS and joins Reset The Net</title> <link>https://reactos.org/project-news/reactos-infrastructure-goes-fully-https-joins-reset-the-net/</link> <pubDate>Wed, 11 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-infrastructure-goes-fully-https-joins-reset-the-net/</guid> <description>Dear all, You are still numerous people to use our infrastructure without any encryption.This news is the opportunity to inform you that the ReactOS infrastructure is fully available with encryption. Web sites (be them developpers or general purpose websites) are finally all HTTPS aware. Other services such as mails are also using secure protocols (SSMTP, SIMAP, and so on). Furthermore, for more security, we enabled HSTS (HTTP Strict Transport Security) &amp; PFS (Perfect Forward Secrecy).</description> </item> <item> <title>Leaks and corruption</title> <link>https://reactos.org/blogs/leaks-and-corruption/</link> <pubDate>Mon, 09 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/leaks-and-corruption/</guid> <description>After I finally managed to write last week’s report (have you ever tried to write something, and the words wouldn’t come out at all?), I continued looking at those nasty menu leaks.In an attempt to make the task simpler, I started looking for software with the ability to detect USER handle leaks. I checked the free (libre) alternatives first, but after not much luck I moved on to free (beer) software, and to fully commercial and proprietary software, when I finally found Deleaker.</description> </item> <item> <title>Leak-leaking leaks</title> <link>https://reactos.org/blogs/leak-leaking-leaks/</link> <pubDate>Mon, 02 Jun 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/leak-leaking-leaks/</guid> <description>I began the week by fixing the issue where the right button wasn’t detected by the code managing the start menu and submenus.I had been told that there was a JIRA issue related to the shutdown dialog, and that it had been implemented in some way in trunk already. I considered the means of calling that dialog from the shell32 function the start menu calls, but I dropped the idea some hours later, when I decided the code in msgina wasn’t designed to be called externally.</description> </item> <item> <title>Precise Calculator Joins Open Source Support Program</title> <link>https://reactos.org/project-news/precise-calculator-joins-open-source-support-program/</link> <pubDate>Fri, 30 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/precise-calculator-joins-open-source-support-program/</guid> <description>The calculator in modern versions of Windows is a very useful tool, but it is still limited in many respects especially when trying to punch in a long computation. Third parties have come up with a variety of alternatives though and it is the Project's great pleasure to present Precise Calculator as another member of the Open Source Support Program.Precise Calculator not only has feature parity with the native calculator on Windows, it offers a variety of enhancements such as unit conversions and even the ability to script calculations.</description> </item> <item> <title>PeaZIP Joins Open Source Support Program</title> <link>https://reactos.org/project-news/peazip-joins-open-source-support-program/</link> <pubDate>Wed, 28 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/peazip-joins-open-source-support-program/</guid> <description>The ReactOS Project is pleased another participant in the Open Source Support Program, PeaZIP.Many community members have been asking that some sort of zip utility be bundled with ReactOS for convenience and while participation in the program does not mean PeaZIP will be present by default, it will make it considerably easier for users to pre-stage PeaZIP so that it will be available to use once the installation of ReactOS is complete.</description> </item> <item> <title>PWCT Joins Open Source Support Program</title> <link>https://reactos.org/project-news/pwct-joins-open-source-support-program/</link> <pubDate>Wed, 28 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/pwct-joins-open-source-support-program/</guid> <description>The ReactOS Project is pleased to announce PWCT as a new participant in the Open Source Support Program.Programming Without Coding Technology (PWCT) is a set of tools that tries to make GUI programming more accessible, especially for people with little programming experience.PWCT is focused on visual programming&nbsp; and comes with a very practical syntax editor. Its program paradigm ranges from imperative to event driven and uses tree hierarchies instead of a drag-and-drop style.</description> </item> <item> <title>Advancing the TODO list...</title> <link>https://reactos.org/blogs/advancing-the-todo-list/</link> <pubDate>Mon, 26 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/advancing-the-todo-list/</guid> <description>If you recall from the last report, I had a few issues that I couldn’t fix myself. Well, Huw (Frontier) surprised me by sending me a patch to fix the activation issue!One of the issues in explorer-new was that every time you clicked on the desktop to open a new folder, it would launch a new instance of explorer.exe and run the new window on it. While the underlying issue still remains (it requires implementing the DDE handler for explorer), by disabling the version of the desktop window from RShell and using the existing one from shell32 instead, the shell takes a shortcut and runs the window directly on its own instance.</description> </item> <item> <title>LibreCAD joins ReactOS Open Source Support Program</title> <link>https://reactos.org/project-news/librecad-joins-reactos-open-source-support-program/</link> <pubDate>Mon, 19 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/librecad-joins-reactos-open-source-support-program/</guid> <description>Computer Aided Design software has long been the bastion of proprietary vendors such as Autodesk and SolidWorks where license seats tend to run into the thousands of dollars, putting them well out of reach of enthusiasts and hobbyists. It has only been recently that software for design work has become more accessible and in many ways this accessibility has helped spawn the entire Maker revolution that is happening now. The ReactOS Project is therefore very pleased to see LibreCAD join as the first member of the Open Source Support Program.</description> </item> <item> <title>On installers</title> <link>https://reactos.org/blogs/on-installers/</link> <pubDate>Mon, 19 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/on-installers/</guid> <description>The ReactOS installer is probably one of the oldest extant chunks of code in ReactOS that has not undergone significant overhauls for a very long time. Besides some tuning by Alex Ionescu to reduce resource usage and adding initial support for removable devices by Cameron Gutman, it has not seen any real major changes since Eric Kohl put it together all those years ago. For the developers, this was not too much of an issue since the installer did its job perfectly fine for the most part.</description> </item> <item> <title>The Bar of the Tasks</title> <link>https://reactos.org/blogs/the-bar-of-the-tasks/</link> <pubDate>Sun, 18 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-bar-of-the-tasks/</guid> <description>Hello! Another weekend is here, time for me to write a new report…Good news! I’m recovered and back on track! ;PThe week started by doing some boring investigation on how Windows manages the addressbar. If you didn’t guess already, analysing the behaviour of COM(ATL) classes is anything but simple. Interface inheritance is good for encapsulation, but bad for about anything else, including debugging. I did manage to figure out that it has two functions related to filling the addressbar combobox: one of them resets the contents and fills them from scratch, and the other only adds/changes/removes items related to the navigation.</description> </item> <item> <title>ReactOS Open Source Support Program</title> <link>https://reactos.org/project-news/reactos-open-source-support-program/</link> <pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-open-source-support-program/</guid> <description>Open source is more than just individual bits of software in isolation, it is about the ecosystem and environment that those bits of software come together to create. To that end, as part of the Community Edition initiative the ReactOS Project has put together the Open Source Support Program to help its end users in building that environment. When a user installs a new operating system, one of the first things they need to do is go and install all of the applications that they actually need.</description> </item> <item> <title>Small Hickup</title> <link>https://reactos.org/blogs/small-hickup/</link> <pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/small-hickup/</guid> <description>Hello everyone!This update will be rather short.At the same time I was writing last week's post, I had already started to feel sore in my throat.By Sunday evening, I had a slight fever, and by Monday it was obvious that I must have caught a flu.I have been trying to poke around as I was recovering, but I couldn't really focus enough to do anything complex.</description> </item> <item> <title>Tweaks and improvements</title> <link>https://reactos.org/blogs/tweaks-and-improvements/</link> <pubDate>Mon, 05 May 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/tweaks-and-improvements/</guid> <description>Sorry for the delay! Drupal was causing issues on submitting new things.This week I continued what I was doing the previous one.I focused my efforts in the browse window, tweaking the existing code, fixing logic issues and cleaning up the code a bit.There were some visual differences that were easy to fix, and others that will require a lot of work.I added some code to extract the icon and show it in the titlebar.</description> </item> <item> <title>Slowly getting closer...</title> <link>https://reactos.org/blogs/slowly-getting-closer/</link> <pubDate>Mon, 28 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/slowly-getting-closer/</guid> <description>Another week is over, and it’s time for me to look back and convert all my efforts into words.If you recall from the previous report, I was trying to fix the keyboard navigation. I managed to find and fix the issue that caused my code not to process the key presses correctly. With that issue fixed, I could implement the code to switch left and right between popup menus, and shell menus, both between a popup and a shell menu (which was already working last week), and between a shell menu and a popup.</description> </item> <item> <title>Menus and keyboard navigation</title> <link>https://reactos.org/blogs/menus-and-keyboard-navigation/</link> <pubDate>Tue, 22 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/menus-and-keyboard-navigation/</guid> <description>Sorry for the delay.This past week has been full of holidays and the inevitable family meetings, so the report will be short.After spending some more time on the context menu bug, I decided to leave it aside, and focus on things that improve the progress. If the code is incompatible with TortoiseGit for some reason, I can figure that out later.The next issue on the list was the keyboard navigation.</description> </item> <item> <title>At the peak of the mountain... there's a hill?</title> <link>https://reactos.org/blogs/at-the-peak-of-the-mountain-theres-a-hill/</link> <pubDate>Tue, 15 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/at-the-peak-of-the-mountain-theres-a-hill/</guid> <description>This week really didn’t “start”; it was merely a continuation of the past weeks.The issue where the toolbar did not receive clicks was one of those annoying problems where finding the apparent cause is easy, but finding a solution not so much. The issue, as far as I could tell, was related to using SetCapture as a means to track the mouse movement on top of the toolbar. If I disabled that piece of code, the clicks got through, but – of course – other features stopped working.</description> </item> <item> <title>Security issue on the ReactOS infrastructure</title> <link>https://reactos.org/project-news/security-issue-reactos-infrastructure-2014/</link> <pubDate>Wed, 09 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/security-issue-reactos-infrastructure-2014/</guid> <description>Dear all, In case you don't use SSL/TLS on our infrastructure (web sites - drupal, jira, fisheye), skip reading (and reconsider your choices about such non-usage). As you may (should?) have heard recently, OpenSSL has suffered a critical security vulnerability (CVE-2014-0160), known as Heartbleed Bug (http://heartbleed.com/). Most of our services were using an affected release of OpenSSL, with heartbeat feature activated. Be it, mails services, web services (Drupal, Jira).</description> </item> <item> <title>Indiegogo software/hardware vote info</title> <link>https://reactos.org/blogs/indiegogo-software-hardware-vote-info/</link> <pubDate>Mon, 07 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/indiegogo-software-hardware-vote-info/</guid> <description>So there's quite a few questions coming in about the campaign and its rewards. Questions are good, that means people are paying attention to us.One of the most common ones is in regard to how to "push" one's desired hardware or software. Well, the FAQ provides a brief explanation and we'll expand upon it here. After the funding period is over, a series of votes will be held to whittle down candidates.</description> </item> <item> <title>The Sisyphean Bug -- part 2</title> <link>https://reactos.org/blogs/the-sisyphean-bug-part-2/</link> <pubDate>Mon, 07 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-sisyphean-bug-part-2/</guid> <description>Over this past week, I continued fixing many small bugs, logic errors and such. Eventually I got to a point where I couldn’t deny the truth anymore.One of the lessons you are taught when learning to be an engineer (including software programming), and one that some people find hard to accept, is that you should always try to reuse existing processes and components, instead of reinventing your own. Because of that, I tried very hard to let the toolbars manage their own hot-tracking and only intercept hot-tracking events when strictly necessary.</description> </item> <item> <title>ReactOS (R)evolution is happening!</title> <link>https://reactos.org/project-news/reactos-revolution-happening/</link> <pubDate>Wed, 02 Apr 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-revolution-happening/</guid> <description>The ReactOS (R)evolution has begun!During the last couple of months we have been compiling all your&nbsp;feedback and suggestions about ReactOS in order to come up with a new&nbsp;paradigm. Now the time has come to show you what we've been working on:&nbsp;ReactOS Community Edition.ReactOS Community Edition is.. special, not just as a form of&nbsp;connecting further with our Community, it also opens doors to new&nbsp;ideas and strategies.We hope that you like all the work that we've done as we got inspired by&nbsp;a lot of your ideas.</description> </item> <item> <title>The Sisyphussian Bug</title> <link>https://reactos.org/blogs/the-sisyphussian-bug/</link> <pubDate>Sat, 29 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-sisyphussian-bug/</guid> <description>If you have been following the weekly reports, you know that I have been having issues with the focus manager.Well, this week I redesigned part of the focus manager, improving the structure so that it has more accurate information of what’s happening with the menus. While improving the code, I also fixed some bugs in the code.By Wednesday, I had what appeared to be working code. While running it in Windows 7, everything seemed to work, both in the start menu and the menu bar.</description> </item> <item> <title>Walking in circles</title> <link>https://reactos.org/blogs/walking-in-circles/</link> <pubDate>Mon, 24 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/walking-in-circles/</guid> <description>When work progresses, there’s a natural tendency towards running out of simple bugs to fix, and being left with those persistent ones that seem to have an intelligence of their own.I thought I was over those. That the bug I was working on would be a simple one.I wanted to have some test builds ready to share with the world, to be able to tell you all “hey look, if you don’t try to navigate with the keyboard, everything mostly acts the way it should, come and try!</description> </item> <item> <title>ReactOS. The (R)evolution is now here. </title> <link>https://reactos.org/project-news/reactos-revolution-now-here/</link> <pubDate>Sat, 22 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-revolution-now-here/</guid> <description>For a over a year we've been working hard on the ReactOS (R)evolution. It is undoubtedly the largest initiative from the ReactOS Foundation so far in terms of Strategy and Evolution. When Microsoft started counting down to the end we started counting down to a new beginning.Big changes are coming, while you will find some of them desired and expected thanks to your feedback and support, you'll also be greatly surprised by some others: It's time to move ReactOS to the Next Level.</description> </item> <item> <title>Blog comments</title> <link>https://reactos.org/blogs/blog-comments/</link> <pubDate>Thu, 20 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/blog-comments/</guid> <description>Due to the proliferating of spamming in the blog comments, we're going to disable it outright. For the future we'll link to a dedicated forum/thread for commenting on blog posts.</description> </item> <item> <title>Menus, menus</title> <link>https://reactos.org/blogs/menus-menus/</link> <pubDate>Sun, 16 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/menus-menus/</guid> <description>I began the week by fixing the menus, so that they would properly display submenus, and react to clicks. I was stuck for a bit, but I finally managed to find the problem that prevented the menus from working correctly within ReactOS.I set the filebrowser aside for a bit after this small success, to revisit some of the old bugs and pending tasks.I took a fresher look at the exec issue, where items weren’t clickable unless a submenu had been opened first, and I (painfully) traced the issue to pointless/bogus WM_ACTIVATE messages, with the new HWND being equal to the old HWND.</description> </item> <item> <title>NTVDM progress</title> <link>https://reactos.org/blogs/ntvdm-progress/</link> <pubDate>Thu, 13 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/ntvdm-progress/</guid> <description>A while back Aleksander Andrejevic began working on a NTVDM implementation for ReactOS to support 16bit programs. This was one of the more often requested features by the community, which was met with some ambivalence by the developers themsleves since it entailed a significant amount of work. Aleksander then appeared and instead of simply asking for the feature, rolled up his sleeve to do the actual work. Since then NTVDM has made significant progress and other developers like Hermès Bélusca-Maïto and community member Vampyre have joined in to help.</description> </item> <item> <title>ReactOS RShell</title> <link>https://reactos.org/blogs/reactos-rshell/</link> <pubDate>Mon, 10 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/reactos-rshell/</guid> <description>I began the week by testing the progress of the start menu in ReactOS.You may remember this screenshot from last weekend’s report. In it, you can see the results of implementing vertical menus in a different, more documented, way. This method requires more work to be done per item, to make them all wrap into a new row, but it is supported by the Wine toolbar implementation ReactOS uses.</description> </item> <item> <title>Feburary 2014 Meeting Minutes</title> <link>https://reactos.org/project-news/february-2014-meeting-minutes/</link> <pubDate>Tue, 04 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/february-2014-meeting-minutes/</guid> <description>2014-02-2719:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:14 by Aleksey Bragin.Point 1: Shell Development ProgressPoint 2: Contract JobsPoint 1David Quintana and Giannis Adamopoulos provided a summary of the state of the explorer shell implementation, reporting that a fair amount of the start menu functionality is working when run on Windows. Running the current code in ReactOS however requires some improvements to code imported from Wine with respect to vertical toolbars with custom backgrounds and edges.</description> </item> <item> <title>Look&Feel of the Start Menu</title> <link>https://reactos.org/blogs/look-feel-start-menu/</link> <pubDate>Mon, 03 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/look-feel-start-menu/</guid> <description>This week’s work began by improving the look&amp;feel of the start menu so that it matches the Windows start menu better.The first step was to improve the look of the menu: This included positioning, colours, dropdown arrows, icon sizes, etc.I continued by trying to improve the feel of the menu: Hot-tracking behaviours, keyboard navigation, etc. The keyboard navigation keeps resisting me somewhat, though, as it tends to glitch when using the left/right arrow keys to open and close submenus, but moving up and down seems to behave as expected.</description> </item> <item> <title>Regarding the motto proposal</title> <link>https://reactos.org/blogs/regarding-motto-proposal/</link> <pubDate>Mon, 03 Mar 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/regarding-motto-proposal/</guid> <description>The ReactOS Project recently received a proposal to adopt "Open your Windows to Freedom" as the official project motto, with the proposed motto itself having been selected in a self-organized vote by the community. After internal discussions between the team developers and other administrative members, the Project has chosen to reject the proposal. The following outlines the reasons.The overaching issue the team has with the proposal is the impression that "</description> </item> <item> <title>The Starts and The Menus</title> <link>https://reactos.org/blogs/the-starts-and-the-menus/</link> <pubDate>Sun, 23 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-starts-and-the-menus/</guid> <description>The week began by implementing the functionality needed to handle clicking on menu items. This involved sending a callback notification for the currently selected item, asking the callback to execute the appropriate action of the item.Some of the items are not meant to be clicked on and are supposed to show a submenu instead. For these items I had to subclass the toolbar windows so that I could add a timer on hover and handle the opening of the submenu in the resulting WM_TIMER event, which would be received by the toolbar, but needed to be handled by my code.</description> </item> <item> <title>Shell experiments: Progress on the start menu</title> <link>https://reactos.org/blogs/shell-experiments-progress-on-the-start-menu/</link> <pubDate>Sun, 16 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/shell-experiments-progress-on-the-start-menu/</guid> <description>Work, this week, began with finishing the initial implementation of CMenuSite. This class and the window it creates act as an intermediary between a BaseBar and a MenuBand, forwarding the events and messages either to the child band, or to the parent bar, as necessary. It handles the sizing of the child band, to adapt it to changes in the available space. It also provides certain services related to the positioning and sizing of the child bar, which it handles by forwarding some requests to the child, and the rest to the parent.</description> </item> <item> <title>On ARM</title> <link>https://reactos.org/blogs/on-arm/</link> <pubDate>Tue, 11 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/on-arm/</guid> <description>A lot of people have expressed excitement or enthusiasm regarding ARM though when asked to explain their enthusiasm the result has often been incoherent babbling. In other words, the vast majority of people still have trouble communicating their thoughts in a clear and, more importantly, concise, manner. ARM is interesting though and from multiple perspectives. The biggest point is the amount of processing power it represents despite its small physical, power, and thermal footprint.</description> </item> <item> <title>Proper?! Windows explorer.exe implementation</title> <link>https://reactos.org/blogs/proper-windows-explorer-exe-implementation/</link> <pubDate>Tue, 11 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/proper-windows-explorer-exe-implementation/</guid> <description>"A picture is worth a thousand words"Thanks Giannis for this awesome work</description> </item> <item> <title>Anonymous spread word of ReactOS Kickstarter</title> <link>https://reactos.org/blogs/anonymous-spread-word-reactos-kickstarter/</link> <pubDate>Mon, 10 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/anonymous-spread-word-reactos-kickstarter/</guid> <description>An interesting tidbit.First because the motto seems to be real: "We are All. We are everywhere".&nbsp; Second, because they have just twitted the following::&nbsp;As you may know, ReactOS began a Kickstarter campaign to create a business product to help supporting and boosting current ReactOS development.What is it about? Thorium Core is about taking the ReactOS operating system from the proof-of-concept and engineering stages to building a fast and lightweight solution that can be tailored to suit the computing needs of both private and commercial users.</description> </item> <item> <title>Drag&Drop and Improved interactions.</title> <link>https://reactos.org/blogs/drag-drop-improved-interactions/</link> <pubDate>Sat, 08 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/drag-drop-improved-interactions/</guid> <description>One of the main issues people trying out ReactOS have complained about is the clunkiness of the shell and how things they expect to work don't. As the shell serves as the main gateway to using the operating system, if it is hard to use then the OS itself becomes hard to use.When talking about "interaction" we can think in two different ways of interaction: The interaction between the user and ReactOS Explorer and the interaction between applications and ReactOS Explorer(well, really the Shell).</description> </item> <item> <title>ReactOS 0.3.16 Released</title> <link>https://reactos.org/project-news/reactos-0316-released/</link> <pubDate>Thu, 06 Feb 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0316-released/</guid> <description>The ReactOS Project is pleased to announce the release of version 0.3.16. A little under a year has passed since the previous release and a significant amount of progress has been made. Some of the most significant include completion of the CSRSS rewrite and the first stages of a shell32 rewrite. 0.3.16 is in many ways a prelude to several new features that will provide a noticeable enhancement to user visible functionality.</description> </item> <item> <title>Contributions: MS Office 2003</title> <link>https://reactos.org/blogs/contributions-ms-office-2003/</link> <pubDate>Fri, 31 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/contributions-ms-office-2003/</guid> <description>This time a double-win.Not so long ago trying to run a whole office suite was almost a dream. Just launching an app was a success.There was just one complex suite almost working: "SoftMaker Office 2008". A nice, and mostly unknown, Microsoft Office clone. It was such a good Office clone that it is closed and non-free.From past experience you can find two kind of users out there: "</description> </item> <item> <title>Contributions: TeamSpeaker!</title> <link>https://reactos.org/blogs/contributions-teamspeaker/</link> <pubDate>Fri, 31 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/contributions-teamspeaker/</guid> <description>&nbsp;After opening the totally unofficial, irrelevant, NôÓbsletter section, now it's time to open a new serious section oriented and opened to the Community. Because, as you may know, an opensource project has sense thanks because its supporting Community behind it.Welcome to this awesome, yours, "Contribution" section.From time to time astonishing content is created by the Community and shared through IRC or Forum. It's a pity that such content keeps moving just in the inner circle.</description> </item> <item> <title>Todo list: ReactOS edition</title> <link>https://reactos.org/blogs/todo-list-reactos-edition/</link> <pubDate>Tue, 28 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/todo-list-reactos-edition/</guid> <description>So there is this tendency amongst the community to ask why the project doesn't do this or the project doesn't do that. A lot of the stuff people want done would tend to fall into my area of responsibility. I tend to frown upon people who make more work for me so I often push back, hard, requiring that others demonstrate their willingness to do some heavy lifting before I will consider a proposal.</description> </item> <item> <title>Shell Contract Report</title> <link>https://reactos.org/project-news/shell-contract-report/</link> <pubDate>Sat, 25 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/shell-contract-report/</guid> <description>Several months ago the ReactOS Foundation issued a development contract to Giannis Adamopoulos to work on improving ReactOS' shell support. The end goal of this work was to get explorer_new running, though it was understood from the onset that a single contract may not be sufficient to finish the project. Still, the first contract would at least provide a solid foundation that could be built upon. The fruits of Giannis' work were recently previewed with screenshots of explorer_new running on Windows 8 and its inclusion into ReactOS, even though not all functionality is working.</description> </item> <item> <title>The shell</title> <link>https://reactos.org/blogs/the-shell/</link> <pubDate>Wed, 22 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-shell/</guid> <description>A part of me feels a tad guilty testing all of you with promises regarding shell progress. Another part of me feels no guilt whatsoever and I tend to listen to that part more. It helps having no conscience when doing PR, I have found.Anyway, recently I started doing the prep work needed for a new release of ReactOS, which will be 0.3.16 despite the constant badgering for me to just go ahead and call the next release 0.</description> </item> <item> <title>Thorium: On the embedded use case</title> <link>https://reactos.org/blogs/thorium-embedded-use-case/</link> <pubDate>Tue, 14 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/thorium-embedded-use-case/</guid> <description>When people think about "embedded" systems, they often think about ARM systems running Linux. Well, that's one part of the embedded world, but another big chunk is actually x86 systems running Windows. For that matter, one of the biggest reasons for someone to use x86 in an embedded application is to get the ability to run Windows applications. There are a LOT of point-of-sale and other dumb terminals out there that run Windows due to the widespread availability of a Windows application to do damn near anything.</description> </item> <item> <title>Response to Thorium questions</title> <link>https://reactos.org/blogs/response-to-thorium-questions/</link> <pubDate>Mon, 06 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/response-to-thorium-questions/</guid> <description>Quite a few people that first look at Thorium ask questions about what exactly it is for and what purpose does it serve. These are not unreasonable questions to ask and the answers are sometimes difficult to parse due to the complexity of Thorium itself. The second set of questions relates to why we believe Thorium is achievable with the amount of funding requested. Let's go over both sets and hopefully they will convince you we aren't completely out of our minds.</description> </item> <item> <title>Thorium Core</title> <link>https://reactos.org/project-news/thorium-core/</link> <pubDate>Mon, 06 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/thorium-core/</guid> <description>Right before Christmas, Aleksey Bragin and Steven Edwards launched the Thorium Core Kickstarter appeal. At its most basic level, the goal is to advance ReactOS development by creating a commercial project using it. The proposed product, as it were, is a remotely accessible desktop environment, basically a computer in the cloud. No longer does one need to shuffle around USB sticks or reinstall applications from computer to computer, simply connect to Thorium and you'll be back to your familiar setup.</description> </item> <item> <title>Monstera</title> <link>https://reactos.org/blogs/monstera/</link> <pubDate>Sun, 05 Jan 2014 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/monstera/</guid> <description>This post really should have been made months ago, but finding the time to write a full blown newsletter has been getting more and more scarce. That being said, I've decided for the short term to split things that would normally act as a single newsletter section into separate blog posts so I don't need to wait and gather things.There was a lot of speculation as to what Monstera was when Aleksey made his commit with some suggesting it is a repeat of his ARWINSS effort but targetted at the memory manager.</description> </item> <item> <title>A Little Christmas Gift</title> <link>https://reactos.org/project-news/little-christmas-gift/</link> <pubDate>Tue, 24 Dec 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/little-christmas-gift/</guid> <description>A year ago the project ran a donation drive to raise money to pay for funded development of ReactOS. While the drive was moderately successful, a slight paperwork issue with the German foundation caused a temporary halt to funded development contracts. Since then, the issue has been resolved and the project has been working to restart handing out development contracts to demonstrate that the money donated to the project is being put to good use.</description> </item> <item> <title>Announcement: Server downtime on 28th December</title> <link>https://reactos.org/project-news/announcement-server-downtime-28-december/</link> <pubDate>Mon, 16 Dec 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/announcement-server-downtime-28-december/</guid> <description>In order to fix the availability problems of our Website, the ReactOS Infrastructure Team will upgrade another Server on 28th December.This will result in a downtime for the following public services:www.reactos.org Websitejira.reactos.org Bugtrackerreactos.reactos.org Test ServerSVN will continue to function, as well as our Build and Test bots. The latest ReactOS builds can be downloaded at iso.reactos.org in the meantime.After the upgrade, you should be able to enjoy a higher availability and faster response times when using the ReactOS Online Services.</description> </item> <item> <title>Intellectual Property: Ideology vs Practicality</title> <link>https://reactos.org/blogs/intellectual-property-ideology-vs-practicality/</link> <pubDate>Sat, 14 Dec 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/intellectual-property-ideology-vs-practicality/</guid> <description>The thing that people need to keep in mind when discussing the GPL is that it was created to achieve an ideological and political goal, namely that users of software should have the right to modify and extend the software as they see fit. To achieve this goal, the GPL seeks to ensure that the source code is always available and that reusing the source code in question comes without any restrictions save for what the GPL itself imposes in order to ensure this "</description> </item> <item> <title>Developer services offline</title> <link>https://reactos.org/project-news/developer-services-offline/</link> <pubDate>Mon, 25 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/developer-services-offline/</guid> <description>Updated at 13h21 CET: We are trying to restore all the services at the moment, on a new server. Everything should be working again. Let's hope it will be a stable server this time... Except issues with mail server and delays with mails for the moment.Dear all,On Saturday, we attempted an upgrade of one of our old hypervisor. If the upgrade went fine, it appears that the new server provided by our hoster is totally unstable.</description> </item> <item> <title>NôÓbsletters: Moar games!Moar compatibility!</title> <link>https://reactos.org/blogs/moar-games-moar-compatibility/</link> <pubDate>Wed, 20 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/moar-games-moar-compatibility/</guid> <description>Well, let's face it! Users love Games. Me too.I still have some really great childhood memories, playing with those lovely old games.Do you remember trying to save the poor Lemmings? Damn, they do seem predestined to fall!&nbsp;Or what about XWing? And Dangerous Dave (a blatant game copy of&nbsp; inspired by Super Mario)? I still have nightmares with the Aliens from X-COM every once in a while !</description> </item> <item> <title>Intellectual Property: Fundamentals</title> <link>https://reactos.org/blogs/intellectual-property-fundamentals/</link> <pubDate>Fri, 15 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/intellectual-property-fundamentals/</guid> <description>Intellectual property is something way too many people like to talk about without actually understanding the nuances of the laws supporting them. While I could easily go on and on about these misconceptions, I'll focus primarily on those that relate to free software and open source, of which there are plenty. Some of the more prominent ones include incorrectly claiming what is and what is not a GNU Public License (GPL) violation and the notion that companies should "</description> </item> <item> <title>October 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/october-2013-meeting-minutes/</link> <pubDate>Thu, 14 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/october-2013-meeting-minutes/</guid> <description>2013-10-3119:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:08 by Aleksey Bragin.Point 1: CoordinationPoint 2: Code Style GuidelinesPoint 3: Donations and HardwarePoint 1Aleksey Bragin opened up the meeting with a statement that the project's members need to coordinate and work better together to avoid internal confusion as to what work is being done and what work requires some help due to other commitments by team members.Point 2Colin Finck presented for approval a finalized draft for the project's coding style guideline.</description> </item> <item> <title>ReactOS Talk at Google Montreal</title> <link>https://reactos.org/project-news/reactos-talk-google-montreal/</link> <pubDate>Thu, 14 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-talk-google-montreal/</guid> <description>Alex Ionescu was recently at Google Montreal providing training in Windows internals. He was invited to do one of their monthly tech talks and did an introduction to ReactOS and discussed the project's current status. It's an excellent view for anyone who wants to get an overview from a developer's perspective.</description> </item> <item> <title>September 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/september-2013-meeting-minutes/</link> <pubDate>Mon, 04 Nov 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/september-2013-meeting-minutes/</guid> <description>VersioningThe question of changing the versioning scheme was brought up again by and Victor Martinez and Ziliang Guo. Objections came in principally two forms from developers, the first that none of them saw a reason for changing and the other that attempting to use a new scheme based on progress of components was futile as developers work on components at their whim and thus progress cannot be scheduled. Aleksey Bragin again attempted to push developers to make further use of JIRA to track development and thus perhaps set the stage for resolving the question of development progress.</description> </item> <item> <title>Newsletter 99</title> <link>https://reactos.org/blogs/newsletter-99/</link> <pubDate>Mon, 09 Sep 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-99/</guid> <description>ShellSince the last newsletter Giannis Adamopoulos has completed his development contract and while a more formal report will be published later, a brief summary follows. The fruits of his labor are already visible in that explorer_new can actually start in ReactOS and allow a user to browse the directories. Much of this was achieved by completing work Andrew Hill started. Giannis also spent considerable amounts of time trying to understand how the various menus in the shell worked.</description> </item> <item> <title>August 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/august-2013-meeting-minutes/</link> <pubDate>Mon, 02 Sep 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/august-2013-meeting-minutes/</guid> <description>Note that while there was a June meeting, all of the points were internal in nature. As such, there will be no public minutes for that meeting.2013-08-2919:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:04 by Aleksey Bragin.Point 1: Funded Development StatusPoint 2: Version SchemePoint 3: SEOPoint 4: FOSDEMPoint 1Matthias Kupfer reported that revised rules for the German ReactOS Foundation are ready for review. Assuming the tax authorities do not find any new problems, he believes the German ReactOS Foundation will be able to directly issue fellowships for ReactOS developments around the turn of the year.</description> </item> <item> <title>Newsletter 98</title> <link>https://reactos.org/blogs/newsletter-98/</link> <pubDate>Wed, 07 Aug 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-98/</guid> <description>Explorer Shell A while back the project announced a development contract for Giannis Adamopoulos to work on getting the necessary supports for running explorer-new to run on ReactOS. Since then, Giannis has been very busy and has made considerable progress. Much of his work has been properly separating responsibilities in the various components so that there are clear delineations of who does what.There are two major accomplishments, both fairly wide in scope.</description> </item> <item> <title>July 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/july-2013-meeting-minutes/</link> <pubDate>Sun, 04 Aug 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2013-meeting-minutes/</guid> <description>Note that while there was a June meeting, all of the points were internal in nature. As such, there will be no public minutes for that meeting.2013-07-2519:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:23 by Aleksey Bragin.Point 1: StudentsPoint 2: ReleasePoint 3: ContractsPoint 1Aleksey Bragin reported that several of his students showed great promise. Three students in particular have started doing some low level work in extending ReactOS&#39; functionality in the area of virtualization.</description> </item> <item> <title>Newsletter 97</title> <link>https://reactos.org/blogs/newsletter-97/</link> <pubDate>Mon, 01 Jul 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-97/</guid> <description>C++ One of the last big missing pieces of building ReactOS using Visual Studio was support for C++. In ReactOS, the biggest piece of C++ code is explorer, without which users have no graphical shell when ReactOS boots up. Support for C++ requires not just a compiler capable of building C++ code, but also the presence of the standard template library. For developers where C++ was their first language, usage of the STL is fairly common and it is almost guaranteed to be linked in by default regardless of whether it is used or not.</description> </item> <item> <title>PITA bugs part 3</title> <link>https://reactos.org/blogs/pita-bugs-part-3/</link> <pubDate>Wed, 26 Jun 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pita-bugs-part-3/</guid> <description>It is somewhat difficult to put into words just how much hate I have for this particular issue. Debugging it ended up taking an entire week and the result surprised pretty much everyone on the team, including the senior developers. The issue that was highlighted however has very deep root causes that touch upon the very foundation of the C ABI and its brittleness.First, a slight aside. In C, there is a family of functions that take in a variable number of arguments, the printf functions.</description> </item> <item> <title>May 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/may-2013-meeting-minutes/</link> <pubDate>Fri, 21 Jun 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/may-2013-meeting-minutes/</guid> <description>2013-05-3019:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:11 by Aleksey Bragin.Point 1: ContractsPoint 2: ReleasePoint 1Colin Finck reported that Matthias Kupfer had another meeting with tax advisers to try to resolve the issue of direct funding. Ziliang Guo prodded Aleksey Bragin again to remind him that the Russian ReactOS Foundation needed to start issuing invoices to cover existing contracts. A suggestion was made to hire freelancers to help develop the project, but there was internal resistance to this as traditionally open source projects do not fund development commercially like that unless under extraordinary circumstances.</description> </item> <item> <title>PITA bugs part 2</title> <link>https://reactos.org/blogs/pita-bugs-part-2/</link> <pubDate>Sat, 15 Jun 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pita-bugs-part-2/</guid> <description>Weclome to the second part of the series where I discuss bugs that were truly irritating to debug. In general, fixing a bug is usually simple. Finding the bug is where the actual work is involved.As I mentioned before, I currently work as an intern at a company that does development work on a UEFI BIOS. BIOS development is difficult because we are often so close to the hardware that we often do not have the convenience of things like a debugger.</description> </item> <item> <title>Sourceforge Project of the Month</title> <link>https://reactos.org/project-news/sourceforge-project-of-the-month/</link> <pubDate>Sat, 01 Jun 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/sourceforge-project-of-the-month/</guid> <description>The ReactOS project has won Sourceforge Project of the Month for June. Thanks to all of our fans who voted for us, netting us the plurality of votes. You can visit Sourceforge to read the interview they conducted with Aleksey Bragin, the project coordinator. Be sure not to miss the little tidbit at the end where Aleksey hints about the future of ReactOS and funded development.</description> </item> <item> <title>On desktops</title> <link>https://reactos.org/blogs/on-desktops/</link> <pubDate>Fri, 31 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/on-desktops/</guid> <description>In the recent craze over smartphones, tablets, and what I&#39;ll term webbooks (think ChromeOS machines), many companies seem to have forgotten the greatest achievement of modern desktop operating systems, namely the ability to multitask. Smartphone OSes originally either did not have this capability built in or did not expose it to the end user. This was understandable, as smartphones operate under different constraints with respect to power and screen space.</description> </item> <item> <title>ReactOS 0.3.15 Released</title> <link>https://reactos.org/project-news/reactos-0315-released/</link> <pubDate>Thu, 30 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0315-released/</guid> <description>The ReactOS project is proud to announce the release of version 0.3.15. A culmination of over a year of development, 0.3.15 incorporates several architectural enhancements to create a more compatible and conformant implementation of the NT architecture. Perhaps the most user visible enhancement is initial support for USB devices, both storage and input.Infrastructure wise, this is the first release of ReactOS using CMake instead of rbuild. The conversion to CMake has allowed developers to generate Visual Studio solutions for working on the code, though several C++ components still need work before support for Microsoft&#39;s toolchain is complete.</description> </item> <item> <title>Use cases for ReactOS</title> <link>https://reactos.org/blogs/use-cases-for-reactos/</link> <pubDate>Sun, 26 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/use-cases-for-reactos/</guid> <description>Many people see ReactOS as a Windows XP successor, a way for them to avoid the changes Microsoft brought about in Windows 8. This is a somewhat idealized goal, as ReactOS would need to be much more complete before it could attempt to fill in that role. There are however other use cases for which ReactOS is much closer to being ready for. Many of these however are more business use cases than consumer use cases.</description> </item> <item> <title>A perspective: Games vs Microsoft</title> <link>https://reactos.org/blogs/perspective-games-vs-microsoft/</link> <pubDate>Fri, 24 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/perspective-games-vs-microsoft/</guid> <description>Deciding whether to write this latest entry was a tad difficult, if only because I&#39;m starting to feel like I&#39;ve been harping a bit too much on Microsoft, but some of the information that has trickled out about the new Xbox bears some putting into context. Specifically, the requirement that anyone wanting to publish a game to Xbox Live needs to sign on with a publisher, so no self-publishing by indies.</description> </item> <item> <title>ReactOS at LinuxTag</title> <link>https://reactos.org/project-news/reactos-at-linuxtag/</link> <pubDate>Tue, 21 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-at-linuxtag/</guid> <description>The ReactOS will have a display at the LinuxTag expo in Berlin from May 22nd through the 25th. People visiting will get a sneak preview of the 0.3.15 release, along with some of the new eyecandy the development team has decided to turn on. The project will be in hall 7.1c booth179b.</description> </item> <item> <title>The cost of progress</title> <link>https://reactos.org/blogs/the-cost-of-progress/</link> <pubDate>Tue, 21 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/the-cost-of-progress/</guid> <description>The project often gets suggestions for what people consider to be &quot;improvements&quot; over how Windows does something. Nothing wrong with that, save for the fact people rarely consider the implications of what they are asking for. The most recent spurt was in &quot;enhancements&quot; for the shell, some of it due to the renewed attention I started drawing to it. We&#39;ll take the request for &quot;full screen&quot; application support to start with.</description> </item> <item> <title>Shell Development Contract</title> <link>https://reactos.org/project-news/shell-development-contract/</link> <pubDate>Sun, 19 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/shell-development-contract/</guid> <description>The Foundation for the Advancement of Information Technologies ReactOS Foundation (Russia) is pleased to announce a development contract with Giannis Adamopoulos. The contract will involve extending the shell32 library to support running the explorer-new shell. Focus will be on the browseui components, needed to allow explorer-new to display its file browser. This is the first step to ultimately replacing the existing explorer shell. Duration: 2 months Time: 100 hours Rate: 600&euro;</description> </item> <item> <title>Newsletter 96</title> <link>https://reactos.org/blogs/newsletter-96/</link> <pubDate>Thu, 16 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-96/</guid> <description>Testing and Debugging The hardest thing about writing software is finding the source of bugs. Good testers are as such extremely valuable, and those able to use debuggers well even more so. Two issues were recently dealt with thanks to one such tester, Olaf Siejka.The first issue involved Microsoft Excel Viewer, an application that as its name suggests allows for viewing of spreadsheets but not editing. Word Viewer actually worked in ReactOS, and Excel Viewer&#39;s failure drew Olaf&#39;s attention.</description> </item> <item> <title>Funded Development Issue Resolved</title> <link>https://reactos.org/project-news/funded-development-issue-resolved/</link> <pubDate>Tue, 14 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/funded-development-issue-resolved/</guid> <description>After a considerable amount of effort, the issue with funding development using donations collected by ReactOS Deutschland e.V. has been worked around. As a result of this, the Project is working to arrange additional funded development to ensure that the money donated to the project is put to the use it was intended. We hope to pay special attention to the shell, themes, and USB to improve the overall user experience.</description> </item> <item> <title>A perspective: managed developers beyond Microsoft</title> <link>https://reactos.org/blogs/perspective-managed-developers-beyond-microsoft/</link> <pubDate>Sun, 12 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/perspective-managed-developers-beyond-microsoft/</guid> <description>In my last post, I talked a bit about how Microsoft&#39;s fixation on Metro/Modern and the appstore had resulted in it basically ignoring large swathes of its developer community. So that post got a lot more attention than I was expecting, with some agreeing and others disagreeing. Some discussions however took a turn where people began debating how much trouble, if any, developers were in with Microsoft&#39;s move. This was something that I had decided not to explore further because the previous post had already reached a fairly ridiculous length.</description> </item> <item> <title>A perspective: developers vs Microsoft</title> <link>https://reactos.org/blogs/perspective-developers-vs-microsoft/</link> <pubDate>Sat, 11 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/perspective-developers-vs-microsoft/</guid> <description>Most people understand that Windows is used by a variety of people who have a variety of needs, ranging from corporate server to workstation to POS terminals to home PC and beyond. Most people accept that whenever Microsoft updates Windows, it has to balance the competing requirements to find some kind of workable compromise. There is however another set of competing requirements that many do not really register, even those that call themselves power users or are IT admins.</description> </item> <item> <title>PITA bugs part 1</title> <link>https://reactos.org/blogs/pita-bugs-part-1/</link> <pubDate>Mon, 06 May 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/pita-bugs-part-1/</guid> <description>In my years working as a programmer, I have run into many, many bugs and introduced many of my own. A few stand out as tremendously irritating to debug, as their behavior made little sense and the source of the bug was non-obvious. The first issue was from my work for the HTCondor Project, an open source cluster management software used by research groups around the world including those working on crunching data from the Large Hadron Collider, the LIGO graviton detector, and the IceCube neutrino observatory.</description> </item> <item> <title>April 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/april-2013-meeting-minutes/</link> <pubDate>Tue, 30 Apr 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/april-2013-meeting-minutes/</guid> <description>2013-04-2519:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:20 by Aleksey Bragin. Point 1: Legal Whitepaper Point 2: 0.3.15 Point 3: Contracts Point 4: 0.4 Point 1 Ziliang Guo reported that the intellectual property guidelines had been agreed upon with other developers and would be published the coming weekend.Point 2 Ziliang stated that he wanted the release to be out the coming weekend regardless of whether the changelog was complete or not.</description> </item> <item> <title>An introduction</title> <link>https://reactos.org/blogs/introduction/</link> <pubDate>Mon, 29 Apr 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/introduction/</guid> <description>Despite my involvement with the project for several years, I do not believe I have ever actually introduced myself. While the developers and a few other members of the community know about me, in general the rest of the community knows me as the guy that writes the newsletters and sometimes posts snarky comments on the forum whenever I see something that I think is a bad idea. As such, this might be a good time to introduce myself and provide some background.</description> </item> <item> <title>Newsletter 95</title> <link>https://reactos.org/blogs/newsletter-95/</link> <pubDate>Thu, 11 Apr 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-95/</guid> <description>OpenGL The ReactOS project has relied on the Mesa Project for OpenGL 3D graphics for a long time, but unfortunately the code needed by ReactOS is no longer maintained by Mesa. Actual rendering involves a chain of components, one of which is the called the installable client driver. The ICD is for the most part bundled with the graphics card driver, though it can also be a driver that performs rendering completely in software.</description> </item> <item> <title>March 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/march-2013-meeting-minutes/</link> <pubDate>Wed, 10 Apr 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/march-2013-meeting-minutes/</guid> <description>2013-03-2819:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:26 by Aleksey Bragin.Point 1: GSoC StatusPoint 2: CLT ReportPoint 3: LinuxTag BerlinPoint 4: Foundation FundingPoint 5: Release PlansPoint 1Amine Khaldi reported that the Google Summer of Code application had been completed and a preliminary list of project proposals set up on the wiki, with a link to the main GSoC page put on the front page. Feedback from Google indicated that there was nothing wrong per se with the application last year and the project was encouraged to try again this year.</description> </item> <item> <title>February 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/february-2013-meeting-minutes/</link> <pubDate>Wed, 13 Mar 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/february-2013-meeting-minutes/</guid> <description>2013-02-2819:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:30 by Aleksey Bragin.Point 1: WebsitePoint 2: GSoCPoint 3: CLT2013Point 1Aleksey Bragin reported that backend wise the new site appeared to be functionally complete and that the majority of the remaining work would likely be content-centric. Aleksey also wanted to include a few more people who would have the ability to work on the site so that improvements were not bottlenecked because he or Pierre Schweitzer were busy.</description> </item> <item> <title>Newsletter 94</title> <link>https://reactos.org/blogs/newsletter-94/</link> <pubDate>Wed, 27 Feb 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-94/</guid> <description>Site Migration The project recently migrated from its old site to one using the Drupal content management system. Work on this migration had been going on in some form for the last year, with a major milestone being the migration from Bugzilla to JIRA. The migration of the site proper however was nowhere as smooth as many people, including myself, desired. One of the root causes for the bumpy migration was my fault actually, when I sent an email claiming that the site's content was at a state where it should not be a blocker to migration.</description> </item> <item> <title>January 2013 Meeting Minutes</title> <link>https://reactos.org/project-news/january-2013-meeting-minutes/</link> <pubDate>Thu, 07 Feb 2013 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/january-2013-meeting-minutes/</guid> <description>2013-01-3119:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:18 by Aleksey Bragin. Point 0: CLT2013 Point 1: Donation Campaign and Contract Status Point 2: Website Point 3: University Cooperation Point 4: UDF Support Point 0Daniel Reimer called for volunteers to attend this year's CLT2013 convention. Several of the German members are tentatively able to come, but Daniel wanted a bit more buffering and manpower present to better deal with more people coming.</description> </item> <item> <title>November 2012 Meeting Minutes</title> <link>https://reactos.org/project-news/november-2012-meeting-minutes/</link> <pubDate>Thu, 20 Dec 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/november-2012-meeting-minutes/</guid> <description>2012-11-2919:00 UTCfreenode, #reactos-meetingProceedingsMeeting started at 19:02 by Aleksey Bragin. Point 1: Contract Status Point 2: Release Status Point 3: Website Status Point 4: VirtualPC Support Point 1The development team has not been able to get in touch with Magnus Olsen or Mike Nordell for status updates and currently considers these contracts to be voided. Edijs Kolesnikovics reported that work is progressing well, though he faces difficulties in trying to use AutoHotkey to test games.</description> </item> <item> <title>October 2012 Meeting Minutes</title> <link>https://reactos.org/project-news/october-2012-meeting-minutes/</link> <pubDate>Tue, 06 Nov 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/october-2012-meeting-minutes/</guid> <description>2012-10-3019:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:20 by Aleksey Bragin Point 1: Contract status Point 2: Voice chat Point 1People with outstanding contracts were asked to report their progress. There are currently four contracts outstanding for Mike Nordell, Magnus Olsen, Edijs Kolesnikovics, and James Tabor. Edijs is on his third contract extension after completing his second. Ziliang Guo reported that the second contract's report will be published but had been delayed due to Amine Khaldi being away.</description> </item> <item> <title>Newsletter 93</title> <link>https://reactos.org/blogs/newsletter-93/</link> <pubDate>Fri, 19 Oct 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-93/</guid> <description>Desktops and Windows In the Windows operating system, the desktop one sees is made up of three things, a kernel mode desktop object, a user mode desktop window, and a desktop thread. While the desktop object can be considered almost mundane, the window and thread are somewhat special. In Windows, desktop windows are created differently from regular windows and all share a single desktop thread. This thread handles messages sent to the desktop window, though users will generally only see the desktop window if the explorer shell is not running.</description> </item> <item> <title>September 2012 Meeting Minutes</title> <link>https://reactos.org/project-news/september-2012-meeting-minutes/</link> <pubDate>Wed, 03 Oct 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/september-2012-meeting-minutes/</guid> <description>2012-09-2719:00 UTCfreenode, #reactos-meetingProceedingsMeeting started at 19:17 by Aleksey Bragin&nbsp; 0. Website progress, plan for the next month. 1. Next RosBE release - recent status and what will come next. 2. Gallium3D poor performance - what to do. 3. CIA.vc replacement. Point 0Aleksey Bragin summarized the work done since the last meeting, including setting up an LDAP mirror that Jira could use to authenticate against.</description> </item> <item> <title>Contract Awarded to Mike Nordell</title> <link>https://reactos.org/project-news/contract-awarded-mike-nordell/</link> <pubDate>Wed, 12 Sep 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/contract-awarded-mike-nordell/</guid> <description>The ReactOS Project is delighted to announce another development contract funded by community donations. Mike Nordell was a previous ReactOS developer that went on sabbatical but continued to drop in to check on the project from time to time. As such, he has considerable experience developing ReactOS and extensive knowledge about the Windows NT architecture. As many people are aware of, ReactOS has a large test suite that checks to see whether specific functionality is working or not.</description> </item> <item> <title>New Developer Contract</title> <link>https://reactos.org/project-news/new-developer-contract/</link> <pubDate>Fri, 07 Sep 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-developer-contract/</guid> <description>The ReactOS Project is pleased to announce a new development contract with James Tabor, a long time ReactOS developer that has worked extensively on the Win32 subsystem. Jim intends to tackle many of the longstanding bugs and hopefully significantly reduce the number of outstanding issues in the Win32 subsystem. This particular contract will have a heavy emphasis on bugfixing instead of attempting to introduce new features.Time: 120 hours</description> </item> <item> <title>Contract Extension</title> <link>https://reactos.org/project-news/contract-extension/</link> <pubDate>Wed, 05 Sep 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/contract-extension/</guid> <description>The ReactOS Project is happy to announce an extension to Edijs Kolesnikovics's contract for developing application tests using AutoHotkey. Amine Khaldi, the supervisor for the previous contract, was very satisfied with Edijs' work and moved that an extension be made to give Edijs more time to develop additional tests. The first contract saw tests for installing applications and the exercising of some very basic functionality, as well as some improvements to the testing framework.</description> </item> <item> <title>August 2012 Meeting Minutes</title> <link>https://reactos.org/project-news/august-2012-meeting-minutes/</link> <pubDate>Mon, 03 Sep 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/august-2012-meeting-minutes/</guid> <description>2012-08-3019:00 UTCdev.reactos.org, #meetingProceedings Meeting started at 19:13 by Aleksey Bragin Point 0: Website status Point 1: ROS Testing and Bugs Point 2: Developer Contracts Point 3: State of Trunk and Release Feasibility Point 0Ziliang Guo had earlier reported that Atlassian's documentation was misleading with respect to Jira integration and did not actually permit what the team was trying to achieve. This was only discovered after Ziliang submitted a support request to Atlassian.</description> </item> <item> <title>Contract and Donation</title> <link>https://reactos.org/project-news/contract-and-donation/</link> <pubDate>Mon, 03 Sep 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/contract-and-donation/</guid> <description>Contract 1 Summary Report The contract issued to Edijs Kolesnikovics has now concluded and the following is a summary of the work completed.Installation tests were created for all applications part of the Golden Apps list. One additional test was also created for each to at least attempt to run the application after installation, with some exercising simple functionality. These tests were verified to work on Windows before integration into the ReactOS test suite.</description> </item> <item> <title>July 2012 Meeting B Minutes</title> <link>https://reactos.org/project-news/july-2012-meeting-b-minutes/</link> <pubDate>Tue, 07 Aug 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2012-meeting-b-minutes/</guid> <description>2012-07-2619:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:09 by Aleksey Bragin Point 1: Website Update Point 2: Technical Questions by Newer Team Members &nbsp;Point 1 Danny Gotte noted that he was still having trouble with the Java code to plug into the Atlassian web applications. Ziliang Guo had stated that he could help, as he had Java development experience, but both he and Danny had exams this week and so did not have time to do any actual work.</description> </item> <item> <title>ReactOS Presented to President Putin</title> <link>https://reactos.org/project-news/reactos-presented-president-putin/</link> <pubDate>Mon, 06 Aug 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-presented-president-putin/</guid> <description>The ReactOS Project once again had a presence at the Seliger Youth Forum held at Lake Seliger in Russia, with Marat Karatov and Alexander Rechitskiy representing the project. ReactOS ranked third overall of all projects presented at the Forum, but after Alexander and Marat had already left after having completed the presentation, the project was informed that the Forum wished to present the top projects to President Vladimir Putin. This caused some complications as Aleksey Bragin, the project coordinator, had been on vacation and could not make it back before the security lockdown.</description> </item> <item> <title>First Developer Contract Issued</title> <link>https://reactos.org/project-news/first-developer-contract-issued/</link> <pubDate>Tue, 31 Jul 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/first-developer-contract-issued/</guid> <description>The ReactOS Project is proud to announce the first of the development&nbsp;contracts that will be funded by the recent donation campaign. Edijs&nbsp;Kolesnikovics joined the ReactOS development team very recently and&nbsp;has been working extensively with Amine Khaldi and Olaf Siejka to&nbsp;create an application test suite based around the AutoHotkey (AHK)&nbsp;automation system. AutoHotkey is a tool for scripting keyboard and&nbsp;mouse actions in order to automate running of programs on Windows.&nbsp;While the current test suites exercise a considerable amount of&nbsp;functionality, the true test for ReactOS remains when it is used to&nbsp;run applications.</description> </item> <item> <title>July Meeting A Minutes</title> <link>https://reactos.org/project-news/july-2012-meeting-a-minutes/</link> <pubDate>Tue, 10 Jul 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/july-2012-meeting-a-minutes/</guid> <description>July 2012 Meeting A Minutes 2012-07-0519:00 UTCdev.reactos.org, #meetingProceedingsMeeting started at 19:16 UTC by Aleksey Bragin.&nbsp; Point 0: CD/Product Store Point 1: Update/Team Plan Point 2: Website Update Point 3: Internet Declaration Due to scheduling constraints by some participants, the question of a team store and sale of ReactOS CDs was moved to be the first topic. Point 0 Ziliang Guo presented the question of CD sales and merchendise sales in general.</description> </item> <item> <title>IPv6 Launch Day</title> <link>https://reactos.org/project-news/ipv6-launch-day/</link> <pubDate>Wed, 06 Jun 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/ipv6-launch-day/</guid> <description>The foundation of the internet are IP addresses, which tell people how to reach websites and machines across the world. The current iteration, IPv4, is 32bits in size and the world is quickly running out of available addresses. As such, there has been a steady march towards IPv6, which uses 128bits for addresses. This march has however been slow due to the massive existing infrastructure that uses IPv4. To try and help get more organizations IPv6 ready, the Internet Society set up IPv6 Launch Day, intended to be a day where participating organizations permanently turn on access over IPv6 to their services.</description> </item> <item> <title>May 2012 Development Team Meeting</title> <link>https://reactos.org/project-news/may-2012-development-team-meeting/</link> <pubDate>Sun, 03 Jun 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/may-2012-development-team-meeting/</guid> <description>2012-05-31 19:00 UTC dev.reactos.org, #meetingProceedingsMeeting started at 19:08 UTC by Aleksey Bragin.Point 1: Website Revamp Danny Goette explained that about a month ago he started a new approach for the website revamp, based on the typo3 cms, with a theme based on the current website, a working forum (a mm_forum extension for typo3) that has all the data of our current phpbb forum, along with current user accounts imported from roscms.</description> </item> <item> <title>Newsletter 92</title> <link>https://reactos.org/blogs/newsletter-92/</link> <pubDate>Mon, 21 May 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-92/</guid> <description>Win32 Improvements Deep within GDI is code designed to carry out a series of raster operations that involve applying patterns to bitmaps. For performance reasons, it is desirable to have optimized versions of this code for the various bit depths. Formally, ReactOS only generated these optimized versions for the few ternary raster operations that were used often enough to be given a common name by Microsoft. The rest were handled in a single unoptimized version.</description> </item> <item> <title>ReactOS Fundraiser 2012</title> <link>https://reactos.org/project-news/reactos-fundraiser-2012/</link> <pubDate>Sat, 28 Apr 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-fundraiser-2012/</guid> <description>The ReactOS Project has engaged in several fundraising efforts in the past, and thanks to their success and non-monetary donations, an industry-grade infrastructure was developed and deployed, and is being continuously improved.Donations have also helped developers travel to several conferences and events to promote and present ReactOS. These presentations were crucial in drawing attention to the project and often helped spur further donations.This year we want to do something different, something even grander.</description> </item> <item> <title>Newsletter 91</title> <link>https://reactos.org/blogs/newsletter-91/</link> <pubDate>Wed, 29 Feb 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-91/</guid> <description>Session Manager Subsystem Rewrite The session manager subsystem is responsible for initializing much of the operating system environment and starting up services and processes needed to get a user to the login screen. Specifically, it creates the environment variables inherited by other processes, loads the Win32 subsystem, sets up the pagefiles for virtual memory, and finally starts up the winlogon.exe process, amongst other things. The implementation that was in ReactOS took many shortcuts in how it communicated with subsystem components, which in turn led to those components not correctly implementing the interfaces SMSS was supposed to use.</description> </item> <item> <title>SourceForge Featured Project</title> <link>https://reactos.org/project-news/sourceforge-featured-project/</link> <pubDate>Wed, 29 Feb 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/sourceforge-featured-project/</guid> <description>The ReactOS Project is proud to have been selected as a SourceForge.net Featured Project for the month of February. While ReactOS maintains much of the development infrastructure internally now, SourceForge remains the host for all of our releases and helps provide another web presence for the project. Based on the stats, getting bumped to SourceForge's front page has drawn a fair amount of attention to the project.</description> </item> <item> <title>USB Help From Haiku</title> <link>https://reactos.org/project-news/usb-help-haiku/</link> <pubDate>Tue, 21 Feb 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/usb-help-haiku/</guid> <description>The ReactOS and Haiku projects have had a friendly working relationship for several years now, with each group helping the other whenever possible. These range from helping each other with conference attendance at SCALE and FOSDEM to development related matters. Haiku was especially helpful during ReactOS' successful application to Google Summer of Code 2011, providing advice and feedback on ReactOS' application efforts, and the ReactOS project remains grateful for the assistance.</description> </item> <item> <title>ReactOS 0.3.14 Released</title> <link>https://reactos.org/project-news/reactos-0314-released/</link> <pubDate>Wed, 08 Feb 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0314-released/</guid> <description>The ReactOS team is proud to announce the release of ReactOS 0.3.14. This version includes a significant amount of changes including both user visible and architectural improvements. Also included in this release is the valuable work accomplished as part of the Google Summer of Code 2011 event, of which ReactOS was a mentoring project. One of the more significant sets of improvements was to ReactOS’ networking stack. As part of the GSoC, ReactOS gained a new TCP/IP driver built around the LwIP project.</description> </item> <item> <title>ISIMA Partnership</title> <link>https://reactos.org/project-news/isima-partnership/</link> <pubDate>Wed, 01 Feb 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/isima-partnership/</guid> <description>ReactOS developer and IT administrator Pierre Schweitzer is currently a student at Institut Supérieur d&#39;Informatique, de Modélisation et de leurs Applications (ISIMA) and had worked over the last few months to establish a formal partnership between the ReactOS project and ISIMA. After a formal presentation to ISIMA&#39;s directors on January 11th, 2012, this partnership was approved. The ReactOS project will in the future be allowed to present projects that ISIMA students can complete as part of their coursework.</description> </item> <item> <title>Newsletter 90</title> <link>https://reactos.org/blogs/newsletter-90/</link> <pubDate>Tue, 24 Jan 2012 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-90/</guid> <description>Wireless Cameron Gutman has spent the last month or so adding the pieces needed to support wireless network cards to ReactOS. A good portion of the work entailed writing the NDIS protocol driver (ndisuio) that handles sending wireless NDIS object identifier (OID) messages. These messages handle querying network drivers about their status and capabilities and also set the receiving mode the device should operate in. In addition to the kernel side, a user mode utility is needed to let end users actually make these requests.</description> </item> <item> <title>Newsletter 89</title> <link>https://reactos.org/blogs/newsletter-89/</link> <pubDate>Thu, 15 Dec 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-89/</guid> <description>RPC Remote procedure calls underline a lot of things in Windows, especially services. Thus the Remote Procedure Call Runtime (rpcrt4) library is fairly important to the continued operation and stability of ReactOS. It is also a component in which the project is heavily reliant on Wine for. Unfortunately, just because Wine code works on Linux does not mean it will work on ReactOS, and attempts to sync rpcrt4 in the past have produced monumental headaches, breakages, and difficulties in ReactOS.</description> </item> <item> <title>ING-DiBa Foundation Sponsorship</title> <link>https://reactos.org/project-news/ing-diba-foundation-sponsorship/</link> <pubDate>Sun, 23 Oct 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/ing-diba-foundation-sponsorship/</guid> <description>The German ING-DiBa AG bank is running a competition which people have until November 15th to vote on which foundation they support. The top 1000 foundations will receive a 1000€ donation from the bank. At the time of writing the ReactOS Foundation is sitting at 9th place, but three weeks is a long time for other projects to catch up and perhaps even bump ReactOS from the top 1000. Instructions for how to vote are located here and requires only an email.</description> </item> <item> <title>Newsletter 88</title> <link>https://reactos.org/blogs/newsletter-88/</link> <pubDate>Thu, 13 Oct 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-88/</guid> <description>Shell32 Another recent accomplishment by Claudiu Mihail, the Google Summer of Code responsible for transforming the lwIP library into a driver, was the completion and remerging of the shell32 library as C++ code instead of C code. The effort was started originally by Ged Murphy and Andrew Hill as C++ was better suited to implementing the COM aspects of the library. Ged had originally tried to do the conversion in trunk, but that proved too disruptive and he moved the code into a branch.</description> </item> <item> <title>ReactOS Demonstrated to the Russian President Dmitry Medvedev</title> <link>https://reactos.org/project-news/reactos-demonstrated-russian-president-dmitry-medvedev/</link> <pubDate>Mon, 12 Sep 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-demonstrated-russian-president-dmitry-medvedev/</guid> <description>ReactOS Demonstrated to the Russian President Dmitry Medvedev The ReactOS project participated in the Seliger 2011 Forum this summer. "Seliger" is an annual youth educational forum held since 2005 at Lake Seliger in Russia, close to the city of Ostashkov in the Tver region (370km away from Moscow). The forum is funded by the Russian government with a budget of approximately 178 million rubles (approximately 5.9 million dollars or 4.</description> </item> <item> <title>Newsletter 87</title> <link>https://reactos.org/blogs/newsletter-87/</link> <pubDate>Tue, 30 Aug 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-87/</guid> <description>Google Summer of Code Progress Of the six projects ReactOS entered as part of the Google Summer of Code, four are well on track to completion. Each of the completed projects will greatly help increase ReactOS' usability and provide a foundation for future enhancement. Many of the successful projects will help make ReactOS more usable from both a stability and UI perspective. The deadline for final submissions is already over and the project and Google are currently evaluating students.</description> </item> <item> <title>Newsletter 86</title> <link>https://reactos.org/blogs/newsletter-86/</link> <pubDate>Tue, 26 Jul 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-86/</guid> <description>MSVC Progress The entirety of ReactOS can now be built using Microsoft's compiler, but running the resulting operating system is still a ways off. &nbsp;Timo Kreuzer has already squashed several bugs that arose, one such being corruption of filesystem metadata that caused the loading of freeldr to fail. On x86/x64 platforms, part of the booting process involves the bootsector loading in the FAT table from disk, which needs to be loaded in a high enough address that reading freeldr into memory afterward would not overwrite the table.</description> </item> <item> <title>Newsletter 85</title> <link>https://reactos.org/blogs/newsletter-85/</link> <pubDate>Mon, 20 Jun 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-85/</guid> <description>Theme Support Giannis has completed support for drawing in most non-client areas of a window such as captions, borders, and scrollbars. Scrollbars turned out to be especially problematic as the code that handles calculations of how much to scroll is also responsible for redrawing the changes. This has the very unfortunate consequence of duplicating a significant amount of drawing code inside the scrolling update function. Maintenance of this code will likely be troublesome due to this, but currently Giannis is not aware of a way around the problem.</description> </item> <item> <title>Newsletter 84</title> <link>https://reactos.org/blogs/newsletter-84/</link> <pubDate>Sun, 15 May 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-84/</guid> <description>Loader Rewrite When an application has external dependencies that are in DLLs, a loader is responsible for loading and initializing them. The implementation in ReactOS is very, very old and like many such instances of ancient code incorrect. It worked after a fashion but took many shortcuts. There are matters such as initialization of the Thread Local Storage, calling the DllMain of a specific DLL, and loading of DLLs in the correct order based on interdependencies or even circular dependencies.</description> </item> <item> <title>Newsletter 83</title> <link>https://reactos.org/blogs/newsletter-83/</link> <pubDate>Fri, 29 Apr 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-83/</guid> <description>GDI Memory Usage As part of his work rewriting the Graphics Device Interface (GDI) handle manager, Timo Kreuzer ran across what can only be described as an atrocious waste of memory. The memory allocation granularity for when objects were created was an entire page, 4KB, regardless of whether an object needed that much space to store its attributes. This thus wastes a considerable amount of memory and also eats up memory addresses.</description> </item> <item> <title>Accepted Summer of Code Projects</title> <link>https://reactos.org/project-news/accepted-summer-code-projects/</link> <pubDate>Tue, 26 Apr 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/accepted-summer-code-projects/</guid> <description>The ReactOS project has accepted six entries from the submitted projects, covering a wide range of functionality. The completion of some would have immediate, user visible effects on ReactOS, while others are more long term.TCP/IP Driver Rewrite of the current TCP/IP stack using the lwIP library. Student: Claudiu Mihail Mentor: Art Yerkes Completion of Explorer_New Complete the implementation of a new explorer shell for ReactOS. Student: Andrew Green Mentor: Aleksey Bragin Theme Support Implement the theme service for the user interface.</description> </item> <item> <title>Newsletter 82</title> <link>https://reactos.org/blogs/newsletter-82/</link> <pubDate>Sat, 09 Apr 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-82/</guid> <description>NewCC Status A while back Art Yerkes merged in a significant part of his new common cache implementation into trunk. This merge was intended to lay the foundation for the eventual replacement of the current common cache, which will happen once Art clears up some inconsistencies in how the sections data structure is treated by the memory manager and the common cache. Sections management is the responsibility of the memory manager but provide functionality the common cache relies on.</description> </item> <item> <title>ReactOS 0.3.13 Released</title> <link>https://reactos.org/project-news/reactos-0313-released/</link> <pubDate>Tue, 22 Mar 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0313-released/</guid> <description>The ReactOS team is proud to announce the release of ReactOS 0.3.13. This version continues building on the work first previewed in 0.3.12, ranging from memory management improvements to better sound and display control. A Coverity scan also occurred between 0.3.12 and 0.3.13, helping the team clean up potential security holes and also help improve general stability by enforcing more care in memory operations.Some of the biggest system changes happened with memory management with the introduction of a new heap manager based on the Windows 2003/Vista architecture, significantly increasing ReactOS’ compatibility with advanced memory allocation types and providing proper kernel mode heap management used by win32k.</description> </item> <item> <title>Google Summer of Code 2011</title> <link>https://reactos.org/project-news/google-summer-code-2011/</link> <pubDate>Sun, 20 Mar 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/google-summer-code-2011/</guid> <description>We are proud to announce that ReactOS has been accepted into the 2011 Google Summer of Code program. It has been a few years since we were last a part of the program, so we are keen to use this opportunity not only to benefit ReactOS in hopefully gaining new features, but in passing on our knowledge to bright and prospective students with an interest in operating system development and especially Windows internals.</description> </item> <item> <title>Newsletter 81</title> <link>https://reactos.org/blogs/newsletter-81/</link> <pubDate>Mon, 14 Mar 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-81/</guid> <description>C++ Mangling Those with any experience using third party libraries while writing C++ applications should quickly recognize the topic I am about to go over and can skip down to paragraph three for the ReactOS specific miseries. Those that are not familiar with the issues or want a refresher should continue. The C++ standard outlines behavior for C++ code when compiled. To be considered a compliant compiler requires following the specifications laid out, though no compiler that I am aware of actually implements 100% of the entire standard.</description> </item> <item> <title>Newsletter 80</title> <link>https://reactos.org/blogs/newsletter-80/</link> <pubDate>Thu, 03 Feb 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-80/</guid> <description>Component Testing As more components relating to filesystems sees implementation in ReactOS, they need to be tested. Pierre Schweitzer decided to try using Microsoft's FASTFAT driver to help in the effort, as using it successfully in ReactOS would indicate development is on the right track. Unfortunately, ReactOS' current common cache implementation effectively blocks that attempt due to its sorry state. The common cache has been touched upon in the past and mention was made of its problems.</description> </item> <item> <title>Donators page is back on track</title> <link>https://reactos.org/project-news/donators-page-back-track/</link> <pubDate>Sat, 08 Jan 2011 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/donators-page-back-track/</guid> <description>Donators page is back on track As of today, the Donators page which lists all monetary donations to the project is back on track.The long outage originated from the fact that all donations are handled by the German non-profit organization ReactOS Deutschland e.V. as of 2010. This change has required a new software for creating the donation list, which has needed some time to mature.Gladly, this long development time has paid off and updating the donation list is now just a matter of a few clicks.</description> </item> <item> <title>Newsletter 79</title> <link>https://reactos.org/blogs/newsletter-79/</link> <pubDate>Sat, 25 Dec 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-79/</guid> <description>The ReactOS team would like to wish everyone a merry Christmas and a happy New Year.Coverity Redux The ReactOS team recently ran another Coverity scan on the source code. While a few new issues were discovered thanks to enhancements to Coverity's analysis program, the vast majority of issues fell into two categories; false positives due to the way the Portable Structured Exception Handling (PSEH) library is implemented and used, and warnings from third party code not developed by this project.</description> </item> <item> <title>Newsletter 78</title> <link>https://reactos.org/blogs/newsletter-78/</link> <pubDate>Tue, 23 Nov 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-78/</guid> <description>Sound Stack The sound stack on Windows has a fairly clearcut layout, but the explanation provided in issue 65 of the newsletter was very brief and likely confusing so a more complete explanation follows. The sound card on a computer deals with two types of lines, source and destination. Source lines are effectively inputs from various things like the CD-ROM, microphone, or the like. Destination lines are ouputs from the card to speakers, headphones, and such.</description> </item> <item> <title>Newsletter 77</title> <link>https://reactos.org/blogs/newsletter-77/</link> <pubDate>Wed, 27 Oct 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-77/</guid> <description>0.3.12 As one can see from the front page, 0.3.12 has been released into the wild. In many ways 0.3.12 provides more a transitional view of ReactOS development than presenting loads and loads of new features or functionality. The 10 months between it and 0.3.11 provided a long window in which developers could drop in new features. Unfortunately many of them promised to be extremely disruptive and the decision was made to disable the full functionality of several before shipping.</description> </item> <item> <title>ReactOS 0.3.12 Released</title> <link>https://reactos.org/project-news/reactos-0312-released/</link> <pubDate>Wed, 20 Oct 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0312-released/</guid> <description>The ReactOS team is proud to announce the release of ReactOS 0.3.12. This is a huge release for the team, not just with regards to the number of improvements which this release holds but in terms of the leap forward architecturally, stability wise and in bringing some of the more modern aspects of the NT kernel into ReactOS. It's been almost a year since the last release and whilst this is understandably excessive, it was required to stabilize the OS due to the nature of the work which was undertaken.</description> </item> <item> <title>Newsletter 76</title> <link>https://reactos.org/blogs/newsletter-76/</link> <pubDate>Wed, 08 Sep 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-76/</guid> <description>Hunting Dangling Pointers There has always been a suspicion and concern amongst the ReactOS developers that there are points of sloppiness in ReactOS with respect to memory management. These can be fairly innocuous when at the user mode level, but in kernel mode can lead to data corruption and other problems. Cameron Gutman, Timo Kreuzer, and Michael Martin have just managed to find and fix what was perhaps the most serious of these suspected leaks.</description> </item> <item> <title>Newsletter 75</title> <link>https://reactos.org/blogs/newsletter-75/</link> <pubDate>Sat, 07 Aug 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-75/</guid> <description>Starcraft 2 came out. Enough said.Bitmap Drawing Bitmaps are more or less the primary medium through which the Win32 subsystem draws things. However, the term refers to more than just the widely used format for images and the like. That format is generally considered a device independent bitmap (DIB). With a device independent version there of course exists a device dependent one, which is the format that a particular graphics device supports for drawing.</description> </item> <item> <title>Newsletter 74</title> <link>https://reactos.org/blogs/newsletter-74/</link> <pubDate>Fri, 09 Jul 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-74/</guid> <description>General Developments Amine Khaldi's effort in getting the driver headers cleaned up is starting to show results. Not only are a good portion of the driver headers sorted out, the necessary checks have been added to allow the headers to be used in both MSVC and GCC. Anyone who has had to write cross platform code will know that the two compilers have subtle differences at times in their allowed syntax so producing code that works with both can get nontrivial quickly.</description> </item> <item> <title>Newsletter 73</title> <link>https://reactos.org/blogs/newsletter-73/</link> <pubDate>Wed, 23 Jun 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-73/</guid> <description>A word of advice to everyone, traveling through six different cities in the span of two weeks requires a careful balance between changes of clothes brought and lightness of luggage, though a willingness to hand wash will also go a long way.Timers and Messages Several years back when I first joined the ReactOS team as a release engineer, which I technically still am, the team ran into an odd bug where when downloading something in Firefox they needed to move the mouse to see any progress.</description> </item> <item> <title>Newsletter 72</title> <link>https://reactos.org/blogs/newsletter-72/</link> <pubDate>Sat, 15 May 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-72/</guid> <description>Just a heads up, I'm out of the country for the next two months and will have unreliable net access, so do not expect any newsletters until late July.General Developments A few weeks back Aleksey Bragin directed the developers to take a look at a long list of regressions that had accumulated. Individually the problems were for the most part minor, though a few were near show stoppers. However, cumulatively they represented a major perception problem in ReactOS' progress.</description> </item> <item> <title>Newsletter 71</title> <link>https://reactos.org/blogs/newsletter-71/</link> <pubDate>Fri, 23 Apr 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-71/</guid> <description>NT USB Stack Pre-Vista, the USB architecture started with a very low level usbport driver. This driver was the one that created device objects for each USB controller and received I/O Request Packets (IRP). Depending on which USB standard the controllers were for, usbport would call into one of three helper drivers, usbehci, usbohci, and usbuhci. The one actually sending those IRPs was usbhub, and these components constitute the lower levels of the USB stack.</description> </item> <item> <title>Newsletter 70</title> <link>https://reactos.org/blogs/newsletter-70/</link> <pubDate>Thu, 01 Apr 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-70/</guid> <description>UniATA Timing UniATA continues to be problematic, with testers often struggling to get past the first stage install much less actually put ReactOS through its paces. As mentioned before, the time UniATA waits for responses from hardware is considerably lower than that of the old ATA driver. On older hardware, sometimes various drives are not fast enough in responding so operations time out and UniATA reports an error even when there technically was nothing wrong.</description> </item> <item> <title>Back from CLT 2010</title> <link>https://reactos.org/project-news/back-clt-2010/</link> <pubDate>Mon, 15 Mar 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/back-clt-2010/</guid> <description>The Chemnitz Linux-Days 2010 are over and all ReactOS developers have safely made their way home again.We would like to give a summary, and share our impressions with those who were unfortunately unable join us:Contrary to our expectations, the stall and the presentation were a wow. Especially for ReactOS Deutschland e.V., the new German non-profit organization supporting the project, it was a promising start. A lot of interested guests visited our stall and wished us success for the future.</description> </item> <item> <title>Chemnitz Linux Day</title> <link>https://reactos.org/project-news/chemnitz-linux-day/</link> <pubDate>Thu, 04 Mar 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/chemnitz-linux-day/</guid> <description>Several German members of the ReactOS development team and Aleksey Bragin, the project coordinator, will be attending the Chemnitz Linux Day, an expo for open source technologies running from March 13 to 14. Besides the team manning a table, Matthias Kupfer will be holding a talk outlining the architecture of ReactOS as well as achieved and future objectives on Sunday, March 14 at 16:30, so be sure to drop by.</description> </item> <item> <title>Newsletter 69</title> <link>https://reactos.org/blogs/newsletter-69/</link> <pubDate>Wed, 03 Mar 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-69/</guid> <description>Trap Handling One of the ways low level communication with hardware is handled is with interrupts and exceptions. Code still has to be written to deal with these and that code is in the trap handler. The original trap handler code in ReactOS was pure assembly, which to an extent is inevitable due to the very needing to carry out operations that the C language does not specify a method for.</description> </item> <item> <title>Newsletter 68</title> <link>https://reactos.org/blogs/newsletter-68/</link> <pubDate>Fri, 22 Jan 2010 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-68/</guid> <description>ARWINSS, Third Time's the Charm, Maybe There has been increasing speculation on what ARWINSS is, on what it is for, and on what it does, despite several statements released by Aleksey Bragin. The speculation has reached the point where people with incomplete information are making assertions as if they were fact when often their assertions are incorrect. ARWINSS is not intended to 'replace' the current Win32 subsystem. It exists as a parallel effort to overcome the limitations in the current Win32 subsystem by applying a different design instead of duplicating the one in Windows NT.</description> </item> <item> <title>ReactOS 0.3.11 Released</title> <link>https://reactos.org/project-news/reactos-0311-released/</link> <pubDate>Wed, 16 Dec 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0311-released/</guid> <description>ReactOS 0.3.11 Released The ReactOS team is proud to announce the release of ReactOS 0.3.11. This release has been delayed by quite some time due to various blocker bugs which manifested each time we tried to release. A lot of time has gone into hunting down these bugs and various steps have been taken to try to ensure we don't hit this problem again. This isn't to say we don't have a lot of new and exciting features in this release.</description> </item> <item> <title>Newsletter 67</title> <link>https://reactos.org/blogs/newsletter-67/</link> <pubDate>Thu, 12 Nov 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-67/</guid> <description>Debugging The last time WinDBG support was discussed up was nearly a year ago. The first step needed was a kernel compatible with WinDBG, which was achieved by the kernel rewrite that mostly concluded two years ago. The required features mostly revolved around dealing with an executing thread's context and reading virtual memory. While the kernel rewrite made these possible, a few bugs prevented their usage. Debugging requires interrupting the executing thread's flow but also restoring it to allow the program to continue.</description> </item> <item> <title>Newsletter 66</title> <link>https://reactos.org/blogs/newsletter-66/</link> <pubDate>Sat, 31 Oct 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-66/</guid> <description>FAT A short while ago the FullFAT library was mentioned on the ReactOS forum and then brought to the attention of the developers by IRC regulars. Written by James Walmsley, it is a platform independent library for accessing FAT12/16/32 partitions and it was suggested that a new IFS driver could be written using it. The current FAT driver was written against an older, less NT compliant kernel and was never extensively tested on Windows to begin with.</description> </item> <item> <title>Newsletter 65</title> <link>https://reactos.org/blogs/newsletter-65/</link> <pubDate>Sun, 11 Oct 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-65/</guid> <description>Disks and Partitions One of the non-cross platform aspects of ReactOS was in how the bootloader dealt with disks and partitions. The naming scheme used was very x86 centric and also was limited in which partitions it could access. Herv&eacute; Poussineau started working on a new API to remove the limitations, one based on names instead of drive numbers. Previously on platforms like PPC and ARM, developers would have needed to give numbers to each storage device they wanted to use.</description> </item> <item> <title>Newsletter 64</title> <link>https://reactos.org/blogs/newsletter-64/</link> <pubDate>Wed, 16 Sep 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-64/</guid> <description>Color and Filling Colored cursors aren't a feature used that often by regular applications, but games certainly make use of it and Winamp is a non-game example. When using Winamp, Gregor Schneider noticed the mouse turned into a black box when he tried to use it and dug into the code to see if he could fix it. In several places were comments noting the need for color support so Gregor had a few hints about where additional code was needed.</description> </item> <item> <title>Website Design Contest</title> <link>https://reactos.org/project-news/website-design-contest/</link> <pubDate>Tue, 04 Aug 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/website-design-contest/</guid> <description>The task is to create a mockup for a new homepage and menu layout. We want a fresh layout, as the current one is starting to show its age. color scheme should be compatible with the ReactOS logo and the logo included into the design. it should contain a diagram for a simplified frontpage it should also integrate stylistically with the forum, wiki & bugzilla it should render consistently across IE7+, FF2+, Opera 9+, Safari 3+ and without javascript or other browser plugins, though javascript and DOM may be used for optional effects whose absence will not adversely degrade the usability of the site there is no guarantee that your proposal will not be modified if selected any submission must be of an original work by the submitter/submitters (you are free to use the ReactOS logo for the proposal) submitters grants the ReactOS Foundation a royalty-free license to use and/or modify their respective designs, though all submitters retain the rights to their work The best submission will be selected by a jury of five (Aleksey Bragin, Colin Finck, Danny Götte, Ged Murphy and Ziliang Guo).</description> </item> <item> <title>Newsletter 63</title> <link>https://reactos.org/blogs/newsletter-63/</link> <pubDate>Sat, 01 Aug 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-63/</guid> <description>Test Disruptions For several days the automated testing suite that runs every ReactOS revision got stuck in an infinite loop once it reached the msi_winetest. Several people following the testing noticed this issue and suggested possible causes but Jeffrey Morlan eventually committed a patch that seems to resolve it. The problem appeared to be in the LoadLibraryExW function, in a specific case where the LOAD_LIBRARY_AS_DATAFILE flag was set. The function received as one of its inputs DllName, the name of the library it was being asked to load.</description> </item> <item> <title>Newsletter 62</title> <link>https://reactos.org/blogs/newsletter-62/</link> <pubDate>Tue, 21 Jul 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-62/</guid> <description>PSEH Corruption In NT operating systems, structured exception handling is used to help safeguard probing of user mode memory buffers and pageable memory while in kernel mode. This requirement was what motivated the creation of the PSEH library by KJK::Hyperion since GCC does not have support for it. Since the last attempt to add SEH support to GCC failed, ReactOS remains dependent on PSEH. Recently, the ARM team committed some code which exposed a very nasty bug in the PSEH library and investigation of the issue led KJK to discover another bug while analyzing the code.</description> </item> <item> <title>ReactOS 0.3.10 Released</title> <link>https://reactos.org/project-news/reactos-0310-released/</link> <pubDate>Sun, 05 Jul 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-0310-released/</guid> <description>ReactOS 0.3.10 Released The ReactOS team is proud to announce the release of ReactOS 0.3.10. This version is the first to use the Universal ATA driver as the default disk driver, adding support for Serial ATA and partitions greater than 8GB. In addition, recent work was done on the USB stack to increase compatibility with USB keyboards and mice. These features are still under heavy development and have several known bugs, but their inclusion should allow more people to run ReactOS on real hardware and are part of the extensive work to make ReactOS usable as an every day operating system.</description> </item> <item> <title>Newsletter 61</title> <link>https://reactos.org/blogs/newsletter-61/</link> <pubDate>Tue, 30 Jun 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-61/</guid> <description>0.3.10 Preparations Effort is underway to get the 0.3.10 release out the door. Testers have been going through the usual list of applications to find any regressions and several have popped up. An especially nasty one was a seemingly random data corruption in the Download application, eventually traced back to an update in wininet from Wine. As the developers were unable to pinpoint the exact cause, Cameron Gutman simply reverted the entire code synchronization.</description> </item> <item> <title>Sourceforge Community Choice Awards</title> <link>https://reactos.org/project-news/sourceforge-community-choice-awards/</link> <pubDate>Thu, 25 Jun 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/sourceforge-community-choice-awards/</guid> <description>The ReactOS project is once again taking part in the Sourceforge Community Choice Awards and we have made it into the final round of voting. ReactOS is currently in three categories, Best Project, Best Project for Government, and Most Likely to Change the Way You Do Everything. We ask all of our supporters to please vote for us by following this link and to help spread the word. There's no money involved, but the publicity would certainly help the project gain more exposure.</description> </item> <item> <title>Newsletter 60</title> <link>https://reactos.org/blogs/newsletter-60/</link> <pubDate>Fri, 12 Jun 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-60/</guid> <description>RBuild and MSVC Getting ReactOS built using Microsoft&#39;s compilers has been on the wishlist of several ReactOS developers, but no one really wanted to deal with the monstrosity that RBuild had transformed into. KJK::Hyperion decided his sanity was sufficient enough to survive the experience and has been working for quite some time to get it to be able to use a compiler that is not GCC. So far, his additions allow RBuild to detect the presence of the VC++ compiler, whether you got it through Visual Studio, one of the SDKs, or the WDK.</description> </item> <item> <title>Newsletter 59</title> <link>https://reactos.org/blogs/newsletter-59/</link> <pubDate>Thu, 04 Jun 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-59/</guid> <description>ReactOS Foundation The ReactOS Foundation is the entity that handles the legal affairs of the project and owns the trademarks and logos associated with the ReactOS Project. The Foundation itself has been established for a few years now and is based in Moscow, but two recent developments have helped increase its legitimacy in a broader perspective. The first was the approval of ReactOS as a registered trademark owned by the Foundation in Russia.</description> </item> <item> <title>Newsletter 58</title> <link>https://reactos.org/blogs/newsletter-58/</link> <pubDate>Sat, 16 May 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-58/</guid> <description>UniATA The Universal ATA driver has often been pointed out as a way to solve some rather annoying issues in ReactOS, such as the lack of support for SATA and limiting the amount of space ROS sees to about 8GB. Since both issues border on the outright absurd in this day and age, fixing them was of very high priority. A few showstoppers stood in the way however of switching over permanently and Aleksey Bragin has managed to resolve some of them.</description> </item> <item> <title>Newsletter 57</title> <link>https://reactos.org/blogs/newsletter-57/</link> <pubDate>Thu, 30 Apr 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-57/</guid> <description>VBox Video Driver A while back the VBox video driver started working in ReactOS, which meant people using VirtualBox could now get hardware acceleration for graphics. To make the driver usable, Timo Kreuzer fixed two things in the Win32 subsystem. While the driver ran before the fixes, its functionality was somewhat crippled and drawing often resulted in problems. The first fix was for the mouse pointer, or more specifically drawing the mouse pointer moving across the screen.</description> </item> <item> <title>ReactOS 0.3.9 Released</title> <link>https://reactos.org/project-news/reactos-039-released/</link> <pubDate>Sun, 26 Apr 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-039-released/</guid> <description>ReactOS 0.3.9 Released Our development team is pleased to announce the 9th increment of the 0.3 series of ReactOS, an open source Windows® compatible operating system. As we draw ever closer to the 0.4 series, more and more work is being put into bugfixing existing code in an effort to get more applications and drivers working. This release is testament to that and is our most compatible release to date.</description> </item> <item> <title>Newsletter 56</title> <link>https://reactos.org/blogs/newsletter-56/</link> <pubDate>Thu, 09 Apr 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-56/</guid> <description>USB USB support has an odd history in ReactOS. The original effort involved porting the Cromwell USB stack from Linux, which Aleksey Bragin spent awhile trying to get working. This was eventually abandoned for another third party project, an USB stack developed for NT4 by a programmer in China. This stack however was incomplete and rather buggy and the original author no longer maintained it so Aleksey spent some time fixing it up, to an extent.</description> </item> <item> <title>Newsletter 55</title> <link>https://reactos.org/blogs/newsletter-55/</link> <pubDate>Mon, 16 Mar 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-55/</guid> <description>Font Engine There is a difference between functional correctness and implementation correctness, a distinction one always has to keep in mind when saying something works in ReactOS. In the case of text rendering, while the output may for the most part look correct, the underlying implementation is nothing like how it should be. The abbreviated function call chain for displaying text is TextOutA/W, NtGdiExtTextOutW, and GreExtTextOutW. There are a few variations but the above provides a general idea of the path down to the Gre function.</description> </item> <item> <title>Newsletter 54</title> <link>https://reactos.org/blogs/newsletter-54/</link> <pubDate>Wed, 04 Mar 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-54/</guid> <description>Memory Usage The minimum required memory for ReactOS has been creeping up for some time now, mainly due to the installer. In general, the developers knew that the memory required by ROS after the install was nowhere as high as during the install. Most assumed there was some kind of memory leakage happening, whether it be in the installer or even in the memory manager. It was an issue many people wanted addressed but it wasn&#39;t until Alex Ionescu took a look that the problem was resolved.</description> </item> <item> <title>FOSDEM Writeup</title> <link>https://reactos.org/project-news/fosdem-writeup/</link> <pubDate>Mon, 23 Feb 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/fosdem-writeup/</guid> <description>The following is a writeup by KJK::Hyperion detailing his experiences at FOSDEM. Since all the developers unilaterally agreed that it was a much more entertaining read, it now represents the project&#39;s writeup. Besides some minor spelling corrections, name corrections, and conclusion, it was all his, quirky grammar included. Enjoy. FRIDAY Left home at 3.30 AM. My pessimistic estimate is 10 hours total of travel from home (Milan, Italy) to hotel (Brussels, Belgium).</description> </item> <item> <title>Newsletter 53</title> <link>https://reactos.org/blogs/newsletter-53/</link> <pubDate>Mon, 16 Feb 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-53/</guid> <description>ReactOS 0.3.8 Version 0.3.8 was released on Feburary 4th. The developers actually did a rush job, trying to get it ready in time for Andrew Greenwood to burn all the CDs they would be taking to FOSDEM. 0.3.8 continues the emphasis on stability and usability, but ultimately the OS still has a long way to go before these goals are achieved. FOSDEM Several developers were present at the FOSDEM convention representing the project.</description> </item> <item> <title>ReactOS 0.3.8, FOSDEM 2009</title> <link>https://reactos.org/project-news/reactos-038-fosdem-2009/</link> <pubDate>Wed, 04 Feb 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-038-fosdem-2009/</guid> <description>ReactOS 0.3.8 Released Our development team is proud to present a new version of ReactOS, a Windows®-compatible operating system. It has been three months since the 0.3.7 release date. Much of the work has been done and only some minor changes remain in order to make the release cycle faster and less time consuming for developers and release engineers. Besides development of the operating system, a number of organizational and administrative changes were done to make the development process easier and more enjoyable.</description> </item> <item> <title>Newsletter 52</title> <link>https://reactos.org/blogs/newsletter-52/</link> <pubDate>Mon, 02 Feb 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-52/</guid> <description>More Win32 Work Timo Kreuzer continues his efforts to make the Win32 subsystem more correct, recently working on the functions SetWindowExtEx and SetViewpointExtEx. The first step was moving it out of win32k, where the operations were originally being carried out, and into gdi32, where they should be carried out. Jim Tabor had code in place which implemented them, but they needed some fixing. While not yet complete, Timo has corrected some of the errors.</description> </item> <item> <title>Year in Review</title> <link>https://reactos.org/project-news/year-review/</link> <pubDate>Sat, 17 Jan 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/year-review/</guid> <description>Year in Review 2008 saw a total of four point releases by the ReactOS project, all of which were made after the kernel rewrite was completed. Thus the instabilities people saw in the 0.3.1 release were greatly reduced and there were better rates of success in running ROS on real hardware and not just virtual machines. That is not to say the system runs reliably, but we have gotten closer.</description> </item> <item> <title>Newsletter 51</title> <link>https://reactos.org/blogs/newsletter-51/</link> <pubDate>Mon, 12 Jan 2009 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-51/</guid> <description>Drawing Bugs Two issues were recently fixed that caused some problems in Firefox 2. The first was the page loaded would wash out after about 60 seconds of inactivity. The problem was in NtGdiGetDIBitsInternal, where the function was using the device context's palette instead of the bitmap's. The second problem involves the logos and images on Firefox's Google homepage being blacked out or completely missing entirely. This problem is slightly more complex as it involved the three types of "</description> </item> <item> <title>Newsletter 50</title> <link>https://reactos.org/blogs/newsletter-50/</link> <pubDate>Sat, 20 Dec 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-50/</guid> <description>The Perils of PSEH2 While KJK did get PSEH2 out in record time, this meant that it was relatively untested when he committed it and developers began using it. Currently PSEH seems to be corrupting data when exceptions get thrown, which then cascades down and causes functions to assert and crash, something that it was supposed to prevent. Michael Martin&#39;s theory about what is happening is that PSEH is clobbering local variables that are being held in registers, though KJK attributes it to an issue of not using setjmp.</description> </item> <item> <title>Soft of the Year Award</title> <link>https://reactos.org/project-news/soft-year-award/</link> <pubDate>Fri, 19 Dec 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/soft-year-award/</guid> <description> "Soft of the Year 2008" Award "Soft of the Year 2008" is a national Russian software award given annually to the best computer software. Winners in seven different categories are selected by results of people's voting (carried out by Mail.Ru). ReactOS won second place in the "Technologies" category. Thanks to everyone who supported us! </description> </item> <item> <title>Newsletter 49</title> <link>https://reactos.org/blogs/newsletter-49/</link> <pubDate>Mon, 17 Nov 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-49/</guid> <description>Network Configuration Johannes Anderwald has been working to fix a persistent bug in the network settings that resulted after he reimplemented the network configuration and settings dialog in netcfgx.dll using COM interfaces. Johannes also had to implement the COM interfaces, since they didn't exist before, and they are now in netshell.dll. Unfortunately, it seems that the dhcpclient was storing settings in the wrong registry key, which resulted in failure to retrieve DNS information and crashing of applications that relied on such information.</description> </item> <item> <title>ReactOS 0.3.7</title> <link>https://reactos.org/project-news/reactos-037/</link> <pubDate>Wed, 05 Nov 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-037/</guid> <description>ReactOS 0.3.7 Released Version 0.3.7 got delayed due to a couple of blocker bugs, however they are fixed now and we are ready to release. This release along with the rest of the 0.3.x series is still considered alpha quality software. ReactOS 0.3.7 continues further work on the main three principles of current ReactOS development: bugfixes, compatibility and stability. Changes summaryA consolidation of all changes in great details can be found in the changelog.</description> </item> <item> <title>Newsletter 48</title> <link>https://reactos.org/blogs/newsletter-48/</link> <pubDate>Sat, 25 Oct 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-48/</guid> <description>General Developments The release was delayed to take care of a series of regressions. That and I was busy so the changelog itself wasn&#39;t ready either. Anyways, every time a branch is created, Colin Finck, the release engineer, puts up a build and our team of testers run it through its paces and see if any applications that worked in the past got broken. If that happens, effort is made to fix the regression.</description> </item> <item> <title>Newsletter 47</title> <link>https://reactos.org/blogs/newsletter-47/</link> <pubDate>Sun, 28 Sep 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-47/</guid> <description>General Developments The developers have been quite busy over the past month, each chugging away at their respective spots. Cameron Gutman continues filling in holes in our networking code, while Ged Murphy is putting together headers for the user mode side of networking. Samuel Serapion and Timo Kreuzer are still working on the x64 branch, fixing compile errors and warnings as they go. We've also had a few discussions with the mingw64 people about what's missing on both ends to get ReactOS to run as a proper x64 OS.</description> </item> <item> <title>Newsletter 46</title> <link>https://reactos.org/blogs/newsletter-46/</link> <pubDate>Wed, 20 Aug 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-46/</guid> <description>Shellfolder Extensions All of the special folders such as control panel, printer folder, and administrative tools are actually shellfolder extensions that the Explorer shell implements using IShellFolder. Johannes Anderwald has been implementing those still missing in ReactOS as well as extending and fixing others. Two new ones are the Font folder and the Administrative Tools folder. Johannes also implemented the dialog for formating drives, but this obviously isn&#39;t functional.</description> </item> <item> <title>Newsletter 45</title> <link>https://reactos.org/blogs/newsletter-45/</link> <pubDate>Mon, 11 Aug 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-45/</guid> <description>LinuxWorld Report For the past week, Art Yerkes has been representing ReactOS at the Linux World Convention in California.&nbsp; He was unfortunately the only ReactOS developer or community member that could make it, but things seem to have turned out well.&nbsp; In the process of preparing for the convention, Art stumbled over an issue with drive letters that I will cover later.&nbsp; This forced him to rely on running ReactOS in QEMU, which actually turned out nicely.</description> </item> <item> <title>Newsletter 44</title> <link>https://reactos.org/blogs/newsletter-44/</link> <pubDate>Wed, 06 Aug 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-44/</guid> <description>General Development There was an interesting bug involving handle creation a while back. When creating the 4100th handle, the system would crash. This bug was exposed through VLC and was eventually fixed by Christoph von Wittich. The problem was the result of an incorrect calculation, where the code attempted to access an index higher than 4099 on the first table. Such values are out of bounds and are supposed to be found in the second table and higher.</description> </item> <item> <title>ReactOS 0.3.6</title> <link>https://reactos.org/project-news/reactos-036/</link> <pubDate>Wed, 06 Aug 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-036/</guid> <description>ReactOS 0.3.6 Released In a little over a month since version 0.3.5, we are announcing the release ReactOS 0.3.6. This release along with the rest of the 0.3.x series is still considered alpha quality software, so do not set your expectations too high. ReactOS 0.3.6 is the product of the current development focus: bugfixes, compatibility, and stability. There were more than a thousand commits to the ReactOS Subversion repository this month.</description> </item> <item> <title>Newsletter 43</title> <link>https://reactos.org/blogs/newsletter-43/</link> <pubDate>Wed, 16 Jul 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-43/</guid> <description>0.3.5 Release Obviously the release has gone out and we are receiving the usual reports of problems and successes. The biggest problem seems to be an issue people are having with Qemu on Vista, at least the Qemu version we prepackaged. This is not really a problem with ReactOS itself, but with the emulator software. For people who have encountered this, we suggest using the 0.9.0 builds instead of the 0.</description> </item> <item> <title>ReactOS 0.3.5</title> <link>https://reactos.org/project-news/reactos-035/</link> <pubDate>Mon, 30 Jun 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-035/</guid> <description>ReactOS 0.3.5 Released Four months after the release of 0.3.4, we are pleased to announce ReactOS 0.3.5. This release, along with the rest of the 0.3.x series is still considered alpha quality software, so do not set your expectations too high. ReactOS 0.3.5 release contains fixes for many old bugs, some having been present since 0.3 or even earlier and some being regressions introduced in further releases due to rewrites of certain components, not to mention new features.</description> </item> <item> <title>Newsletter 42</title> <link>https://reactos.org/blogs/newsletter-42/</link> <pubDate>Sat, 28 Jun 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-42/</guid> <description>Various Matters The project's been dealing with some internal matters recently and this combined with my day job being at the same time the majority of developers are online means I wasn't fully up to date on development matters and was busy dealing with other matters. Due to various issues and my lack of time recently, it's taken this long to get one out. We did have a second person who volunteered to write something up and the basic information in this newsletter is from his draft.</description> </item> <item> <title>Newsletter 41</title> <link>https://reactos.org/blogs/newsletter-41/</link> <pubDate>Thu, 15 May 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-41/</guid> <description>Just a reminder that there really isn&#39;t any set schedule for newsletters anymore. We (or at least I) publish whenever there&#39;s something to report, and boy do we have a lot of ground to cover. The past few weeks have been very eventful. 0.3.5 and Development Focus Amongst the developers, the joke was that Aleksey&#39;s vacation delayed the release, so it was his fault that we&#39;re behind. Now, it is Aleksey&#39;s fault, but for a different reason.</description> </item> <item> <title>Newsletter 40</title> <link>https://reactos.org/blogs/newsletter-40/</link> <pubDate>Mon, 05 May 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-40/</guid> <description>Microsoft DirectX Runtime First, let me state that legally, according to the whole Windows Genuine Advantage and EULA, you&#39;re not supposed to install the MS DirectX runtime on nongenuine Windows systems. On the other hand, the runtimes that come with various games as a prerequisite to playing the game aren&#39;t technically bound by the WGA. That aside, the MS DirectX runtime now loads on ReactOS. To get DX on, you need to manually copy the following files: dxg.</description> </item> <item> <title>New project of ReactOS Foundation</title> <link>https://reactos.org/project-news/new-project-reactos-foundation/</link> <pubDate>Fri, 04 Apr 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-project-reactos-foundation/</guid> <description>New project of ReactOS Foundation Our russian department launched a new service for opensource projects hosting: FireForge.net. This site provides file releases, SVN/CVS, web, ftp hosting, bug/feature trackers, mailing lists and everything else needed for building a successive opensource community. A difference from similar known sites like sf.net or code.google.com is that FireForge.net provides hosting services for projects interested for russian audience, and it&#39;s not just about providing services, but it&#39;s about providing a way for new projects to become known quicker, attract interested users and developers.</description> </item> <item> <title>Newsletter 39</title> <link>https://reactos.org/blogs/newsletter-39/</link> <pubDate>Mon, 31 Mar 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-39/</guid> <description>General Status We&#39;re currently in the middle of compiling the changelog, but that doesn&#39;t necessarily mean we&#39;re ready for release. The keyboard/mouse problem has slowly been worked out and according to Colin Finck it is now fixed. If you still encounter problems, complain to him, not me.&nbsp; The issue with the keyboard not responding during language selection should now be gone and was due to the keyboard driver not loading properly.</description> </item> <item> <title>Back to normal operation</title> <link>https://reactos.org/project-news/back-normal-operation/</link> <pubDate>Mon, 10 Mar 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/back-normal-operation/</guid> <description>Server maintenance Our scheduled server maintenance period is over now, all went good and is supposed to be in a working state. If you notice some unusual behavior, please don't hesitate to let us know!As a bonus, the subversion server was upgraded to the latest stable version, both svn:// and http:// access methods are provided, there is a special dedicated server for per-revision installation CDs storage, and even more bandwidth and server power to the ReactOS Website.</description> </item> <item> <title>Server maintenance</title> <link>https://reactos.org/project-news/server-maintenance/</link> <pubDate>Fri, 07 Mar 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/server-maintenance/</guid> <description>Server maintenance Our scheduled server maintenance started about a week ago. It went rarther smooth, with exception to all mail-related services. We're working on fixing email-related issues and beg our pardon for the inconvinience. Please have in mind that right now ALL email services may not work. This includes registration on the website, forum notifications, mailing lists, @reactos.org email aliases, etc.The mailing system will be restored as soon as possible</description> </item> <item> <title>Newsletter 38</title> <link>https://reactos.org/blogs/newsletter-38/</link> <pubDate>Sat, 01 Mar 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-38/</guid> <description>Server maintenance Recent server maintenance caused outages of the web and SVN servers. The ordeal lasted a few hours for some users, which could not access the project web page, SVN servers, or send mail to the mailing lists. If you sent an email to our mailing list during the outage your mail could have bounced, or have been lost. Don&#39;t believe the conspiracy theories, it was just a DNS change.</description> </item> <item> <title>Newsletter 37</title> <link>https://reactos.org/blogs/newsletter-37/</link> <pubDate>Thu, 07 Feb 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-37/</guid> <description>0.3.4 Release 0.3.4 was released a few weeks back. While it has seen some major improvements, the mouse/keyboard bug wasn&#39;t completely squashed in the release. However, it has been fixed in trunk by Aleksey, so all of you can stop complaining about it. On the other hand, people are reporting some major speed increases with this release. Thomas Bluemel&#39;s work on the desktop heap and Jim Tabor&#39;s work in deferring switchs between user and kernel mode seem to be paying off.</description> </item> <item> <title>ReactOS 0.3.4 Released</title> <link>https://reactos.org/project-news/reactos-034-released/</link> <pubDate>Tue, 22 Jan 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-034-released/</guid> <description>ReactOS 0.3.4 Released We are pleased to announce the release of the next version of ReactOS in the 0.3 series. This is a culmination of the last 3 months of development, and some significant progress has been made in various areas. Release cycle Starting from version 0.3.3 we have aimed to move our release cycle to a 2 month period. There are various reasons for this, but the two which are key to this decision is a desire to keep the main development tree in a stable condition, and an effort to keep up the interests of the people who follow the project, by providing regular release builds to play with.</description> </item> <item> <title>Forum lock</title> <link>https://reactos.org/project-news/forum-lock/</link> <pubDate>Thu, 17 Jan 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/forum-lock/</guid> <description> Forum Issues We&#39;re currently dealing with some malicious activity on the forum.&nbsp; Some of the developers have decided to lock it until the problem is fixed.&nbsp; Quite frankly, it&#39;s disappointing that we need to go this far, but we the development team will ban and kick people who refuse to behave or cause problems for us.&nbsp; </description> </item> <item> <title>Newsletter 36</title> <link>https://reactos.org/blogs/newsletter-36/</link> <pubDate>Tue, 08 Jan 2008 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-36/</guid> <description>General Developments Aleksey and Herve have been working on the PnP problem, which many people are experiencing through the unresponsive mouse or keyboard. At least some of the problem&#39;s been fixed, since people seem to have better success. In an attempt to squash the rest of the bug, Aleksey is updating the Remote Procedure Call code in ROS. Also, a working RPC would also allow WIDL, our substitute for MIDL (Microsoft Interface Definition Language), a method for software components written in different programming languages to communicate, to finally work.</description> </item> <item> <title>Newsletter 35</title> <link>https://reactos.org/blogs/newsletter-35/</link> <pubDate>Sun, 16 Dec 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-35/</guid> <description>Release Time According to our project manager the change log should be finished by the end of December and if all remaining blockers are fixed release will occur sometime in January. ReactOS 0.3.4 promises to improve on 0.3.3 by working on more hardware, running even more applications, being faster and more stable than ever before. Even so many of the same old restrictions apply. We thank everyone who has helped make this release possible.</description> </item> <item> <title>Newsletter 34</title> <link>https://reactos.org/blogs/newsletter-34/</link> <pubDate>Mon, 19 Nov 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-34/</guid> <description>A rare joint newsletter between Samuel and I. General Changes Some people have already noticed the inclusion of a new remote desktop utility, mstsc.exe, by Ged. Some asked why include this new tool when there is already such a client in SVN, albeit incomplete. The reasoning is simple. The author of the old client has been gone a while and Ged is not familiar with his code, so he chose to use something else.</description> </item> <item> <title>ReactOS Status Update</title> <link>https://reactos.org/project-news/reactos-status-update/</link> <pubDate>Wed, 14 Nov 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-status-update/</guid> <description>Status Update ReactOS had quite a few major improvements since the last 0.3.3 release, and I feel this needs to be given a special attention. Kernel First of all, the kernel gets mostly bugfixes in all areas, especially which haven't been touched for a long time (Cache controller, for example), leading to great improvements in compatibility+stability. A number of issues with Win32 applications crashing went away. Drivers Then, drivers.</description> </item> <item> <title>Newsletter 33</title> <link>https://reactos.org/blogs/newsletter-33/</link> <pubDate>Mon, 22 Oct 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-33/</guid> <description>Les Trophees du Libre Les Trophees du Libre is a contest for free software, divided into six categories. ReactOS has entered the contest, in the science category. At first glance that might seem odd, but LinuxBIOS is also in that category. However, it's not LinuxBIOS we should be worried about. The competition from the other projects is going to be rough. We're facing mathematical libraries, pattern recognition, even bioinformatics.</description> </item> <item> <title>Newsletter 32</title> <link>https://reactos.org/blogs/newsletter-32/</link> <pubDate>Sun, 23 Sep 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-32/</guid> <description>ReactOS 0.3.3 Recently we released 0.3.3. We thank all the developers, testers, translators and everyone else who helped make it possible. The official release announcement by our project coordinator is here. The changelog can be found here, new screenshots are also available here. You can download your copy in the download page. Rbuild Improvements Herve has been working recently on several rbuild improvements. The focuses of these is correctly separate and represent files using only a single scheme, improving flexibility and speed.</description> </item> <item> <title>ReactOS 0.3.3 Released!</title> <link>https://reactos.org/project-news/reactos-033-released/</link> <pubDate>Thu, 13 Sep 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-033-released/</guid> <description>ReactOS 0.3.3 Released! As we have previously made you aware, we skipped the 0.3.2 release due to massive problems with old incompatible drivers resulting in blocker bugs we couldn't resolve within the scheduled release time. With these issues now resolved, and along with a extensive amount of additional improvements, we are presenting the next minor release - 0.3.3 This is still labeled as alpha-stage release, so do not set your expectations too high: translating into a non-programmer’s language alpha-stage means: “You are lucky if it actually installs and runs for you outside of a virtual machine”.</description> </item> <item> <title>Newsletter 31</title> <link>https://reactos.org/blogs/newsletter-31/</link> <pubDate>Sun, 02 Sep 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-31/</guid> <description>This newsletter is late because I ran into a permissions conflict with RosCMS. Others who have also run into it, frik is fixing it tomorrow. Win32k Rewrite Samuel mentioned this last time and I spoke with the developers responsible to get more details. Jim Tabor, Timo Kreuzer, and Magnus Olsen have been working extensively to redo the win32k subsystem. The biggest thing is duplicating the behavior of Windows&#39; win32k.</description> </item> <item> <title>Newsletter 30</title> <link>https://reactos.org/blogs/newsletter-30/</link> <pubDate>Tue, 21 Aug 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-30/</guid> <description>Compilation fixes for MacOS X Recently some developers have managed to compile ReactOS in OS X. So if you have built mingw32 for your mac and would like to build ReactOS in your mac you can. The primary difficulties lay in some wchar defines and iswdigit function and where fixed relatively easily. Win32k The all important graphical subsystem continues its march to becoming the fully featured, safe and performing beast it should be.</description> </item> <item> <title>New RosCMS v3 online</title> <link>https://reactos.org/project-news/new-roscms-v3-online/</link> <pubDate>Tue, 14 Aug 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-roscms-v3-online/</guid> <description>New RosCMS v3 online The ReactOS Content Management System software for the ReactOS website got a major update. RosCMS is used to manage the ReactOS website and in near future additionally to maintain the ReactOS translation work. It is a very flexible web based system. The core parts of the software are the flexible database layout and the dynamic interface that consist of a bunch of filters. The end user can costumize his/her own workflow by changing the filter settings or choose one of the predefined views (which consist itself of filters internally).</description> </item> <item> <title>Newsletter 28</title> <link>https://reactos.org/blogs/newsletter-28/</link> <pubDate>Sun, 22 Jul 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-28/</guid> <description>Release time The long awaited 0.3.3 release is branched; the usual preparations for releases are under way. You should already know we skipped a version number and that this release is primarily bug fixes from the massive kernel rewrites that have been taking place. Stability being the primary motivation of this release, I can safely say this is a big improvement from the 0.3.1 release. The outlook looks bright on future releases, ever closer to the 0.</description> </item> <item> <title>Newsletter 29</title> <link>https://reactos.org/blogs/newsletter-29/</link> <pubDate>Sat, 21 Jul 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-29/</guid> <description>ReactOS 0.3.3 RC1 The release candidate was more or less a success, far more than what many of us expected. When bug reports started coming in from people running it on real hardware, several of us, including myself, were quite surprised. Having a stabilized kernel definitely helps. The RC was released for several reasons. First, ReactOS suddenly got a surge of attention over the past two weeks, resulting in people going and downloading our latest release.</description> </item> <item> <title>Newsletter 27</title> <link>https://reactos.org/blogs/newsletter-27/</link> <pubDate>Wed, 04 Jul 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-27/</guid> <description>Bug Hunt The past few weeks have seen quite a lot of activity.&nbsp; At least six major blocker bugs were dealt with, ranging from the network issue to various bugs in the command line console.&nbsp; The pre VMware Workstation 6 Display Driver also now installs and works, which opens up some interesting possibilities.&nbsp; Specifically, on VMware Workstation, the driver allows the use of DirectX or ReactX.&nbsp; Which means Magnus Olsen's work on ReactX can actually be demo'ed on Workstation, to an extent.</description> </item> <item> <title>Newsletter 26</title> <link>https://reactos.org/blogs/newsletter-26/</link> <pubDate>Mon, 11 Jun 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-26/</guid> <description>Forget 0.3.2 We promised a release period of two months, but all the kinks are not out yet. More than 2 months have passed and project leaders have decided that there are already enough changes in trunk to call it 0.3.3, the next release. This is a sign that development, although a bit hard to manage, is moving at faster rates. As development approaches 0.4.0 goals we would see increasing functionality and stability, as well as keeping in line with the best practices in software development, testing and compatibility.</description> </item> <item> <title>Update on ReactOS internals</title> <link>https://reactos.org/project-news/update-reactos-internals/</link> <pubDate>Thu, 07 Jun 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/update-reactos-internals/</guid> <description>Update on ReactOS internals 0.3.2 Release ReactOS 0.3.2 is officially going to be skipped (due to 4 blocker bugs), and ReactOS 0.3.3 will be the next in the cycle which, according to the 2 months release schedule,&nbsp;will be released in July. Trunk already has many improvements and bugfixes for 0.3.3, however we are still working on fixing those 4 major issues. Team Alex Ionescu left the ReactOS team to follow an exciting career opportunity working with David Solomon as an official replacement to&nbsp;Mark Russinovich Our best wishes to him at his new position, and a big thanks for all the great work he has done for ReactOS.</description> </item> <item> <title>Newsletter 25</title> <link>https://reactos.org/blogs/newsletter-25/</link> <pubDate>Wed, 06 Jun 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-25/</guid> <description>In theory, I shouldn't be writing this edition. In reality, I got tired of waiting for Samuel to get this out. Thank You Alex For those that don't know, Alex Ionescu, the kernel coordinator, has resigned.&nbsp; Alex first joined the project in 2004, around the 0.2.2 release.&nbsp; Since then, he's been at the center of quite a few squabbles about how to code the kernel.&nbsp; However, Alex has also been responsible for completely rewriting the kernel almost from the ground up.</description> </item> <item> <title>Newsletter 24</title> <link>https://reactos.org/blogs/newsletter-24/</link> <pubDate>Sun, 20 May 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-24/</guid> <description>When exam time comes, my priorities shift to real life obviously.&nbsp; As such, the newsletter is a week late.&nbsp; Whether the next newsletter is a week away or two will be up to Samuel when he gets around to it. Release Plans When the new release cycle was announced, the idea was that releases would happen every two months. This was a theoretical timeline that was dependent on several factors.</description> </item> <item> <title>Newsletter 23</title> <link>https://reactos.org/blogs/newsletter-23/</link> <pubDate>Tue, 01 May 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-23/</guid> <description>Just to make it clear, while we aim for a biweekly newsletter, we only aim for it to be up around Sunday. It can easily be delayed if there isn't enough to talk about. The Road to 0.3.2 For those of you who don't follow the ReactOS scene closely it may be hard to know what exactly is happening in terms of development progress. The technical nature of some improvements also proves confusing to most people.</description> </item> <item> <title>Newsletter 22</title> <link>https://reactos.org/blogs/newsletter-22/</link> <pubDate>Sun, 15 Apr 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-22/</guid> <description>A New Volume When Samuel took over the newsletter, there was no guideline as to what constituted a Volume.&nbsp; After talking to him, we decided to mark Volumes by year.&nbsp; This means that Volume 1 had nine issues from 2005, Volume 2 had five issues from 2006, and Volume 3 has eight issues and counting in 2007.&nbsp; And now we continue the biweekly rotation of who writes the meat of the article.</description> </item> <item> <title>Newsletter 21</title> <link>https://reactos.org/blogs/newsletter-21/</link> <pubDate>Mon, 02 Apr 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-21/</guid> <description>Another newsletter I am glad I am able to bring you the latest news about ReactOS through this newsletter. It is the purpose of this newsletter to inform everyone of the recent work and notable highlights of this great project. It is my hope that you will find it useful and informative. (Insert license agreement indicating no particular usefulness, assorted legal wording and notices here... Just kidding!) Project News New storage stack based on NT4-DDK examples implemented in trunk, fixes booting on VmWare and several other nasty bugs.</description> </item> <item> <title>Newsletter 20</title> <link>https://reactos.org/blogs/newsletter-20/</link> <pubDate>Sun, 18 Mar 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-20/</guid> <description>A Third Introduction Good day to all. The name's Z98 and I'm one of two release managers for ReactOS. The source files and QEMU images were generated by me, so if there are any mistakes, you know who to complain to. Today I wrote most of the newsletter and I will be helping samwise52 in the future.Reactions to 0.3.1 Reactions have varied in regard to 0.3.1, though one response was consistent.</description> </item> <item> <title>Newsletter 19</title> <link>https://reactos.org/blogs/newsletter-19/</link> <pubDate>Mon, 12 Mar 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-19/</guid> <description>0.3.1 Released! After months of discussions, testing and of course mountains of code, it&rsquo;s finally here! The official release announcement was made by our project coordinator. This release has many deep down changes that may not be comprehensible to most users, but most users will in fact notice improved stability and speed. The changelog will tell you about these changes in technical terms, but the best testimony would be your own tests.</description> </item> <item> <title>ReactOS 0.3.1 Released</title> <link>https://reactos.org/project-news/reactos-031-released/</link> <pubDate>Sun, 11 Mar 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-031-released/</guid> <description>ReactOS 0.3.1 Released! It's been almost half a year since the last release (0.3.0). And all this time work was going on like crazy - sometimes up to 50 commits per day. Mainly, the work focused on rewriting certain parts of the ReactOS Core (kernel, HAL, bootloader, etc). It's very hard to sum up&nbsp;the huge Changelog&nbsp;in an outline, but briefly: Freeldr was improved HAL's key areas&nbsp;have been&nbsp;significantly improved (irql-related, bus support, kd-functions) The Kernel experienced a massive rewrite of incompatible parts (and is still in the process of improvement) Run-time library (Rtl)&nbsp;got a lot of improvements and bugfixes Bugs were fixed in kernel-mode drivers&nbsp;and a better USB driver was added Registry-support&nbsp;has been&nbsp;greatly improved thanks to addition of&nbsp;&quot;cmlib&quot;, a library shared by the boot loader and the kernel to handle&nbsp;binary registry hives; it even supports binary registry hives created by Windows More fixes in the Win32 subsystem and user-mode DLLs Boot video&nbsp;driver (and a splash screen) was added Read through the changelog, and you will see the amount of changes in this release!</description> </item> <item> <title>ReactOS at DELL IdeaStorm</title> <link>https://reactos.org/project-news/reactos-dell-ideastorm/</link> <pubDate>Wed, 07 Mar 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-dell-ideastorm/</guid> <description>DELL IdeaStorm project After some requests from people&nbsp;at our forum, we decided to add an idea&nbsp;about ReactOS&nbsp;to the DELL IdeaStorm project.If you like this idea, &quot;Promote&quot; it, and it'll get higher on the list of popular ideas.Thanks!</description> </item> <item> <title>FOSDEM 2007</title> <link>https://reactos.org/project-news/fosdem-2007/</link> <pubDate>Thu, 01 Mar 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/fosdem-2007/</guid> <description>FOSDEM 2007 event in Brussels FOSDEM&nbsp;turned out to be a big great event indeed.I was just back from the event yesterday, and after having some rest I'm writing this news. This was my first time attending FOSDEM, and first time speaking at FOSDEM. I should say, FOSDEM's staff organized everything very well, the room(Janson)given for ReactOS talk was huge (and the space was not wasted ;)), the hotel was quite perfect and very well situated (despite it's far from the ULB, where the event took place, they provided a nice Taxi service).</description> </item> <item> <title>Newsletter 18</title> <link>https://reactos.org/blogs/newsletter-18/</link> <pubDate>Wed, 28 Feb 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-18/</guid> <description>Opening Words Here is another informative newsletter for your enjoyment. You may have recently noticed last issue, that some of our developers were part of community conferences and events. It&rsquo;s all part of new PR efforts to get ReactOS out there, in front of serious developers and community leaders. To raise awareness of how much ReactOS has advanced and it&rsquo;s vast potential.I&rsquo;m kind of wary of this issue, I&rsquo;ve been talking about 0.</description> </item> <item> <title>ReactOS at FOSDEM event</title> <link>https://reactos.org/project-news/reactos-fosdem-event/</link> <pubDate>Tue, 20 Feb 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-fosdem-event/</guid> <description>ReactOS talk at the coming FOSDEM event in Brussels FOSDEM (Free and Open source Software Developers' European Meeting) will take place the 24th and 25th of February 2007&nbsp;in Brussels, Belgium.ReactOS is going to be represented by me, who is going to give a talk&nbsp;this saturday&nbsp;about ReactOS internals, and do some live demonstrations of what ReactOS achieved so far.See you there, Aleksey Bragin.</description> </item> <item> <title>Fundraising campaign finished!</title> <link>https://reactos.org/project-news/fundraising-campaign-finished/</link> <pubDate>Mon, 12 Feb 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/fundraising-campaign-finished/</guid> <description>ReactOS Fundraising campaign A month ago ReactOS project announced a fundraising campaign aimed to gather money to support our operation - servers, exhibitions, promotions, spread the word, etc.Today I am very glad to say that this fundraising campaign did not only meet the required value of 4000 euro, but also outperformed and we gathered a total of 4450 EUR!We already ordered parts for the new buildslave server, which is going to be amazingly fast in building DBG/REL .</description> </item> <item> <title>Newsletter 17</title> <link>https://reactos.org/blogs/newsletter-17/</link> <pubDate>Mon, 12 Feb 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-17/</guid> <description>Busy Times It's been a hectic 3 weeks, yes I am 1 week overdue. I've been real busy with school and personal stuff, but I haven't been the only one thats been busy. It seems in my absence that 0.3.1 is finally shaping up. In this issue I will expand on the developments that have occurred not only in the main development branch (trunk), but also in the &quot;stable&quot; release branch for 0.</description> </item> <item> <title>Newsletter 16</title> <link>https://reactos.org/blogs/newsletter-16/</link> <pubDate>Thu, 18 Jan 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-16/</guid> <description>Another 2 weeks without 0.3.1 I know you've been waiting for it(I sure have), but you certainly want a release that will boot. ReactOS will still be alpha, unstable and not recommended for everyday use. If you're really hardcore you'll try out the SVN versions. I can say that 0.3.1 will be a VERY significant improvement from 0.3.0, when we can finally get it to run on your PC. Also I would like to remind everyone(just in case you missed the big fundraising bar at the top of every reactos.</description> </item> <item> <title>Newsletter 15</title> <link>https://reactos.org/blogs/newsletter-15/</link> <pubDate>Sun, 07 Jan 2007 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-15/</guid> <description>On the status of 0.3.1 Many of you have asked about 0.3.1 since it was clearly promised for the time frame of late December-early January. There have been many queries about it in the chat rooms and forums. Well, the problem is actually rather simple. The developers have decided that releases should be made every month, or at an appropriate time where in trunk or a designated branch is reasonably usable and showcases the progress of the ReactOS project.</description> </item> <item> <title>Interview 6: Art Yerkes</title> <link>https://reactos.org/interviews/art-yerkes/</link> <pubDate>Fri, 29 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/art-yerkes/</guid> <description>Art YerkesInterview with Art Yerkes by Klemens FriedlThis is the sixth in a series of interviews with ReactOS developers. In a few weeks we will have a nice collection showcasing the talent of the people behind ReactOS.Art, born in Philadelphia, PA, USA in 1974. He&#39;s been involved with ReactOS since 2002 and contributed primarily to the keyboard code in win32k and the network code. Lately much of the work has been networing related, as well as slowly giving birth to a PowerPC architecture port.</description> </item> <item> <title>ReactOS Website back online again</title> <link>https://reactos.org/project-news/reactos-website-back-online-again/</link> <pubDate>Fri, 29 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-website-back-online-again/</guid> <description>ReactOS Website back online again ReactOS website has been offline for two weeks due to a hardware problem. Everything is back online!The RAID controller inside the server failed and &quot;forgot&quot; all RAID partitions, the reason is unknown. The server hardware and harddisk content has been restored and everything is back online again.Fixing the problem was not easy during christmas time. Thanks to all persons who have been involved&nbsp;in bringing the webserver back online.</description> </item> <item> <title>Newsletter 14</title> <link>https://reactos.org/blogs/newsletter-14/</link> <pubDate>Thu, 28 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-14/</guid> <description>Another Introduction Hello, my name is Samuel Serapi&oacute;n, IRC nick: encoded. I Hail from San Juan, Puerto Rico, a 20 year old computer engineering student, I will be your ReactOS informant today. I have great hopes for this project, and this is the small part I do to help it. What will YOU do to help ReactOS!? Website Outage The day was December 14, 2006. A day which will live in infamy, well maybe not that much.</description> </item> <item> <title>Interview 5: Johannes Anderwald</title> <link>https://reactos.org/interviews/johannes-anderwald/</link> <pubDate>Wed, 13 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/johannes-anderwald/</guid> <description>Johannes Anderwald Interview with Johannes Anderwald by Klemens FriedlThis is the fifth in a series of interviews with ReactOS developers. In a few weeks we will have a nice collection showcasing the talent of the people behind ReactOS.&nbsp;Johannes Anderwald, born in Graz, Austria in 1983. He's been involved with ReactOS since 2004 and became a developer in 2006. Lately much of the work has been related to increase source compability with Visual Studio Development Suite.</description> </item> <item> <title>Newsletter 13</title> <link>https://reactos.org/blogs/newsletter-13/</link> <pubDate>Wed, 13 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-13/</guid> <description>I'm the new guy(s) Yup, that's right, we're the new newsletter writers (those two words should never be used in combination - I promise never to do it again). We fought off a crowd of people breaking their necks to apply, and finally, we're here. So. Who are we? I am Dana Burkart, I will do most of the writing, and my associate - Samuel Serapion - will be providing most of the information.</description> </item> <item> <title>Interview 4: Steven Edwards</title> <link>https://reactos.org/interviews/steven-edwards/</link> <pubDate>Wed, 06 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/steven-edwards/</guid> <description>Steven EdwardsInterview with Steven Edwards by Aleksey BraginThis is the fourth in a series of interviews with ReactOS developers. In a few weeks we will have a nice collection showcasing the talent of the people behind ReactOS.&nbsp;For several years Steven Edwards has served as a valuable liaison between Wine and ReactOS. In addition, he ha&#39;s been responsible for porting Wine to the MinGW compiler and making the resulting libraries actually work.</description> </item> <item> <title>Mac & Parallels support, new ReactOS Roadmap</title> <link>https://reactos.org/project-news/mac-parallels-support-new-reactos-roadmap/</link> <pubDate>Wed, 06 Dec 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/mac-parallels-support-new-reactos-roadmap/</guid> <description>Intel Mac &amp; Parallels support, new ReactOS Roadmap Intel Mac and Parallels support, new Roadmap, new Interviews and newsletter author request. &nbsp;ReactOS Intel Mac compatibility ReactOS development builds (trunk) have run fine now for two days on Intel Mac (with Bootcamp installed) computers. Intel Mac's consist of standard hardware but there are some differences which had made it impossible to run ReactOS before. Intel Mac's don't have PS/2 keyboard controllers.</description> </item> <item> <title>Interview 3: Magnus Olsen</title> <link>https://reactos.org/interviews/magnus-olsen/</link> <pubDate>Tue, 28 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/magnus-olsen/</guid> <description>Magnus OlsenInterview with Magnus Olsen by Klemens FriedlThis is the third in a series of interviews with ReactOS developers. In a few weeks we will have a nice collection showcasing the talent of the people behind ReactOS.&nbsp;Magnus Olsen, born in Skarholmen, Sweden in 1976 been involved with ReactOS since year 2002 and contributed to a lot of different parts throughout the project since that time.StartHow did you get involved with ReactOS?</description> </item> <item> <title>Interview 2: Alex Ionescu</title> <link>https://reactos.org/interviews/alex-ionescu/</link> <pubDate>Tue, 21 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/alex-ionescu/</guid> <description>Alex IonescuInterview with Alex Ionescu by Klemens FriedlThis is the second in a series of interviews with ReactOS developers. In a few weeks we will have a nice collection showcasing the talent of the people behind ReactOS.Alex Ionescu was born in Bucharest, Romania (Europe) in 1986. He currently lives in Montreal, Canada and is a student at Concordia University in Software Engineering. He&#39;s been involved with ReactOS since 2004 and contributed to many different parts.</description> </item> <item> <title>Newsletter 12</title> <link>https://reactos.org/blogs/newsletter-12/</link> <pubDate>Sun, 19 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-12/</guid> <description>Time to get this Newsletter Back on Track A newsletter author, a new start. No, I am not the new newsletter author, we are still searching for one. Please read the related news entry for more detailed information.If you would like to be the ReactOS newsletter author, please send an email to &quot;ros-dev&quot; developer mailing list (don't forget to subscribe), explaining why you think you would be a good newsletter author.</description> </item> <item> <title>Announcement: ReactOS Interviews series</title> <link>https://reactos.org/project-news/announcement-reactos-interviews-series/</link> <pubDate>Wed, 15 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/announcement-reactos-interviews-series/</guid> <description>Announcement: ReactOS Interviews series We are starting a series of interviews with ReactOS developers. The first interview features our project coordinator Aleksey Bragin. Interviews are divided into several parts and&nbsp;cover different interesting topics - beginning from how&nbsp;developers got involved&nbsp;in the ReactOS project and going up to which development software they use in their daily work.We&nbsp;are going to publish&nbsp;interviews on a weekly basis.&nbsp;Please don't forget to read the second news of today, a request for a &quot;ReactOS Weekly Newsletter&quot; author.</description> </item> <item> <title>Interview: Aleksey Bragin</title> <link>https://reactos.org/interviews/aleksey-bragin/</link> <pubDate>Wed, 15 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/interviews/aleksey-bragin/</guid> <description>Aleksey BraginInterview with Aleksey Bragin by Klemens FriedlAleksey Bragin, born in Moscow, Russia in 1983 been involved with ReactOS since year 2002 and contributed to a lot of different parts throughout the project since that time.&nbsp;&nbsp;StartHow did you get involved with ReactOS?Lots of time ago an idea came to my mind, the idea was creating a FOSS alternative to Windows. However, I was too busy with the projects I was doing (mostly in game development area) and thus did not really search for already existing projects of this kind.</description> </item> <item> <title>Wanted: ReactOS Weekly Newsletter Author</title> <link>https://reactos.org/project-news/wanted-reactos-weekly-newsletter-author/</link> <pubDate>Wed, 15 Nov 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/wanted-reactos-weekly-newsletter-author/</guid> <description>Wanted: ReactOS Weekly Newsletter Author We search an author for our &quot;ReactOS Weekly Newsletter&quot;.History Jason Filby had established the ReactOS Weekly Newsletter (called &quot;ReactOS Weekly&quot;) in 1999 as a useful weekly news summary located on www.reactos.com. In 2000 the newsletter had been discontinued. In late 2004 to early 2005, Zach Tong wrote 5 Issues of the &quot;SPLASH - The official ReactOS Newsletter&quot;. With the website redesign in summer 2005, the newsletter came back with Stuart &quot;TwoTailedFox&quot; Robbins as author.</description> </item> <item> <title>ReactOS servers up again, audit progress bar wrong</title> <link>https://reactos.org/project-news/reactos-servers-again-audit-progress-bar-wrong/</link> <pubDate>Tue, 31 Oct 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-servers-again-audit-progress-bar-wrong/</guid> <description>One of ReactOS server machines (which serves DNS, SVN and website proxy)&nbsp;went&nbsp;offline due to a problem with the webhosting. Now all services&nbsp;are up again except for SVN which is temporarily offline for moving to another machine (expected to be finished today).&nbsp; Sorry for any inconvenience you might have experienced.The audit is not complete, the progress bar is wrong because of the server downtime.</description> </item> <item> <title>ReactOS participation in GSoC 2006 Mentor Summit</title> <link>https://reactos.org/project-news/reactos-participation-gsoc-2006-mentor-summit/</link> <pubDate>Mon, 09 Oct 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-participation-gsoc-2006-mentor-summit/</guid> <description>Google conducts GSoC 2006 mentor summit next week In the area of &quot;better collaboration between organizations&quot;, Alex Ionescu will present a short talk on ReactOS on the following topics: Targetting, developping and testing Win32 versions of projects on ReactOS. Solving OS-level and other platform-specific bugs. Finding out and dealing with undocumented behaviour. Testing Win32 ports without acquiring a Windows license and spending money on a test environment. The ReactOS Foundation is looking at creating an official long-term &quot;division&quot; responsible for communicating with developers and leaders from other projects.</description> </item> <item> <title>Server transfer is over</title> <link>https://reactos.org/project-news/server-transfer-over/</link> <pubDate>Mon, 25 Sep 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/server-transfer-over/</guid> <description>Servers are finally migrated to new places! The ReactOS server is finally fully migrated now to a new datacenter and new hardware, including mailing lists, webserver with all its contents, SVN server, etc.We had to change really a lot of stuff, to make future transfers easier, to prevent&nbsp;&quot;slashdotting&quot; and thus some of you experienced problems using the website or services during the transfer period. I am very pleased to announce that now everything is in place and is expected to work as it always did.</description> </item> <item> <title>ReactOS 0.3.0 Released!</title> <link>https://reactos.org/project-news/reactos-030-released/</link> <pubDate>Mon, 28 Aug 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-030-released/</guid> <description>ReactOS 0.3.0 Released! This release holds a few records - it is the most long-awaited release of ReactOS, it is the release which was preceded by 3 Release Candidates instead of usual 2, and at last ReactOS release never had so much changes since the last one.This release's main feature is the networking ability - it's the first release where it is possible to download and install FireFox and browse the web, get mIRC (or some other irc client) and get to #reactos to chat a bit with developers.</description> </item> <item> <title>ReactOS Status Report - 07/2006</title> <link>https://reactos.org/project-news/reactos-status-report-072006/</link> <pubDate>Wed, 26 Jul 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-status-report-072006/</guid> <description>ReactOS status report for July 2006 The second issue (07/2006) of the ReactOS status reports was published today by Aleksey Bragin (ReactOS Project Coordinator). It's a general overview of the last 6 months of project's progress, with some additional information and future outlook. Download The ReactOS status report is available in several document formats (doc, rtf, xml and plain text). HTML page MS Word document (.doc) RTF document (.</description> </item> <item> <title>Summer Of Code Applications</title> <link>https://reactos.org/project-news/summer-code-applications/</link> <pubDate>Sat, 27 May 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/summer-code-applications/</guid> <description>Summer Of Code: Winning applications for ReactOS project It's time to announce the results of the first phase of Google Summer Of Code project. Some statistics: ReactOS has&nbsp;got&nbsp;4 slots (our&nbsp;number desired projects was 12), and got around ~30 applications (plus 4 applications were classified as ineligible, and 2 more has been redirected to Google).Results: ReactOS Print Spooler Service (spoolsv) by Peter Windridge, mentored by Alex Ionescu. Remote Desktop Client application &amp; ActiveX control by Michele Cicciotti, mentored by Alex Ionescu Login System by Justin Haygood, mentored by Thomas Weidenmueller Clipboard Server API implementation by Pablo Borobia, mentored by Thomas Weidenmueller I congratulate the winning students, they did a great job at picking up complex, but interesting and needed topics, and providing applications, which showed they are capable of performing these tasks.</description> </item> <item> <title>ReactOS and TinyKRNL projects' official relationship</title> <link>https://reactos.org/project-news/reactos-and-tinykrnl-projects-official-relationship/</link> <pubDate>Fri, 19 May 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-and-tinykrnl-projects-official-relationship/</guid> <description>ReactOS and TinyKRNL projects' official relationship Prepared by Aleksey Bragin and Alex Ionescu, Project Coordinators.There is a little information posted officially about TinyKRNL project and this provides a base for gossip to appear. This short article is intended to clear up official relations between these two projects. &nbsp; TinyKRNL is an educational and documentation project which creates plug-in replacements for various modules of Windows 2003 SP 1 (ultimately replacing the kernel too) and a series of papers ultimately combined into a book.</description> </item> <item> <title>ReactOS Compatibility Database (beta status)</title> <link>https://reactos.org/project-news/reactos-compatibility-database-beta-status/</link> <pubDate>Fri, 21 Apr 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-compatibility-database-beta-status/</guid> <description>ReactOS Compatibility Database (beta status) The ReactOS Compatibility Database has reached beta status.URL: http://www.reactos.org/support/ The compatibility database has been designed to store application and driver data. Simply click on one of the 5 green start buttons on the frontpage to begin to browse through the database. To submit an application/driver, click on &quot;Submit Application&quot; (menu bar).Please have a look at the help and faq section for more information.</description> </item> <item> <title>Google Summer Of Code 2006</title> <link>https://reactos.org/project-news/google-summer-code-2006/</link> <pubDate>Wed, 19 Apr 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/google-summer-code-2006/</guid> <description>Google Summer Of Code 2006 Aleksey Bragin's (Project Coordinator&nbsp;of ReactOS) email to the mailing list:We are negotiating technical details now, and soon information will appear on the official SoC 2006 web-site.Meanwhile, we already should start compiling a list of project's suggestions for it. Everyone is welcome to provide suggested projects, however please have in mind that only 1 student can do one project (or separate part of the bigger project).</description> </item> <item> <title>ReactOS Auditing Progress - Status 03/2006</title> <link>https://reactos.org/project-news/reactos-auditing-progress-status-032006/</link> <pubDate>Fri, 10 Mar 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-auditing-progress-status-032006/</guid> <description>ReactOS Auditing Progress - Status 03/2006 A lot of things happened in january and february 2006. This news issue's goal is to sum up what has been happening in the past few weeks. If you want to stay tuned, visit the ReactOS Blogs from time to time. And do not forget to add the ReactOS News Feed to your feed reader or aggregator.A lot of information of this news issue came from Ged Murphy's blog entry, thank you for clearing up of some questions.</description> </item> <item> <title>ReactOS is dead, Welcome to ReactOS !</title> <link>https://reactos.org/project-news/reactos-dead-welcome-reactos/</link> <pubDate>Wed, 22 Feb 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-dead-welcome-reactos/</guid> <description>Hello, It is already a known fact that ReactOS project started working again and that SVN servers are running since some days again. But what has happened? We read so much in the news? What’s true? Let’s summarize: ReactOS project is Dead, welcome to ReactOS ! Every Opensource project can be split into 3 main phases: - Starting and developing fundamental things - Fixing then bugs, doing the long road of mprovements and enhancements - Finding something where it can be used ReactOS now came to the 0.</description> </item> <item> <title>Newsletter 11</title> <link>https://reactos.org/blogs/newsletter-11/</link> <pubDate>Fri, 10 Feb 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-11/</guid> <description>ReactOS Weekly Newsletter Issue 11, "Not dead just yet" Not dead just yet! Whew. Now that Real Life has for now finished kicking me in the gonads for the time being, it's time to let you guys, the End Users, know what's actually happening in the ReactOS Project. Issue II I could have sworn went up, but either it got deleted, or I missed a button.Now, first things, first.</description> </item> <item> <title>Reset, Reboot, Restart, legal issues and the long road to 0.3</title> <link>https://reactos.org/project-news/reset-reboot-restart-legal-issues-and-long-road-03/</link> <pubDate>Fri, 27 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reset-reboot-restart-legal-issues-and-long-road-03/</guid> <description>Hello, There has been a lot of talk about possible tainted code in ReactOS and or developers that had access to leaked Microsoft source code. This has caused a lot of speculation about the future of the ReactOS Project. I'm going to try to put those fears to rest and explain what has been going on and where we are going to go from here. There was one issue that started this discussion and it related to clean-room reverse engineering of certain code in ReactOS.</description> </item> <item> <title>New ReactOS Blog</title> <link>https://reactos.org/project-news/new-reactos-blog/</link> <pubDate>Wed, 25 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-reactos-blog/</guid> <description>New ReactOS Blog The ReactOS Project use a new blog system. The old and outdated dottext 1.x blog system rest now in peace. GvG installed "serendipity" and integrated the global login system.Lets hope than now more devs blogs and write informative articles than before.</description> </item> <item> <title>Newsletter 10</title> <link>https://reactos.org/blogs/newsletter-10/</link> <pubDate>Mon, 09 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-10/</guid> <description>Time to get this Newsletter Back on Track A new year, a new start, I always say. Unfortunately, I was a little bit busier over the holiday period than I had anticipated, but now that I'm back doing early shifts, instead of the late ones I was being handed, I will have enough time set aside to continue.So, I'll start as I mean to go on... by Compiling! Yep, ReactOS' Source Code may be all-singing, all-dancing, bu without it being compiled, all it does it look like a pretty collection of ASCII Codes.</description> </item> <item> <title>ReactOS status report - 01/2006</title> <link>https://reactos.org/project-news/reactos-status-report-012006/</link> <pubDate>Sat, 07 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-status-report-012006/</guid> <description>ReactOS status report for January 2006 The first issue of the quarterly ReactOS status reports. Steven Edwards (ReactOS Project Coordinator) published the first issue of the status report. It's a general overview of the last quarter. The original status report announcement is available in the mailing list archive.Project Coordinator's (PC) job has several responsibilities, one is to provide quarterly status updates regarding all major activities of the project.</description> </item> <item> <title>Newsletter Status</title> <link>https://reactos.org/blogs/newsletter-status/</link> <pubDate>Fri, 06 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-status/</guid> <description>Hi Folks, TwoTailedFox here, just giving you guys the rundown on what's happenning with the Newsletter.Unfortunately, I was busier than I'd intended to be over Christmas and New Years. Being given lots of long shifts bunched together is a sure-fire way for me to feel very, very tired.Newsletter contents for Issue 10 have been finalised, and I've jotted down every relevent SVN update since the 13th of December.</description> </item> <item> <title>Happy New Year!</title> <link>https://reactos.org/project-news/happy-new-year/</link> <pubDate>Sun, 01 Jan 2006 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/happy-new-year/</guid> <description>Happy New Year! 2005 was a great year for ReactOS.The following facts came from the SVN server (thanks to Casper Hornstrup): The core ReactOS code base is now 120MB large. The repository is currently 624MB large and contains ~20500 revisions. ~8000 of these revisions were created in 2005. This mean 39% of the total number of revisions created during ReactOS' entire 8 year history was created in 2005!</description> </item> <item> <title>Newsletter 9</title> <link>https://reactos.org/blogs/newsletter-9/</link> <pubDate>Tue, 20 Dec 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-9/</guid> <description>Issue 9 of the Newsletter has landed There are very few things that irritate me. Windows XP playing havock with my mouse cursor ranks among them. Thus, a reformat and reload ensues. And to top it all off, I have a PSU that's as dodgy as an SCO-Endorsed Lawsuit. For some strange reason, one of my Hard Drives will have its power drop out, which causes my drive to spin down, that acts like a domino toppling, and causes my system to hang.</description> </item> <item> <title>ReactOS Website Translation Process</title> <link>https://reactos.org/project-news/reactos-website-translation-process/</link> <pubDate>Tue, 13 Dec 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-website-translation-process/</guid> <description>ReactOS Website Translation Process - Community Challenge I started the ReactOS Website Translation Process one week ago. My plan was to start it with an information in the ReactOS IRC Web Channel (#reactos-web). The idea was to allow a small group of translators to translate ReactOS web contents with the RosCMS interface. Now, some interface bugs has been fixed and a lot of translated web contents has been added to the database (thanks to all contributors/translators).</description> </item> <item> <title>Newsletter 8</title> <link>https://reactos.org/blogs/newsletter-8/</link> <pubDate>Mon, 12 Dec 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-8/</guid> <description>Welcome To Reality Welcome to the ReactOS Weekly Newsletter, Issue 8, where there are three kinds of people, none of them particularly effective at writing a newsletter today.The Delay: Excuses Inbound Unfortunately, Issue 8 was delayed last week, because Mrs. Flu decided to bed me over, and screw me crosseyed, leaving me very ill, and making my body wish it had a built-in thermostat. Anyway, it's better to have a newsletter late, than not at all, so let's just jump straight to it.</description> </item> <item> <title>ReactOS Website Update</title> <link>https://reactos.org/project-news/reactos-website-update/</link> <pubDate>Wed, 30 Nov 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-website-update/</guid> <description>ReactOS Website Update The ability to browse through the newsletters and news entries wasn't so easy. I got response from several visitors. In conclusion, they prefer a WineHQ newsletter style layout.I rewrote the newsletter and news interface and add a ReactOS News Feed (RSS 2.0 and Atom 1.0).Everything is available on the website frontpage!If you have ideas or suggestion about the website please use the ReactOS Forums and/or the ReactOS Wiki.</description> </item> <item> <title>Newsletter 7</title> <link>https://reactos.org/blogs/newsletter-7/</link> <pubDate>Sun, 27 Nov 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-7/</guid> <description>Welcome to Issue 7 of the ReactOS Weekly Newsletter, as persistant as a Jehovah's Witness. This week, I'll be taking a look at the NDK used by the ReactOS Developers, covering WINE 0.9.2, and detailing the latest SVN activity.NDK: What it does, and why it's needed &quot;What is the NDK designed to do?&quot;, I hear you ask. Well, first off, a little bit of it's history. The NDK stands for Native Development Kit, and was the brainchild of Alex Ionescu, as a way of allowing Windows and ReactOS developers alike to have access to a wealth of undocumented kernel and native structures and function prototype.</description> </item> <item> <title>Newsletter 6</title> <link>https://reactos.org/blogs/newsletter-6/</link> <pubDate>Sun, 20 Nov 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-6/</guid> <description>Welcome to Issue 6, the Issue that confirms we've beaten Splash. And to celebrate, this is going to be a Big issue. First off, We'll be taking a look at where ReactOS is headed, other than for x86, covering the Xbox, Xen, and PowerPC ports.And we've also got out first vic.. I mean volunteer for our very first Interview. .. Now there's no excuse for the rest of the Developers to not volunteer!</description> </item> <item> <title>Newsletter 5</title> <link>https://reactos.org/blogs/newsletter-5/</link> <pubDate>Sun, 13 Nov 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-5/</guid> <description>ReactOS Weekly Newsletter Volume 1, Issue 5 The Number keeps creeping up, and I believe, with this Issue, the ReactOS Weekly Newsletter equals the amount of editions Splash, the former ReactOS Newsletter, releasedFreeloader: What is it? Freeloader (abbreviated freeldr [Why is abbreviated such a long word? -Ed.]), is the ReactOS Bootloader, licensed under the GPL.What does it do? It parses the ReactOS registry, and examines particular keys for certain values to act upon.</description> </item> <item> <title>Newsletter 4</title> <link>https://reactos.org/blogs/newsletter-4/</link> <pubDate>Mon, 07 Nov 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-4/</guid> <description>ReactOS Weekly Newsletter Volume 1, Issue 4 Issue 4. A full month of Newsletters, and we're only just beginning.ReactOS and other Software I said I'd do this last week, and I'm not one to cut back on a promise.So, to clarify, ReactOS is an Operating System. What is an Operating System supposed to include? Well, there are several mentalities. The Linux Distro Approach. All the software you'd ever need on one DVD, and then some.</description> </item> <item> <title>Newsletter 3</title> <link>https://reactos.org/blogs/newsletter-3/</link> <pubDate>Mon, 31 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-3/</guid> <description>Another Week, Another Newsletter, a lot of news stuffed into a single issue, like an 8-course Barium meal.A Request! I actually got a request for some content for the newsletter. And since I like the look of them I'll have a look at both subjects. Let us begin.New Voting System It was decided a while back that the voting procedures needed to be changed, after a slight mis-hap on IRC, and some questioning the validity of a vote conducted there, as opposed to the Ros-Dev Mailing List.</description> </item> <item> <title>ReactOS 0.2.8 Released!</title> <link>https://reactos.org/project-news/reactos-028-released/</link> <pubDate>Mon, 31 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-028-released/</guid> <description>ReactOS 0.2.8 Released! This release brings us near to the release we are all looking forward to, 0.3.0. As always our developers have done a great job. For more information please have a look at the changelog.</description> </item> <item> <title>New mailing list search and voting technique</title> <link>https://reactos.org/project-news/new-mailing-list-search-and-voting-technique/</link> <pubDate>Wed, 26 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-mailing-list-search-and-voting-technique/</guid> <description>New mailing list search! The ability to search the mailing lists with Google wasn't enough for me so I've created a new more flexible mailing list search. This is available under http://www.reactos.org/mlsearch/We also decided to change the voting system. Now votes are done on the forum instead of the mailing list. This way we can do anonymous votes and keep track of the many decisions that must be made.</description> </item> <item> <title>Newsletter 2</title> <link>https://reactos.org/blogs/newsletter-2/</link> <pubDate>Sun, 23 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-2/</guid> <description>Well, would you look at that. Another Sunday. another Newsletter. And Boy has this week been interesting.The ReactOS Constitution Found here, the new ReactOS Constitution is designed to clarify many of the things we all took for granted, such as who can do what on the project, and to elaborate on how Voting Prodecures should be followed. In addition, it also lays out the responsibilities of all the members of the Board of Directors of the ReactOS Foundation.</description> </item> <item> <title>Newsletter 1</title> <link>https://reactos.org/blogs/newsletter-1/</link> <pubDate>Sun, 16 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/blogs/newsletter-1/</guid> <description>The Big Intro Ah, Hello There! Allow me introduce myself. My name is Stuart Robbins, and my job on Reactos.org, is to write a newsletter, each week, giving you, the End User, and even Casual Developer, the run-down on what is going on behind the scenes, with the ReactOS Open-Source Operating System.The ReactOS Content Management System First off, is the new ReactOS.org Content Management System, abbreviated RosCMS. It blends in nicely with the ReactOS Wiki (Itself using MediaWiki), while also providing space for new Website Articles (Much like this one), as well as providing small subsections, to announce news, like 0.</description> </item> <item> <title>ReactOS at Linux World Expo UK</title> <link>https://reactos.org/project-news/reactos-linux-world-expo-uk/</link> <pubDate>Sat, 08 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-linux-world-expo-uk/</guid> <description>On 05th and 06th October, ReactOS attended Linux World Expo UK as part of the .Org village. The two representatives for the project were Ge van Geldorp and Ged Murphy. Equipment for the exhibition consisted of 3 laptops, one running ReactOS on real hardware, one running ReactOS in VMWare and a laptop to act as an internet gateway. We also had around 100 live CDs and 400 flyers.</description> </item> <item> <title>State of the Repository</title> <link>https://reactos.org/project-news/state-repository/</link> <pubDate>Sat, 08 Oct 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/state-repository/</guid> <description>WaxDragon took a look at what happened in ReactOS during September The stats:In Sepember, there were:578 commits98 bugs opened94 bugs closedI wasn't able to determine the bugs that weere touched during the last month, since something made *all* bugs appear touched.A little change of format, I will review the closed bugs first, then go over the SVN commits in less detail than last month.</description> </item> <item> <title>New ReactOS Homepage</title> <link>https://reactos.org/project-news/new-reactos-homepage/</link> <pubDate>Thu, 29 Sep 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/new-reactos-homepage/</guid> <description>New ReactOS Homepage is online! The new ReactOS homepage is now (2005-09-29) online!The website moved to www.reactos.org as the primary name, with www.reactos.com being an alias (you'll be redirected automatically to www.reactos.org if you use the old name).The mailing lists are also going to be moved from reactos.com to reactos.org, so if you have filtering in place please take this into account.Many thanks to Ge van Geldorp, Michael Wirth and especially Klemens Friedl who put a lot of effort in the new site.</description> </item> <item> <title>ReactOS 0.2.7 Released!</title> <link>https://reactos.org/project-news/reactos-027-released/</link> <pubDate>Tue, 23 Aug 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-027-released/</guid> <description> ReactOS 0.2.7 Released! This release brings as always more compatibility and stability. At the time also heavy work on a new webpage is done. It will be up in a few weeks. </description> </item> <item> <title>ReactOS 0.2.6 Final released!</title> <link>https://reactos.org/project-news/reactos-026-final-released/</link> <pubDate>Sun, 10 Apr 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/project-news/reactos-026-final-released/</guid> <description> ReactOS 0.2.6 Released! As always a new release brings increases in speed, stability and compatibility.The next release, 0.3, will feature many improvements - but most notably somewhat usable networking. </description> </item> <item> <title></title> <link>https://reactos.org/parts/footer.html</link> <pubDate>Sat, 01 Jan 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/parts/footer.html</guid> <description> </description> </item> <item> <title></title> <link>https://reactos.org/parts/head.html</link> <pubDate>Sat, 01 Jan 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/parts/head.html</guid> <description> </description> </item> <item> <title></title> <link>https://reactos.org/parts/header.html</link> <pubDate>Sat, 01 Jan 2005 00:00:00 +0000</pubDate> <guid>https://reactos.org/parts/header.html</guid> <description> </description> </item> </channel></rss>If you would like to create a banner that links to this page (i.e. this validation result), do the following:
Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):
If you would like to create a text link instead, here is the URL you can use:
http://www.feedvalidator.org/check.cgi?url=https%3A//reactos.org/index.xml
