Sorry to be nudging about this but:
Will the newly ported wrc.exe & widl.exe be a part of the binutils
(Binary & Source) packages available on SourceForge.net ReactOS project?
Free Life
Boaz
Hello!
I have just updates to the latest SVN version and now I have the problem, that I cannot install ReactOS anymore.
At the first reboot after installation, I get the following Assertion (cut from debug output):
(devinst.c:1008:SetupDiInstallClassW)
Assertion 'NewDC->DMW.dmBitsPerPel == BitsPerFormat(SurfObj->iBitmapFormat)' fai
led at objects/dc.c line 808
Entered debugger on embedded INT3 at 0x0008:0x80006243.
When I ignore this Assertion (by continuing), I can do so serveral times, after that my PC reboots. The error occurs on both QEMU and real HW.
I guess this error has something to do with the latest changes. Perhaps someone can verify/fix this (GvG ?).
I discoverd one or two other problems too (that have nothing to do with the latest SVN build), but I have to recheck them to ensure they still exist.
This is what I've done: I have clicked wildly with the right mouse button on the Desktop background to open the context menu and randomly used the context menu of the Explorer to move the Explorer windows arround in between.
When I do this for a couple of seconds, ReactOS crashes. (I posted a BSOD yesterday in IRC, but I guess nobody noticed it, here is the link:
http://www.rafb.net/paste/results/kxur3L28.html
As I said, I will recheck this in the evening today. Perhaps someone else will have a look on this too.
Best regards,
Dolphin
each test was run from a "mingw32-make clean" or "make clean" tree with
KDBG=0 DBG=0
old build system build command:
mingw32-make
mingw32-make bootcd
21 minutes
new build system:
make bootcd
11 minutes
new build system:
make -j 5 bootcd
13 minutes
I built the old build system with two separate commands because last
time I tried, you could do a "mingw32-make bootcd" from a clean tree.
So, besides the other benefits outlined when we started this project,
the new build system is cutting build time in half.
Now to just fix the remaining bug(s) ;)
I want to change the usermode exception reporter to make stack
traces in this form:
(KERNEL32:except/except.c:184) 6dc00000+cb991 C:\dl\libgtk-0.dll
rather than this from:
(KERNEL32:except/except.c:184) 6dccb991 C:\dl\libgtk-0.dll
My form is less compact but gives more information (namely, the offset in
the target module). It's a simple change but I wanted to see if anyone
objected strongly.
--
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman
Hi,
Robert if you are out there I think we want to try to branch for 0.2.6 sometime in the middle of
the coming week. Alex is going to merge his changes in to the trunk and then we should be mostly
ready. If Robert is not free and no one else wants to do it then I will plan on branching on
Wednesday. I expect we can let the 0.2.6 branch run for about a week so lets plan on shipping
0.2.6-final on 2005/03/16.
Thanks
Steven
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
Hi,
since my last svn update, I'm not able to compile ros on ros. It seems
that something is wrong with the pipes.
- Hartmut
f:\Sandbox\Ros\ReactOS>_make
ReactOS Build Number Generator
Current date : 2005-03-06
ROS Version : 0.3-CVS (build 20050306)
ar: creating zlib.host.a
ntoskrnl: [DLLTOOL] libntoskrnl.a
hal: [CC] hal.c
gcc: pipe: Invalid argument (EINVAL)
_make[1]: *** [hal.o] Error 1
_make: *** [hallib] Error 2
Hi,
compiling fails if KDBG = 0 and DBG = 1.
objects/ke.o: In function `InitializeListHead':
M:/Sandbox/ros_work/reactos/ntoskrnl/../include/ntos/rtl.h:96: undefined
reference to `KdbInit'
objects/ps.o: In function `PsUnlockProcess':
M:/Sandbox/ros_work/reactos/ntoskrnl/ps/process.c:2973: undefined
reference to `KdbDeleteProcessHook'
collect2: ld returned 1 exit status
_make[1]: *** [ntoskrnl.nostrip.exe] Error 1
_make: *** [ntoskrnl] Error 2
- Hartmut
blight(a)svn.reactos.com schrieb:
>Little KDB update ;-) If you have any problems and/or questions let me know. I hope it was tested enough and works well enough for everybody.
>
>
>Added files:
>trunk/reactos/media/drivers/etc/KDB.init
>trunk/reactos/ntoskrnl/dbg/i386/longjmp.S
>trunk/reactos/ntoskrnl/dbg/i386/setjmp.S
>trunk/reactos/ntoskrnl/dbg/kdb_cli.c
>trunk/reactos/ntoskrnl/dbg/kdb_expr.c
>trunk/reactos/ntoskrnl/dbg/kdb_string.c
>
>Updated files:
>trunk/reactos/Makefile
>trunk/reactos/drivers/input/keyboard/keyboard.c
>trunk/reactos/ntoskrnl/Makefile
>trunk/reactos/ntoskrnl/dbg/i386/i386-dis.c
>trunk/reactos/ntoskrnl/dbg/i386/kdb_help.S
>trunk/reactos/ntoskrnl/dbg/kdb.c
>trunk/reactos/ntoskrnl/dbg/kdb.h
>trunk/reactos/ntoskrnl/dbg/kdb_keyboard.c
>trunk/reactos/ntoskrnl/dbg/kdb_serial.c
>trunk/reactos/ntoskrnl/dbg/kdb_symbols.c
>trunk/reactos/ntoskrnl/include/internal/i386/ke.h
>trunk/reactos/ntoskrnl/include/internal/kd.h
>trunk/reactos/ntoskrnl/ke/catch.c
>trunk/reactos/ntoskrnl/ke/i386/trap.s
>trunk/reactos/ntoskrnl/ke/i386/tskswitch.S
>trunk/reactos/ntoskrnl/ke/kthread.c
>trunk/reactos/ntoskrnl/ke/main.c
>trunk/reactos/ntoskrnl/ps/w32call.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
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/
Hi Harmunt:
I remember the solution for this was Bochs + Hardisk images using sparse files.
From: ros-dev-bounces(a)reactos.com on behalf of Hartmut Birr
Sent: Wed 3/2/2005 3:01 PM
To: ReactOS Development List
Subject: Re: [ros-dev] Changelog 0.2.6 Release.
michael(a)fritscher.net schrieb:
>Hmm, I think we shouldn't release 0.2.6 until ros can boot from the first
>128 GB from a over 128 GB HDD again, because I think that's a big
>regression
>
>
Hi,
I can implement the large LBA addressing mode in atapi. But I cannot
test it, because my largest ide disk is only 120GB.
- Hartmut
Hi!
What is the output (with the changed line) when the key is pressed, whithout a modifier key, with shift, with caps lock, with caps lock + shift and with alt gr?
Regards
Johannes Olofsson
> Från: Roman Hoegg <roman.hoegg(a)unisg.ch>
> Till: ReactOS Development List <ros-dev(a)reactos.com>
> Rubrik: Re: Re: [ros-dev] added a proposed patch to bugzilla
> Datum: Wed, 2 Mar 2005 20:58:46 +0100
> Try to change the line :
> /* none, shift, ctrl-alt, ctrl, ctrl-shift */
> { VK_OEM_7, NOCAPS, 0xe4, 0xe0, 0x7b, WCH_NONE, 0x00 }, /* ä à { */
> to:
> { VK_OEM_7, KCTRL, 'code for ä', 'code for à', 0x7b, 'code for Ä', 'code for À }, /* ä à { */
> in order to use the ctrl and ctrl-shift states for caps lock for this key.
thanks for the help. What you suggest here actually works (I've just tested it).
However, what it does is it makes Ctrl to behave the way CapsLock should behave and turns CapsLock into AltGr (strange...). That's not how my keyboard acts on other OS'. I really think there should be a way to differentiate between CapsLock and Shift. I'm sure that there will also be other keyboards that need that in the future.
thanks!
Roman Högg_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
Otur i kärlek - http://www.spray.se/spel Tur i kärlek - http://www.spraydate.com
Hi,
Actually this is a designed behavior of -Wconversion and not a bug.
http://gcc.gnu.org/ml/gcc/2002-12/msg01431.html
--
d_layer
arty(a)svn.reactos.com wrote:
> + * <rant>
> + * These fix the following warning in GCC:
> + * warning: passing arg 1 of `ntohs' with different width due to
> prototype
> + *
> + * Even if you declare an unsigned char or unsigned short variable and
> pass
> + * it to htons or ntohs, this warning will be generated. I believe
> this is
> + * a gcc bug. You can try to reproduce the bug like this:
> + *
> + * u_short foo(u_short bar) {
> + * return htons(bar);
> + * }
> + *
> + * Using the reactos compiler settings this generates the error.
> Unless I'm
> + * missing something, the active prototypes for htons and ntohs are:
> + *
> + * u_short PASCAL htons(u_short);
> + * u_short PASCAL ntohs(u_short);
> + *
> + * From winsock2.h. Since the function above has exactly the same
> signature
> + * as htons except for the required PASCAL (__stdcall) decoration, gcc
> is
> + * erroneously detecting a narrowed value.
> + * </rant>
ion(a)svn.reactos.com wrote:
>Fix queue item not being cleaned. Thank you Jim
>
>Modified: branches/alex_devel_branch/reactos/ntoskrnl/ke/queue.c
>
>
> ------------------------------------------------------------------------
> *Modified: branches/alex_devel_branch/reactos/ntoskrnl/ke/queue.c*
>
>--- branches/alex_devel_branch/reactos/ntoskrnl/ke/queue.c 2005-03-04 04:10:03 UTC (rev 13812)
>+++ branches/alex_devel_branch/reactos/ntoskrnl/ke/queue.c 2005-03-04 04:15:46 UTC (rev 13813)
>@@ -207,7 +207,7 @@
>
>
> /* Remove the Entry */
> RemoveEntryList(ListEntry);
>
>
>- Entry->Flink = NULL;
>
>
>+ ListEntry->Flink = NULL;
>
>
>
> /* Nothing to wait on */
> break;
>
>
This looks wrong. You should never clean list item this way, instead you
should use "InitializeListHead(ListEntry);".
- Filip