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