Hi!
ion(a)svn.reactos.com wrote:
> - Update ASM header file with more offsets.
>
>
> Updated files:
> trunk/reactos/ntoskrnl/include/internal/asm.h
>
[PCH] obj-i386/ntoskrnl/include/ntoskrnl.h.gch
In file included from ntoskrnl/include/internal/ntoskrnl.h:14,
from ntoskrnl/include/ntoskrnl.h:43:
ntoskrnl/include/internal/asm.h:132:1: "CONTEXT_FULL" redefined
In file included from w32api/include/windef.h:249,
from w32api/include/ddk/ntddk.h:35,
from ntoskrnl/include/ntoskrnl.h:18:
w32api/include/winnt.h:1482:1: this is the location of the previous definition
In file included from ntoskrnl/include/internal/ntoskrnl.h:14,
from ntoskrnl/include/ntoskrnl.h:43:
ntoskrnl/include/internal/asm.h:133:1: "CONTEXT_FLOATING_POINT" redefined
In file included from w32api/include/windef.h:249,
from w32api/include/ddk/ntddk.h:35,
from ntoskrnl/include/ntoskrnl.h:18:
w32api/include/winnt.h:1479:1: this is the location of the previous definition
make: *** [obj-i386/ntoskrnl/include/ntoskrnl.h.gch] Error 1
Did I miss a memo or should I delete something to make this work?
Thanks,
James
8^>
greatlrd(a)svn.reactos.com wrote:
>Change some error msg from ConErr to ConOut for they are being pipe so the behover are equal with ms windows cmd
>
>
>
>Updated files:
>trunk/reactos/subsys/system/cmd/error.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
Hi,
I think this change is wrong (also some parts from 16579). The error
messages have always to go to the error output (STD_ERROR_HANDLE).
- Hartmut
ion(a)svn.reactos.com wrote:
> - Fix nasty APC delivery bug (in case a Kernel-Mode Special APC still returned with a Normal Routine, the Normal Routine was called with incorrect values (Special Routines take PVOID* arguments, while Normal Routines do not!))
> - Remove APC from list before setting it to non-inserted.
> - Do proper thread termination piggybacking; terminate threads in user-mode as Hartmut correctly fixed.
>
>
>Updated files:
>trunk/reactos/ntoskrnl/ke/apc.c
>trunk/reactos/ntoskrnl/ps/kill.c
>
>
>
Hi,
I do not agree to this changes. For a non system thread, we use a kernel
mode apc first, which uses a second user mode apc. This overhead isn't
necessary. For system threads it isn't possible to use a kernel mode apc
which calls PspExitThread. A system thread must terminate it self. It is
only possible to help by marking a flag, setting an event or unwait the
thread.
- Hartmut
Hi,
Sorry but I accidentally lost 60 emails including the one I'm supposed
to reply to.
Hartmut, you have done a recent change in kill.c in which you change the
APC inside PspTerminateThreadByPointer to a user-mode APC. This is
incorrect and I don't understand why it was done... furthermore, I've
even documented a source of information which proves my code was correct
(on top of the function header), so why did you change it?
Best regards,
Alex Ionescu
Website proposal looks good.
I don't know if my opinion worth a cent, but I think the lines between left bar menu items make it harder to read and understand. The freebsd.org style is much simpler for brain to acquire and understand, when you only have one bold line around the whole navigation panel, and the items are separated with simple BR tag. Every extra line creates an extra load in your reception systems and occupy brain neuro cycles that can be used for thinking about content or other high abstract concepts instead.
Thanks
Yash
>> http://frik85.fr.funpic.de/reactos/en/index.htm (HTML version)
>
>Nice and clear design, fresh colors. :)
>I'd like to see this proposal as new homepage.
> Martin
Hey all,
Just a second thought about the website that ReactOS is planning on
updating. There are several ideas out there and several layouts. Here are my
suggestions:
Fedora Core 4
OpenLDAP for user information and Login functions
Perl and PHP
Apache 2.0.xx
POP3 and Imap4 email access
NNTP service
MySQL for CMS, Wiki, Portal
Postgresql for CMS, Portal, Wiki
I also believe in sticking with a header, and a three column layout, as well
as a footer. The site should be updateable by either database (MySQL or
Postgresql) or XML. Should provide login credential system that will allow
admins to add news and features.
I think users should be allowed or have access to giving detailed system
data to allow developers to focus on certain devices, drivers, and
applications. This would allow a user to also check the status on a new
optimized driver or binary, or any updates that React my want to distribute
for download. Later ReactOS.com should integrate with the currently
installed software on the users system to alert them of new releases,
patches, updates, and information; much like windows update. I also think
that the portal system should allow users to check @reactos.com email or
provide it in attempts to raise money for the site.
Another great thing that I know major OS manufacturers include is a
development library/ I think that we should list the source code and allow
users to browse it much like webCVS but also to annotate it, and allow a
user to chat in a forum type environment if they don't understand a line of
the code.
Just a few thoughts on color: KISS (Keep it simple stupid). Keep color usage
minimal and allow the user to customize it to their liking with templates.
I wonder how the development of the USB stack is going, the wiki "blog" is kind of old, I tested the USB tool mentioned in the forum some month ago, but it was just info it provided, how is it going with for example keyboard and mouse support?
Yours sincerely,
Jaix Bly
mbosma(a)svn.reactos.com wrote:
> HUMA2000: Spanish translation
>
>
> Updated files:
> trunk/rosapps/packmgr/lib/es.rc
>
Building the Rosapps module fails with the following error :
D:\Reactos\Svn\rosapps>svn update
U packmgr\lib\es.rc
Updated to revision 16597.
D:\Gerard\Reactos\Svn\rosapps>mingw32-make clean
mingw32-make: *** No rule to make target `clean'. Stop.
Any idea ?
Best regards