All,
today I would like to officially announce the (sub)project I was
working on for the last half a year, and make a call to developers to
participate.
ReactOS has been around for about 11 years, and it's been growing
each year since then. The demand for an open source Windows-
compatible operating system is huge: geek, servers, netbooks,
accounting, point of sales, CAD... The list could go on and on.
Time goes by, new versions of Windows operating systems are being
released. ReactOS usability still has not reached any significant
value. Not to say ReactOS didn't even officially enter the Beta
stage. Separately, there are many achievements: audio support
appeared, bootloader is able to boot real Windows, some Windows
binary drivers could be loaded and work in ReactOS, networking is
being improved every day, the kernel is being actively worked on too.
But all of that does not really matter for the end user. For a user
it's important that a web-browser loads websites, instant messenger
client connects and works, [Microsoft/Open] Office shows documents,
email client gets new messages.
This bare usability is what's still missing, and if ti continues to
be like this, I am afraid our project won't be of much use in another
10 years. Certainly, I became very concerned and started analyzing
situation. Being opensource project without major commercial
sponsors, there are certain limitations as to what could be done to
improve the situation, so mainly it's a matter of picking right
priorities and properly managing (motivating) existing human resources.
The part of ReactOS which plays major role in compatibility and
usability is Win32 subsystem. Right now, it's a huge monster which
requires a lot more human resources than we have now. It's very hard
and time consuming to reach even Windows 2000 level of compatibility
with current amount of participating developers, and high entry level.
I came up with something which could solve this problem: Arwinss. To
better explain what it is, I made a special presentation (URL to
slides in PDF format is in the end of this email). Please imagine
myself talking through it as I didn't perform/record it.
Now, after you read through the presentation, I would like to make a
proposal to all developers (even newcomers, who never worked on
ReactOS before). Let's make an Arwinss week, or Arwinss month. Every
developer could definitely find a few hours during a week to hack
Arwinss. Entry level is rather low, there are some basic docs about
Arwinss in the wiki, and I am happy to consult about details.
If I could make this new subsystem out of nothing (out of Wine and
ReactOS) almost alone (Kamil and Smiley help is very valued and
appreciated!) within a few months, imagine what we could do all
together?
With the best regards,
Aleksey Bragin.
The presentation: (links to further information are in the
presentation too)
http://www.reactos.org/media/docs/2010/arwinss.pdf
This project is not wine so please keep it nice! You guys are newbies
and need to play nice! We old timers can kick it around, not you!
Until a year or two you guys can be asses....
Friendly warning,
James
sir_richard(a)svn.reactos.org wrote:
> Please, next time before you harass us with e-mails, try to read your logs.
> LD choses a random entrypoint if the symbol cannot be found.
I hope you aren't referring to the 2 emails stating that you broke the build?
The 2 guys who so rudely "harassed" you for highlighting your mistake are testers, they can't spot and fix your errors.
The fact that you broke the build stops them from testing. Please be a little more considerate.
Ged.
Hi Sir Richard,
just FYI, this rev introduced freeldr crash (happens after loading
initial drivers): http://bjauy.com/images/45155-freeloader.png
Best regards,
Maciej
----------------------------------------------------------------------
Rezerwując wczesniej kupisz bilety lotnicze taniej!
Sprawdz >>> http://link.interia.pl/f256c
Hi,
sir_richard wrote:
> /* GLOBALS *******************************************************************/
> +
> +/* Boot and double-fault/NMI/DPC stack */
> +UCHAR P0BootStackData[KERNEL_STACK_SIZE] __attribute__((aligned (16)));
> +UCHAR KiDoubleFaultStackData[KERNEL_STACK_SIZE] __attribute__((aligned (16)));
MinGW GCC 4.4.x can ignore in some situations attribute aligned on
uninitialized global variables because of a bug. A workaround is to
initialize a variable or to compile with -fno-common.
Hi Sir Richard,
Build's broken:
ntoskrnl/ke/i386/context.c: In function 'KiSwapProcess':
ntoskrnl/ke/i386/context.c:30: warning: passing argument 1 of '_InterlockedXor' makes pointer from integer without a cast
ntoskrnl/ke/i386/context.c:31: warning: passing argument 1 of '_InterlockedXor' makes pointer from integer without a cast
make: *** [/mnt/ramdisk/buildbot/debug/obj/ntoskrnl/ke/i386/context_ntkrnlmp.o] Error 1
make: *** Waiting for unfinished jobs....
Command exited with non-zero status 2
from: http://build.reactos.org:8010/builders/x86_%28Debug%29/builds/3789/steps/co…
Gabriel.
_________________________________________________________________
25 Gygabite gratis online. Archivia e condividi i tuoi file!
http://www.windowslive.it/skyDrive.aspx