I'm getting this after merging...
Filip/Eric, this seems to be related to your changes...any clue?
Assertion Irp->CancelRoutine == NULL failed at io/irp.c:310
Best regards,
Alex Ionescu
Hi Alex!
Good job! I let the testing go on through the night (23 hours) and started
testing your last commit, it's running great!
ion(a)svn.reactos.com wrote:
> Merge with blight's rewrite
>
>
> Added files:
> branches/alex_devel_branch/reactos/media/drivers/etc/KDB.init
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/longjmp.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/setjmp.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_cli.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_expr.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_string.c
>
> Updated files:
> branches/alex_devel_branch/reactos/Makefile
> branches/alex_devel_branch/reactos/drivers/input/keyboard/keyboard.c
> branches/alex_devel_branch/reactos/ntoskrnl/Makefile
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/i386-dis.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/kdb_help.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb.h
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_keyboard.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_serial.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_symbols.c
> branches/alex_devel_branch/reactos/ntoskrnl/include/internal/i386/ke.h
> branches/alex_devel_branch/reactos/ntoskrnl/include/internal/kd.h
> branches/alex_devel_branch/reactos/ntoskrnl/io/iomgr.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/catch.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/i386/trap.s
> branches/alex_devel_branch/reactos/ntoskrnl/ke/i386/tskswitch.S
> branches/alex_devel_branch/reactos/ntoskrnl/ke/kthread.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/main.c
> branches/alex_devel_branch/reactos/ntoskrnl/ps/w32call.c
>
BTW, I'm getting this;
ntoskrnl: [CC] ke/kthread.c
ke/kthread.c: In function `KeInitializeThread':
ke/kthread.c:254: error: too many arguments to function `RtlZeroMemory'
ke/kthread.c:266: error: too many arguments to function `RtlZeroMemory'
ke/kthread.c:267: error: too many arguments to function `RtlZeroMemory'
make[1]: *** [ke/kthread.o] Error 1
make: *** [ntoskrnl] Error 2
Thanks,
James
Hi guys:
I was reading about subversion an in fact installed one svn server because I think that I could benefict from using a versioning system even doing non collaborative programming. Now the part that is related with ReactOS is that svn can be used locally, lite svnserve and (apache + svn modules) concurrently. I beleive you are using only or mostly:
svn://svn.reactos.com/
Are there any chances for us the firewalled to get an apache 2.x listening on port 80? I know you are using apache 1.3.x in www.reactos.com but the configuration should be very similar. I never mentioned anything like this when CVS because it was probably too wuch work for those administrating CVS but hey SVN is modern so it comes ready for it with little effort. So it won´t affect those using the subversion protocol directly. I always had intention to collaborate but never got the chance. I could never do proper checkouts from CVS using tunnels but this way will be direct so probably this could be my chance to get in and maybe get write acces after learning more about svn using it locally on my machine.
Thanks in advance
Regards Waldo Alvarez
There is no need to update this branch since I'll merge changes from
trunk once in a while. Also, always be sure to use svn merge to merge
changes from trunk to the branches so subversion knows where the
changes comes from. If done, then we are less likely to get conflicts
in a future merge.
Casper
> -----Original Message-----
> From: ros-svn-bounces(a)reactos.com
> [mailto:ros-svn-bounces@reactos.com] On Behalf Of mf(a)svn.reactos.com
> Sent: 5. marts 2005 18:52
> To: ros-svn(a)reactos.com
> Subject: [ros-svn] [mf] 13830: add ibrowser to XML build
>
> add ibrowser to XML build
>
>
>
> Added files:
> branches/xmlbuildsystem/reactos/subsys/system/ibrowser/ibrowser.xml
>
> Updated files:
> branches/xmlbuildsystem/reactos/bootdata/packages/reactos.dff
> branches/xmlbuildsystem/reactos/subsys/system/directory.xml
> branches/xmlbuildsystem/reactos/subsys/system/ibrowser/Makefile
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-svn
Thanks - but this should be 0.2.6 shouldn't it?
Jason
On Sat, 5 Mar 2005 16:38:22 +0100, mf(a)svn.reactos.com
<mf(a)svn.reactos.com> wrote:
> tag ReactOS 0.2.5 release
>
> Added files:
> tags/ReactOS-0.2.5/
When he merges with the tip I am really ready for 0.2.6
Thanks
Steven
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
make clean needs unicode and wpp atm,
this is why it does :
unicode&wpp compilation
[clean process]
but at the ends it does:
wpp&unicode clean
Every time you run make clean,
unicode& wpp are removed & compiled,
even if you didnt compile anything else !
Sh(C)ouldnt we avoid this ?
=====
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi all
I have a situation, under QEMU, when ACPI loading when ACPI=0 is
specified in the config file. The problem is that the acpi.sys driver
is crashing. When booting from the boot CD everything works properly
(not sure if acpi.sys is loaded) and ReactOS installs. But booting
from that installation sees the failed acpi.sys.
Is there something about our installation process that ignores ACPI=0
in the config file?
Thanks
Jason
royce(a)svn.reactos.com wrote:
>per-module clean rules, make cabman more *nix/msys friendly
>This fix made it so I was able to successfully build a 22.4MB ReactOS.iso from the xmlbuildsystem branch! ( now to test it... )
>
>
The bootcd fails to boot because freeldr.sys and setupldr.sys are
missing out of the LOADER block of the ISO.
I'm sure we're just not passing the right parameters, but I'm going to
bed, so if someone gets a chance to look at it... we may have a working
bootcd from the xml build system before the end of this weekend.
Kudos to Casper!!!
at the time I did not know what /BOOTLOG did vs /DEBUGPORT=FILE
This patch corrects it. Its verses Alexs tree as my main ReactOS tree is hosed. Someone please
apply to the trunk.
Thanks
Steven
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/