Under Virtual PC 2007, ReactOS r24721 (as well as the last few over the last
few days) simply do not boot.
Boot CD: Boots, installs under text mode, stops when switching to GUI mode,
has ntoskrnl.dll error in debug mode
Live CD: Never finishes booting.
Compiler: RosBE 0.3.1 (GCC 3.4.5)
Does it boot for anyone else? If so, I'll attempt to figure out a way to get
it to boot.
Actually "@X" were removed from all .def files to maintain
compatibility with MSVC compiler, and GCC will do this silently with
"--enable-stdcall-fixup" (which didn't work for some reason when
enabled a few month ago).
WBR,
Aleksey Bragin.
On Nov 11, 2006, at 11:33 PM, ekohl(a)svn.reactos.org wrote:
> Author: ekohl
> Date: Sat Nov 11 23:33:06 2006
> New Revision: 24722
>
> URL: http://svn.reactos.org/svn/reactos?rev=24722&view=rev
> Log:
> KbdLayerDescriptor is a STDCALL function.
> -=skip=-
> Modified: trunk/reactos/dll/keyboard/kbdbe/kbdbe.def
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/keyboard/
> kbdbe/kbdbe.def?rev=24722&r1=24721&r2=24722&view=diff
> ======================================================================
> ========
> --- trunk/reactos/dll/keyboard/kbdbe/kbdbe.def (original)
> +++ trunk/reactos/dll/keyboard/kbdbe/kbdbe.def Sat Nov 11 23:33:06
> 2006
> @@ -4,5 +4,5 @@
> LIBRARY kbdbe.dll
>
> EXPORTS
> -KbdLayerDescriptor
> +KbdLayerDescriptor@0
> ;EOF
-=skip=-
Hello,
as you might have already noticed I took the chance while upgrading
SVN server to 1.4.0 and creating a mirror to effectively set it to
readonly state for now.
The blocker bug is the stack corruption issue, which somewhen (though
rather frequently, but to be fully sure one needs at least 10 boots)
results in "IoPageWrite() failed" during setup.
Herve already took a lot of time to try to track down the revision
number of the regression, however I'm not aware of his recent
achievements.
I would like to ask everyone (especially those who wants to become
testers :) ) to please help and find the revision number which has
this regression. Further commits can go only when this is fixed (the
concept of bootable trunk).
WBR,
Aleksey Bragin.
janderwald(a)svn.reactos.org wrote:
>
> + if (RegOpenKeyEx(HKEY_LOCAL_MACHINE,
> +
_T("SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\RunOnce"),
> + 0,
> + KEY_SET_VALUE,
> + &hKey) != ERROR_SUCCESS)
> + {
> + DPRINT1("Error: failed to open
HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\n");
There's a HKCU typo in the debug print.
Also, is this the correct place to be storing this info?
Ged.
On 08.11.2006 11:49:19 janderwald(a)svn.reactos.org wrote:
> Author: janderwald
> Date: Wed Nov 8 14:47:44 2006
> New Revision: 24701
> URL: http://svn.reactos.org/svn/reactos?rev=24701&view=rev
> Log:
> set most of trunk svn property eol-style:native
Please revert this change (or part of it): It's plain wrong to set
eol-style:native for files of type *.dsp, *.dsw, *.vcproj, *.sln and
some other files like chinese resource scripts.
Thanks,
Martin
--
Martin Fuchs
fuchs.martin(a)gmail.com
Hello,
I tried to to build trunk (rev.24696) with MP=1, but it doesn't build.
ntoskrnl\ke\ipi.c:27:2: #error VerifyMe!
ntoskrnl\ke\ipi.c: In function `KiIpiSendRequest':
ntoskrnl\ke\ipi.c:37: warning: implicit declaration of function `Ke386TestAndSetBit'
ntoskrnl\ke\ipi.c:53:2: #error VerifyMe!
ntoskrnl\ke\ipi.c:102:2: #error VerifyMe!
ntoskrnl\ke\ipi.c: In function `KiIpiServiceRoutine':
ntoskrnl\ke\ipi.c:108: warning: implicit declaration of function `Ke386TestAndClearBit'
ntoskrnl\ke\ipi.c:147:2: #error Not yet implemented!
mingw32-make: *** [obj-i386\ntoskrnl\ke\ipi.o] Error 1
Regards,
David (Quip)
---------------------------------
Sneak preview the all-new Yahoo.com. It's not radically different. Just radically better.
After wiping the "old" reactos.org box (the one at IP 130.161.165.129) and
reinstalling Apache so I can use it for other projects I found that there
are still some hostnames referring to the "old" box:
links.reactos.org
reactos.de
reactos.pl
www.reactos.dewww.reactos.pl
For the moment, I've set up redirection for (www.)reactos.de/.pl to
www.reactos.org/?lang=de/pl and I have reloaded the scripts for
links.reactos.org. I will terminate that service at the end of the month, so
please update DNS before that.
The critical one is links.reactos.org. The getfirefox applet will download
Firefox using the link http://links.reactos.org/getfirefox. The script
behind that URL will redirect to the "real" Firefox download location. This
was done so it was possible to update the script to newer Firefox versions
when they became available, without the need to recompile and redistribute
getfirefox. Same thing is happening for the Mozilla ActiveX control. When
links.reactos.org doesn't work anymore, this means getfirefox and the
automatic Mozilla ActiveX download will cease to work. I assume the scripts
were transferred already during the website move, if not I can provide them.
Oh, and please fix the alias for root(a)www.reactos.org, it still points to my
email address. I'm not interested in receiving that mail, a little while ago
there was an error in a script somewhere, causing it to send me an email
every ten minutes, 24 hours per day....
If there's a need to communicate about this, please email me directly, after
this email gets through I'm unsubscribing again.
Gé van Geldorp.
Brandon Turner wrote:
>
> D. Hazelton wrote:
> > (I once thought I might be able to help, but I am not used
> to writing C++ for
> > low-level interfaces - for those I've always used C)
> >
> > DRH
> >
> >
> Good thing our whole kernel and system lib set is in C. ;)
>
Pretty much the entire operating system ..... Lol
Hi
everyone have notice ReactOS website, svn, mailing list, went down.
The svn and web server was never down the problem was the
DNS server whent down by hardware failour and it took time
getting it back online again. Longer that we did expect.
I've tried fixing this! 8^(
include/psdk/winnt.h line 3666 is the orig.
[CC] subsystems/win32/win32k/dib/dib1bpp.c
In file included from subsystems/win32/win32k/w32k.h:16,
from subsystems/win32/win32k/dib/dib1bpp.c:20:
include/ddk/ntifs.h:404: error: redeclaration of `enum _AUDIT_EVENT_TYPE'
include/ddk/ntifs.h:405: error: conflicting types for 'AuditEventObjectAccess'
include/psdk/winnt.h:3666: error: previous definition of 'AuditEventObjectAccess' was here
include/ddk/ntifs.h:407: error: conflicting types for 'AuditEventDirectoryServiceAccess'
include/psdk/winnt.h:3668: error: previous definition of 'AuditEventDirectoryServiceAccess' was here
ion(a)svn.reactos.org wrote:
> Author: ion
> Date: Tue Oct 24 01:19:15 2006
> New Revision: 24636
>
> URL: http://svn.reactos.org/svn/reactos?rev=24636&view=rev
> Log:
> - Add NtApphelpCacheControl, NtFilterToken (WARNING: PATENTED. TAKE CARE WHEN IMPLEMENTING).
>
I'm assuming that the warning is in reference to NtFilterToken(). If
someone other than you goes to implement this function, they probably
won't look through svn history to see this comment. Wouldn't it be best
to put a warning like this in the comments of the function source?
> - RtlCopyMemory(StateChange,
> + /* Return our wait state change structure */
> + RtlMoveMemory(StateChange,
> &WaitStateChange,
> sizeof(DBGUI_WAIT_STATE_CHANGE));
RtlMoveMemory doesn't really make sense as the destination and source
are never overlapping, resulting in unnecessary overhead.
- Thomas
Aleksey Bragin wrote:
"It should try every revision, otherwise there is no
use from it at
all. And automerge from trunk to stable branch is not
possible,
because patches usually depend on each other."
Sorry,i explained myself wrong, i was not talking
about automerging, or using the "stable branch" to
send patches. No, patches would be still sent to the
unstable branch, and no "automerging will be used", it
will be just overwriting.
The process i imagine like this:
-Unestable not working.
-Recent Stable working (1 day old).
-You dont have the skill to fix unstable.
-You download stable, work in your computer over
stable.
-Send changes to unstable (then things become
interesting).
-Check the files you are have touched. If no other
person have touched them since the stable (1 day old)
was made you can send your patches, if someone have
touched, you cant and have to wait till the stable
revision is updated.
-Once unstable boot again, stable is override by the
unstable, and now named stable.
This would alow people working, maybe in the control
panel, with little kernel or booting code knowledge,
keep working without having to stop developing for
dificult bugs in the kernel.
What do you thing? Maybe is a crazy idea cause i dont
know about the inners of SVN.
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
> +;
> +; ROSBOOT_CMD
> +;
> +; This value is the command which is executed to gain debugging data
> +; this value is mandatory
> +
> +ROSBOOT_CMD=D:\sysreg\qemu\qemu.exe -serial file:debug.log
> -boot c -m 128 -L D:\sysreg\qemu\ D:\sysreg\qemu\RosVM.vmdk
> -cdrom D:\Reactos\ReactOS-RegTest.iso
Is there scope to add vmware to the test?
Ged.
janderwald(a)svn.reactos.org wrote:
> Author: janderwald
> Date: Fri Oct 20 19:49:46 2006
> New Revision: 24584
>
> URL: http://svn.reactos.org/svn/reactos?rev=24584&view=rev
> Log:
> * beginning of a system regression tools
>
Can this be done in C? C++ only slows down the build even more.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
I hate ugly text formatting ...
Resending in a (hopefully) readable format.
Jerry wrote:
> After a team says that it has fixed the bug ...
<snip>
> Each team may have mentees associated with it. The teams would then
> help and guide their mentees in testing and coding, and these mentees
> will help with the work load that the regular testers have. The goal
> here is to guide the mentees to be regular developers and either stay
> in testing or move on to other parts of the project and have.
I'm a little confused with the idea of the testing teams fixing bugs.
Testers aren't usually coders. It's great if they are as they can fix the
bugs they find, but in general testing positions are filled by people who
want to help the project, but aren't programmers.
If a tester is a programmer too, I think you'll find that do a lot more
programming than testing, as shown by our tree instability at the moment ;)
Ged.
Jerry wrote:
> After a team says that it has fixed the bug ...
<snip>
> Each team may have mentees associated with it. The teams would then
help
> and guide their mentees in testing and coding, and these mentees
will help
> with the work load that the regular testers have. The goal here is
to guide
> the mentees to be regular developers and either stay in testing or
move on to
> other parts of the project and have.
I'm a little confused with the idea of the testing teams fixing bugs.
Testers aren't usually coders. It's great if they are as they can fix the
bugs
they find, but in general testing positions are filled by people who want to
help the project, but aren't programmers.
If a tester is a programmer too, I think you'll find that do a lot more
programming
than testing, as shown by our tree instability at the moment ;)
Ged.
Hi,
I'm interested in the Testing Coordinator position. A few ideas I have for
testing in general are,
1) One step update and compile
2) Divide and conquer testing.
Testing would be divided up into teams. Each team will have its own leader.
Each team will be assigned (or assign themselves) a mixed slate of verified
unverified bugs. After a team says that it has fixed the bug or the bug is a
false positive, another team will come and verify their findings. All this
activity will be logged as it happens.
3) Testing Mentor Program
Each team may have mentees associated with it. The teams would then help
and guide their mentees in testing and coding, and these mentees will help
with the work load that the regular testers have. The goal here is to guide
the mentees to be regular developers and either stay in testing or move on to
other parts of the project and have. The goal of this project is to grow the
4) I will try to listen and consider any ideas that other people have and try
to work with people instead of against them.
If you have any questions, be free to ask. I hope to be able to serve this
project better.
Even if i am not a developer in this proyect, may I give an advice?
1) You need two trunks, one experimental, the other 1 day old "booting trunk".
2)Your bot build the experimental trunk (you already have the build bot).
3) Once a day a "boot bot" would try boot the experimental trunk, if it is sucessful (i supouse, sending a "all ok" message throug com1) then it overwrithe the "booting trunk" with that experimental revision.
4)That way there is always a very recent trunk that is stable enough to boot, the testing is automatic, and you have quite narrowed the revisions with the problem.
That way you could be working in a somewhat stable trunk, that can not be older than 1, 2 or 3 days if the experimental is failing.
Best Regards,
Lucio Diaz-Flores
---------------------------------
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Ok, please don't shoot me if this is 'to large a request' for what im
offering, or to little. But here goes..
World of Warcraft on ReactOS, w/ NVidia Drivers AND guide complete to
logging in and speaking with some NPC's (from what i understand the
latest wine works well with WoW as far as right clicking, correct me
if im wrong)
Beings as i dont know how much work will be involved, what im offering
is a copy of WoW to the DevTeam, (or you can use a 10 day trial free
from Blizzard) and a $50/Bounty upfront. If this amount is to low,
willing to go as far as $150/total, mind you i fall under the
'student' classification.
Other then the mentioned, i would also like windowed mode to work (my
preferred). And i use a NVidia Card.
Thank you.
--
~Rob
http://sn0n.com/