Ros-dev November 2009

ros-dev@reactos.org

37 participants
22 discussions

want to learn
by rahul nagpal 12 Nov '09

12 Nov '09

The three Intel Book's which you refer me are only theoratical base not for Practical.I want to learn Assembly language or system programming. My purpose is only that i want to understand the coding of reactos which is done in vc++ but use many lower level programming concepts which i couldn't understand.So you please tell me that which Book or People or Institute can help me to understand the lower level concepts which you can use in reactos coding.So i can also want to participate in making the coding of reactos by using the lower level concepts... :) (:

3 2

Help!!!
by rahul nagpal 12 Nov '09

12 Nov '09

4 3

Re: [ros-dev] [ros-diffs] [hyperion] 44091: modified Makefile Give poor pefixup its own echo line modified ReactOS-amd64.rbuild modified ReactOS-arm.rbuild modified ReactOS-i386.rbuild Set global linker flags globally Goodbye NTOSKRNL_SHARED modified tools/rbuild/b
by Ged Murphy 11 Nov '09

11 Nov '09

Not sure about codeblocks but I still use the msvc backend to generate all the vcproj files. -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of hyperion(a)svn.reactos.org Sent: 11 November 2009 03:41 To: ros-diffs(a)reactos.org Subject: [ros-diffs] [hyperion] 44091: modified Makefile Give poor pefixup its own echo line modified ReactOS-amd64.rbuild modified ReactOS-arm.rbuild modified ReactOS-i386.rbuild Set global linker flags globally Goodbye NTOSKRNL_SHARED modified tools/rbuild/backe modified tools/rbuild/backend/codeblocks/codeblocks.cpp modified tools/rbuild/backend/msvc/vcprojmaker.cpp Build fixes. I really want to delete these dead backends

4 3

want to learn
by rahul nagpal 10 Nov '09

10 Nov '09

Hey, i can get th source code of reactos, but i can't understand the coding, your programmer who wrote these type of coding can also be refer any book/notes.You please tell me the name of that book, for which i can also take refrence for understanding the lower level of coding for making kernel and other files.I know these type of languages(C,C++,Java Core,VC++,Oracle 8i,html),but not for the hardware level only for making user level programs.So Please help me do this task easier and i also tell you that i didn't know the way to access your channel #reactos also help me i have no sufficient time to take part in it but i try so please refer any book.Thanxxx for making me the member of your group and Congratulations for your Project Success... :) (:

5 6

Re: [ros-dev] [ros-diffs] [tkreuzer] 44052: [NDK] - Add KEXCEPTION_FRAME offsets
by Alex Ionescu 09 Nov '09

09 Nov '09

Did you make sure these matched the actual Microsoft-defined offsets in ksamd64? On 2009-11-09, at 2:49 PM, tkreuzer(a)svn.reactos.org wrote: > Author: tkreuzer > Date: Mon Nov 9 20:49:47 2009 > New Revision: 44052 > > URL: http://svn.reactos.org/svn/reactos?rev=44052&view=rev > Log: > [NDK] > - Add KEXCEPTION_FRAME offsets > > Modified: > branches/ros-amd64-bringup/reactos/include/ndk/amd64/asm.h > > Modified: branches/ros-amd64-bringup/reactos/include/ndk/amd64/asm.h > URL: http://svn.reactos.org/svn/reactos/branches/ros-amd64-bringup/reactos/inclu… > ============================================================================== > --- branches/ros-amd64-bringup/reactos/include/ndk/amd64/asm.h [iso-8859-1] (original) > +++ branches/ros-amd64-bringup/reactos/include/ndk/amd64/asm.h [iso-8859-1] Mon Nov 9 20:49:47 2009 > @@ -192,6 +192,42 @@ > #define CONTEXT_LastExceptionFromRip 0x4c8 > > // > +// KEXCEPTION_FRAME offsets > +// > +#define KEXCEPTION_FRAME_P1Home 0x000 > +#define KEXCEPTION_FRAME_P2Home 0x008 > +#define KEXCEPTION_FRAME_P3Home 0x010 > +#define KEXCEPTION_FRAME_P4Home 0x018 > +#define KEXCEPTION_FRAME_P5 0x020 > +#define KEXCEPTION_FRAME_InitialStack 0x028 > +#define KEXCEPTION_FRAME_Xmm6 0x030 > +#define KEXCEPTION_FRAME_Xmm7 0x040 > +#define KEXCEPTION_FRAME_Xmm8 0x050 > +#define KEXCEPTION_FRAME_Xmm9 0x060 > +#define KEXCEPTION_FRAME_Xmm10 0x070 > +#define KEXCEPTION_FRAME_Xmm11 0x080 > +#define KEXCEPTION_FRAME_Xmm12 0x090 > +#define KEXCEPTION_FRAME_Xmm13 0x0A0 > +#define KEXCEPTION_FRAME_Xmm14 0x0B0 > +#define KEXCEPTION_FRAME_Xmm15 0x0C0 > +#define KEXCEPTION_FRAME_TrapFrame 0x0D0 > +#define KEXCEPTION_FRAME_CallbackStack 0x0D8 > +#define KEXCEPTION_FRAME_OutputBuffer 0x0E0 > +#define KEXCEPTION_FRAME_OutputLength 0x0E8 > +#define KEXCEPTION_FRAME_MxCsr 0x0F0 > +#define KEXCEPTION_FRAME_Rbp 0x0F8 > +#define KEXCEPTION_FRAME_Rbx 0x100 > +#define KEXCEPTION_FRAME_Rdi 0x108 > +#define KEXCEPTION_FRAME_Rsi 0x110 > +#define KEXCEPTION_FRAME_R12 0x118 > +#define KEXCEPTION_FRAME_R13 0x120 > +#define KEXCEPTION_FRAME_R14 0x128 > +#define KEXCEPTION_FRAME_R15 0x130 > +#define KEXCEPTION_FRAME_Return 0x138 > +#define SIZE_KEXCEPTION_FRAME 0x140 > + > + > +// > // EXCEPTION_RECORD Offsets > // > #define EXCEPTION_RECORD_ExceptionCode 0x00 > > Best regards, Alex Ionescu

1 0

Re: [ros-dev] [ros-diffs] [sginsberg] 43958: - Fix the "fix" of un-protecting the 7 IDT entries on P5 in HAL's BIOS call code when setting the custom Invalid Opcode handler
by Dmitry Gorbachev 08 Nov '09

08 Nov '09

Hi! This change causes a crash when booting, on Pentium.

3 4

Reactos and MinWin
by Gerard Murphy 03 Nov '09

03 Nov '09

I've recently been taking an interest in MinWin, especially as it's now visible in Windows 7, and I want to bring up the possibility of introducing something similar into ReactOS. I know some of you will be familiar with WinWin and I know at least one of you will know quite a bit more about it than I do, but for those who don't here's an overview. What is WinMin? MinWin is an internal project at Microsoft that manifested around the time of the Vista rewrite. Very basically explained, the aim is to detangle the very core components from the full operating system, resulting in something which can be built separately and leaving just enough components for a working system. This minimal operating system can then boot and be tested separately or be built as part of the full OS and tested in internally as before. The main problem in doing this, and one of the main benefits in solving it, is module dependencies. By simply cutting out the bottom part of the OS you're left with modules which potentially call out to other modules which may now be missing. If these dependencies aren't understood you have the possibility of an unstable OS as you never know where a code path may lead. It also means you need to build more components to get the thing to link, which also undermines one of the reasons for doing it. What Microsoft did is to draw up a dependency tree and structure it in a layered hierarchy. Modules were then rearranged to make architectural sense according to the NT design and a top layer was decided upon. API call were then rewritten within this hierarchy such that anything in one layer would only call API's in the layers below it. Therefore if something in layer 8 called something in layer 7 which then called something in layer 12, the APIs would be fixed to only use APIs at or below its level according to the hierarchy. You're then left with a clean line where nothing calls out and you have a tightly bound core OS which is completely independent from anything. What is essentially left in Microsoft's WinMin is what people class as Cutlers NT along with supporting components to get a bootable system. The main components are: The kernel (main kernel, not the full ntoskrnl module), parts of the executive, memory manager, networking, a file system driver and core drivers (basc IO and Bus, etc) This is then exposed in usermode by 2 dlls, ntdll.dll and the new kernelbase.dll. On top of this you have a console for issuing commands. This comprises of the full OS and amounts to about 25Mb on disk and has around a 40Mb working set. Let's quickly explain the new kernelbase dll. As many of the API's in the lower level dlls such as kernel32 and advapi32 were targeting functionality which wasn't in WinMin, it was decided to pull out any of the API's which were required to exercise WinMin and put them into kernelbase. This dll could then be used when building a running WinMin to provide all the functionality this kernel offered. The dlls which had their APIs removed now forwarded their call onto kernelbase so from a user perspective, nothing had changed. Microsoft went a step further and designed a new technology around virtual dlls. They split functionality of dlls into 'api sets' These can now be seen in Win 7 in the system32 dir with the prefix 'api-ms-win-core-<function>-<num of>-1-0.dll'. WinMin components now link against these virtual dlls which load up the real libs listed in apisetschema.dll. However this involves modification to the loader and I don't think it's something worth us considering right now. What are the reasons for doing this? For a start, it's a much better design from an engineering perspective. The more software you have running on a system the more noise is created and the more things can interfere with each other. It gives us a base to innovate with without worrying about affecting anything outside. It gives us a more reliable base for the OS and a better platform to run comprehensive and efficient tests. It makes us more attractive to external companies as we would have a slick NT compatible kernel ready for companies to build their products on, especially embedded applications. With a few more additional items such as the base win32 subsystem, we'd have something along the lines of a stripped out ServerCore or Windows PE. This is only a quick overview for discussion purposes, but it outlines the main design and goals of WinMin. Comments, questions, concerns and gripes welcome J Ged.

10 16

0.3.11 Status update
by Aleksey Bragin 03 Nov '09

03 Nov '09

Hello, updating everyone on the 0.3.11 status. There is one blocker bug, http://www.reactos.org/bugzilla/ show_bug.cgi?id=4934, which is rapps's inability to complete any download in VMWare. Other regressions (including VMWare video driver, samba-TNG problm) are also present, however they could be either hacked away for release or shipped - e.g. not much of a problem since VMWare Video Driver installer doesn't work in new VMWares anyway. Amount of positive changes outweighs the negative. Please try to have a look at the 4934 bug to fix it ASAP. WBR, Aleskey Bragin.

1 0

Integration of ultracopier to reactOS
by alpha_one_x86 03 Nov '09

03 Nov '09

Hello, I'm the developper of ultracopier, I propose ultracopier as default copier under reactOS for the reactOS explorer. I will activly developpe it under reactOS. It based on Qt. Only the version 0.2.0.0 is developped for reactOS. Screenshot: http://ultracopier.first-world.info/screenshots/reactOS-ultracopier.png -- alpha_one_x86 <alpha_one_x86(a)first-world.info> Main developper of Ultracopier, Esourcing and server management IT, OS, technologies, security and business department

8 21

Re: [ros-dev] [ros-diffs] [hpoussin] 43875: [freeldr/WINLDR] Simplify freeldr.ini syntax for common cases - If boot type is not specified, autodetect bootsector and Windows types - Try to automatically detect version of loaded Windows - Accept boot options after name of OS - Separate loading and scanning of system hive As a result, lines like "multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT4" /DEBUG /BREAK" work
by Aleksey Bragin 01 Nov '09

01 Nov '09

Booting via "ReactOS (Debug)" is broken - when trying to select it, it jumps back to the first item in the list. On Oct 31, 2009, at 6:09 PM, hpoussin(a)svn.reactos.org wrote: > Author: hpoussin > Date: Sat Oct 31 16:09:03 2009 > New Revision: 43875 > > URL: http://svn.reactos.org/svn/reactos?rev=43875&view=rev > Log: > [freeldr/WINLDR] Simplify freeldr.ini syntax for common cases > - If boot type is not specified, autodetect bootsector and Windows > types > - Try to automatically detect version of loaded Windows > - Accept boot options after name of OS > - Separate loading and scanning of system hive > As a result, lines like "multi(0)disk(0)rdisk(0)partition(1) > \WINNT="Windows NT4" /DEBUG /BREAK" work > > Modified: > trunk/reactos/boot/freeldr/freeldr/bootmgr.c > trunk/reactos/boot/freeldr/freeldr/include/winldr.h > trunk/reactos/boot/freeldr/freeldr/oslist.c > trunk/reactos/boot/freeldr/freeldr/windows/winldr.c > trunk/reactos/boot/freeldr/freeldr/windows/wlregistry.c

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev November 2009