Hi!
On Sun, Mar 29, 2009 at 1:13 AM, <jmorlan(a)svn.reactos.org> wrote:
> Author: jmorlan
> Date: Sun Mar 29 09:13:35 2009
> New Revision: 40280
Would you mind taking a look at a cmd.exe bug Wax found? (I can't log
in to bugzilla to file a bug report but I can quickly describe the
issue) For some reason the CreateProcess call in in telnetd that
spawns cmd.exe causes it to generate the error INVALID_HANDLE_VALUE.
This issue does not happen with ReactOS telnetd on windows if you use
Windows cmd.exe or if you use another console application on ReactOS
such as ping.exe so we have isolated it to a cmd.exe problem.
Telnetd is located in rosapps/sysutils/applications/telnetd
Thanks!
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
I searched for everywhere in the source code to see the definition of
the MMVAD struct, but it is nowhere.
So I suppose that we have something else (with different name) for
that? If so, where is it?
Thanks,
Jun
Hi.
I suggest to divide rosapps on two parts:
1) Components which are present in Windows (rosapps)
2) 3rd party components (3rdapps)
In rosapps it is necessary to place all components without which the
system can normally work (calc, hh, winhlp32, charmap, games and etc)
In 3rdapps components which are not present in Windows (downloader,
imagesoft and etc) will take places
Such placing of components will allow to reduce compilation time as you
can not compile not the modules necessary to you (rosapps and/or 3rdapps)
Please tell your opinion on my proposition.
--
WBR,
Dmitry Chapyshev
Are you all receiving this automated reply when sending mail to ros-dev ML ?
Kind regards,
Sylvain Petreolle
________________________________
De : feedback(a)teamexaminer.com
À : spetreolle(a)yahoo.fr
Envoyé le : Vendredi, 27 Mars 2009, 11h20mn 09s
Objet : RE: [ros-dev] Re : Where is MMVAD struct?
Thank you for your feedback. Your email will be reviewed and processed accordingly.
Sincerely,
Examiner.com
Hello everybody,
As you might have noticed, I recently did some changes to our Website stuff
and Regression Testing System.
Finally, it's time to show some results now:
== BuildBot upgrade ==
Christoph reinstalled the latest version of BuildBot on our Swedish server
today, since the previous server system was way too old for such an upgrade.
This also had the uncomfortable side-effect of the BuildBot URL changing
from http://reactos.org:8010 to http://build.reactos.org:8010, which most of
you already seem to have noticed ;-)
Sorry for not giving a note about this before.
I thought I could just finish my stuff and then write this E-Mail explaining
all changes, but as always, it took longer than expected :-/
== Crash Recovery in rosautotest and sysreg2 ==
In the recent days, I rewrote rosautotest in C++ for getting a more
maintainable code. This update also added a Crash Recovery feature.
Together with my updated version of sysreg2, we can now resume the testing
process with the next test in case a specific test made ReactOS crash.
== Web Test Interface ==
As we recently set up a new VM, which will eventually replace our current
outdated www.reactos.org server, I finally had a playground for my third
component of our testing system: The "testman" Web Interface.
It is available at http://79.99.5.181/testman/
Features include finding specific test results through a getbuilds-like
interface and comparing them.
The Comparison feature can compare up to 5 results side-by-side and show the
differences. Clicking on "Show only changed results" will only show the
lines that have differences. You can also use Drag & Drop to move the column
headers with all associated results to get the table to look like you want
it.
Clicking a test result will show details, including a log of this specific
test.
Just play around with it a bit and you should easily get to know about all
features.
Regarding Lone_Rifle's interface at http://reactos.nxserve.net: From what he
told me, this one was only meant as a decentral alternative as long as we
don't have "testman" on an official server.
I'm saying this, so nobody gets the impression that I just wanted to
extinguish his work with my implementation. If some people prefer
Lone_Rifle's version over mine, it would just need to be adjusted to the new
BuildBot URL and those people could still use it.
Comments and suggestions are welcome of course.
Not everything works perfect yet (e.g. the Debug Buildslave needs quite some
time now as all tests are run), but it should be ready for you to try now.
Best regards,
Colin
Hi,
Since today, I cannot access the old buildbot page
(http://reactos.org:8010/) anymore.
I found the new URL (http://build.reactos.org:8010) in Colin's commit
message.
Was this an intentional change?
I am asking because noone announced this change and some people might
now wonder where the buildbot page is...
Or am I the only one accessing it via my favourites? Is there even a
link from the website (I couldn't find one)?
Ah... and the old page had an icon, the new one doesn't.
Timo
PS:
The nice regtest pages at http://reactos.nxserve.net also don't work
anymore.
They were very useful and I'd like to see them up again.
So a) do we have something like that for our website (or in work)?
Or b) can this one be fixed? (I forgot who owns it.)
In a previous message you said:
>Alex Ionescu wrote:
>> This new hack directly slows down every context switch instead of every
>> page fault -- the latter is a less important perf hit.
>
>This slowdown is very small, especially when comparing with other
>"Hack of Doom".
>I just want to see, is it the only raison d'être of that old hack or not.
Could you explain the reason you add Mm Hack of Doom again if the
slowdown is very small?
Regards,
--
Matthieu Suiche
On Mon, Mar 23, 2009 at 1:56 AM, <dgorbachev(a)svn.reactos.org> wrote:
> Author: dgorbachev
> Date: Mon Mar 23 03:56:01 2009
> New Revision: 40181
>
> URL: http://svn.reactos.org/svn/reactos?rev=40181&view=rev
> Log:
> Add "REACTOS Mm Hack of Doom" again (removed in r39723). Bug #4296.
>
> Modified:
> trunk/reactos/ntoskrnl/ke/i386/ctxswitch.S
> trunk/reactos/ntoskrnl/ke/i386/trap.s
>
> Modified: trunk/reactos/ntoskrnl/ke/i386/ctxswitch.S
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/ctxswitch…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ke/i386/ctxswitch.S [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ke/i386/ctxswitch.S [iso-8859-1] Mon Mar 23 03:56:01 2009
> @@ -389,9 +389,6 @@
>
> /* Checking NPX, disable interrupts now */
> mov eax, [esi+KTHREAD_INITIAL_STACK]
> -
> - /* HACK */
> - mov ecx, [eax - 4]
> cli
>
> /* Get the NPX State */
>
> Modified: trunk/reactos/ntoskrnl/ke/i386/trap.s
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/trap.s?re…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ke/i386/trap.s [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ke/i386/trap.s [iso-8859-1] Mon Mar 23 03:56:01 2009
> @@ -1924,10 +1924,14 @@
> NoFixUp:
> mov edi, cr2
>
> + /* REACTOS Mm Hack of Doom */
> + test dword ptr [ebp+KTRAP_FRAME_EFLAGS], EFLAGS_INTERRUPT_MASK
> + je HandlePf
> +
> /* Enable interrupts and check if we got here with interrupts disabled */
> sti
> - test dword ptr [ebp+KTRAP_FRAME_EFLAGS], EFLAGS_INTERRUPT_MASK
> - jz IllegalState
> + /* test dword ptr [ebp+KTRAP_FRAME_EFLAGS], EFLAGS_INTERRUPT_MASK
> + jz IllegalState */
>
> HandlePf:
> /* Send trap frame and check if this is kernel-mode or usermode */
>
>
Hi,
I am doing a project on implementing VFS. Can anyone help me as a mentor?
Since I'm more used to in Linux than in ROS code, it would be a great help
if someone can help me through. I have gone through the ntos folder and read
some documents and also the winvfs project that someone here suggested. I'm
aware this is not a prime target in the ROS team, but once I complete this,
I might be able to contribute to areas of higher priority.
Hoping for a positive reply,
Thank you.
--
Mahesh M
Happy hacking...
, ,
/ \
((__-^^-,-^^-__))
`-_---' `---_-'
`--|o` 'o|--'
\ ` /
): :(
:o_o:
"-"