It is possible to compile with this flag, but you need to build it
yourself then. Official ISOs are compiled with leanandmean set to no.
WBR,
Aleksey Bragin.
On Jun 11, 2007, at 1:06 PM, carlo.bramix wrote:
> Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"?
> If not, is it possible to compile it with this flag?
> For other purposes beside the normal user testing, we have the SVN
> DEB Live CD image.
>
> Sincerely,
>
> LDChen
Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"?
If not, is it possible to compile it with this flag?
For other purposes beside the normal user testing, we have the SVN DEB Live CD image.
Sincerely,
LDChen
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
Hi Lucio,
I must say, that there were a lot of efforts to get our tools working as
easy as possible. Even a global login system was introduced way back so that
you don't need to create an account for wiki, for bugzilla, for forum, for
wiki, for the main website - you just create one. A lot of time was spent in
order to do this (every piece of software needed to be customised - Ge and
Klemens put a lot of their personal time into this).
I will answer between the lines below so it makes better sense.
----- Original Message -----
From: "Lucio Diaz" <reactos_translate(a)yahoo.es>
To: <ros-dev(a)reactos.org>
Sent: Tuesday, April 17, 2007 2:08 AM
Subject: [ros-dev] About translation
-= skip =-
> -Many like me can install SVN, and get the source
> code, but never have made a patch, or even used
> bugzilla(and probably wont have the time).
If a contributor has SO small time that he can't even submit his work to a
bugzilla or, at least, send a patch to a relevant person (the same language
native speaker developer or another translator who has more time), then it's
better to wait when he/she has more free time to contribute.
-= skip =-
> files, but sending them to bugzilla... i dont know how
> to send them to bugzilla, i dont have a bugzilla
> acount, it was tiring trying to find someone to send
> the files, and i dont have the time or will to learn
> bugzilla.
That shows you really did not even slightly investigated how the website
works. And instead you're proposing a whole workflow for developers, so they
mandatory spent a few hours per week maintaining all the stuff you.
During that 2 years you should have spent just a bit of time, even 20
minutes, to overview our website and systems we have there, and another 20
minutes to read online manuals/help for them. Excuses like "I didn't have
time" hardly apply here.
WBR,
Aleksey Bragin.
Hi,
I set up a Chatroom for RosBE (Windows/Linux) specific questions. Its on
Freenode and is called #reactos-rosbe. I dont know if its so useful, but
I was bored and thought this could be useful.
Bye.
Actually, I removed the hack from IopCreateDriver, and added a loop
to prevent creation of drivers with the same name (which actually
have no impact on the servicekeynode).
What is the real cause of a double free? And which hack are you
referring to in IopCreateDriver?
WBR,
Aleksey Bragin.
On May 25, 2007, at 9:10 PM, dgorbachev(a)svn.reactos.org wrote:
> Author: dgorbachev
> Date: Fri May 25 21:10:11 2007
> New Revision: 26893
>
> URL: http://svn.reactos.org/svn/reactos?rev=26893&view=rev
> Log:
> Do not free the string twice.
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/driver.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/driver.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/
> iomgr/driver.c?rev=26893&r1=26892&r2=26893&view=diff
> ======================================================================
> ========
> --- trunk/reactos/ntoskrnl/io/iomgr/driver.c (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/driver.c Fri May 25 21:10:11 2007
> @@ -79,12 +79,14 @@
> ExFreePool(DriverObject->DriverName.Buffer);
> }
>
> +#if 0 /* See a bit of hack in IopCreateDriver */
>
When building the release versions of executables, DLLs, etc, I would suggest to add the "-s" switch to the linker flags.
It will do stripping automatically and release-mode objects will be a bit smaller.
Alternatively, we could "strip -s file.exe" but just adding the flag would be much simpler.
Sincerely,
Carlo Bramini.
------------------------------------------------------
Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom
http://click.libero.it/infostrada
>From livecd-26861-rel it runs again under QEMU.
Last tested image is livecd-26871-rel.
Great job!
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ros-dev" ros-dev(a)reactos.org
Cc :
Date : Fri, 11 May 2007 17:21:55 +0200
Subject : Re: [ros-dev] QEMU support broken!!!
> I just wanted to tell you that I downloaded and tested livecd-26700-rel.7z and it doesn't work yet.
>
> Sincerely,
>
> Carlo Bramini
>
> ---------- Initial Header -----------
>
> >From : ros-dev-bounces(a)reactos.org
> To : "ReactOS Development List" ros-dev(a)reactos.org
> Cc :
> Date : Fri, 11 May 2007 07:16:05 +0000
> Subject : Re: [ros-dev] QEMU support broken!!!
>
> > I also have a problem with booting LiveCD.
> > Bugcheck in cmcontrl.c, line 151.
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
> ------------------------------------------------------
> Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom
> http://click.libero.it/infostrada
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom
http://click.libero.it/infostrada
Hi!
> It should probably be
> + Exp -= (1 - EXCESS);
> in EFtoF() and
> + Exp += (1 - EXCESS);
> in FtoEF(). The other way round.
>
>
No, this would break compatibility. The way to verify this. Write a
driver, install it
and send a packet to it, so to activate the test. Have the driver dump
to WinDbg.
> Suggestion to make it a little clearer:
> #define BIAS 127
> Exp -+= (BIAS - 2);
I know about the IEEE bias. I'm just using my old 68k code that I'm
comfortable with. I'll
change this later with the Dc handle stuff I'm still testing.
Thanks,
James
Hi all,
On or about September 2006 I was asked by Aleksey (PC) and Alex if I could head up
the win32 and gdi32 part of the rewrite. The discussion had taken place on irc. It
was important that the rewrite would have one developer working alone (preferred
method) or be the leading developer working with a small group of developers (no
more than three). The rewrite was needed so that this section of ReactOS would be
compatible with the new kernel and the very thing we are trying to do. Be
compatible. This included interfaces, structures and the data that was contained in
those structures. Just not only that, also dropping in the place of drivers and
dlls, the real thing and still be compatible. Yes! Running with ReactOS.
I do not recall any requirement for me to write a technical manual or any kind of
web wiki. Even a How-To-Black-Box an OS interrupt calling hooky thingy with kmtest
driver callback winpooch as an application interface. ReactOS developers should have
a healthy tool box.
This point on, the discussion is over. I have a job to do. I would like help and not
debate everything I do. Some of you, need to, really think about, the future of this
project. How can I help with this and how can I help make this work for
compatibility with the very thing we are working toward. If you are thinking about
something new and different other than something innovative, compatible and helpful?
Maybe this project is not for you. Aros, FreeMint, Linux, Syllable, Visopsys, X,
etc, these projects might be what you are looking for.
If it breaks compatibility with interfaces and data stored in structures? I will
reject it and post an email why it was rejected. Wine is not enough, okay?
Thanks,
James
Unfortunately, I just tested it into the latest working SVN build under QEMU (livecd-26665-rel) and this bug it is still into the CRT library.
I also read the source code with SVN-WEB and it's still the same of 0.3.1.
BTW, from livecd-26771-rel, a bad thing happens with QEMU: immediately after starting the boot, a blu screen appear with errors and everything is dead.
Sincerely,
Carlo Bramini
----------
This bug have already been fixed by me.
log time ago. some time after 0.3.1 was relase or under 0.3.1 release process.
plese use svn source code, and try make own build of reactos as well. the trunk is changes so fast, the code in 0.3.1 is already outdated in many areas.
Citerar "carlo\\.bramix" <carlo.bramix at libero.it>:
> While I was doing the final tests with ReactOS Calc before releasing the new
> version, I discovered that it didn't work because a bug into log10 function.
> This happens because the two operands are swapped into:
>
> \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s
>
> I attached the patch.
>
> Sincerely,
>
> Carlo Bramini.
>
>
>
>
> ------------------------------------------------------
> Leggi GRATIS le tue mail con il telefonino i-mode di Wind
> http://i-mode.wind.it/
>
>
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
>> - At the boot screen, the version compiled under Windows shows
>> "Service Pack 1" correctly, but the version compiled under Linux
>> shows "Service Pac 1"
>
> I see this "Service Pac 1" in ReactOS compiled under Windows with GCC 4.1.2 (from RosBE).
In ExpInitializeExecutive():
...
ANSI_STRING CsdString;
...
RtlInitAnsiString(&CsdString, MsgEntry->Text);
CsdString.Length -= sizeof(UNICODE_NULL);
...
Why Unicode?
Hi All
Latest revisions of ReactOS produces compilation error at my system.
Build Environment:
RosBE 0.3.5b2
File:
boot\freeldr\freeldr\reactos\reactos.c
Error message (after 'make clean' and 'make'):
cc1.exe: warnings being treated as errors
boot\freeldr\freeldr\reactos\reactos.c: In function 'LoadAndBootReactOS':
boot\freeldr\freeldr\reactos\reactos.c:524: warning: dereferencing
type-punned pointer will break strict-aliasing rules
mingw32-make: *** [obj-i386\boot\freeldr\freeldr\reactos\reactos.o] Error 1
WBR,
DarkHobbit
Sorry net split on irc.
Physicus r26742 is right,,, I will change it this week once I have the rest of my changes ready. We
should support 0x00010000 - 1 = 0xffff handles and it will give us 65K.
Thanks
James
Hello,
After the latest Kernel changes, I noticed some differences in ReactOS
builds compiled under Windows (RosBE 0.3.4) and under Linux (BuildBot and my
32-bit Ubuntu system):
- At the boot screen, the version compiled under Windows shows "Service Pack
1" correctly, but the version compiled under Linux shows "Service Pac 1"
- The version compiled under Linux hangs at "Flushing cache" for me, when I
test it under VMware.
Some other users also wrote that they could not run the latest ReactOS
builds under QEMU.
Although, I could not reproduce this problem with r26719, it might be
related to these build differences.
As I don't know, where this problem might originate from, maybe someone else
could look at it.
Regards,
Colin
I just wanted to tell you that I downloaded and tested livecd-26700-rel.7z and it doesn't work yet.
Sincerely,
Carlo Bramini
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Fri, 11 May 2007 07:16:05 +0000
Subject : Re: [ros-dev] QEMU support broken!!!
> I also have a problem with booting LiveCD.
> Bugcheck in cmcontrl.c, line 151.
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom
http://click.libero.it/infostrada
The last SVN builds don't run under qemu.
The last working image is livecd-26665-rel.iso
It looks like something wrong has been changed in the last 24 hours.
Sincerely,
Carlo Bramini.
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
Sorry, but before writing this messages I tested *ALL* SVN releases from livecd-26660-rel.7z to livecd-26672-rel.7z (except livecd-26671-rel.7z).
I also tested livecd-26626-rel.7z and livecd-26650-rel.7z and they both worked (when I saw that livecd-26670-rel didn't work, I started with checking something older...).
Here the last working version is still livecd-26665-rel.iso.
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Thu, 10 May 2007 17:43:22 +0400
Subject : Re: [ros-dev] QEMU support broken!!!
> Hello,
> the problem was introduced in 26666 and successfuly fixed in 26668
> (read commit logs for more details).
>
>
> WBR,
> Aleksey Bragin.
>
> On May 10, 2007, at 4:47 PM, carlo.bramix wrote:
>
> > The last SVN builds don't run under qemu.
> > The last working image is livecd-26665-rel.iso
> > It looks like something wrong has been changed in the last 24 hours.
> >
> > Sincerely,
> >
> > Carlo Bramini.
> >
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
Hello,
the problem was introduced in 26666 and successfuly fixed in 26668
(read commit logs for more details).
WBR,
Aleksey Bragin.
On May 10, 2007, at 4:47 PM, carlo.bramix wrote:
> The last SVN builds don't run under qemu.
> The last working image is livecd-26665-rel.iso
> It looks like something wrong has been changed in the last 24 hours.
>
> Sincerely,
>
> Carlo Bramini.
>
Wouldn't it be better if we got our act together from like minded groups. Crystalxp.net group's offering of Bricopacks http://www.crystalxp.net/bricopack/en.htm which mimics the look and feel of Vista. Is ReactOS ready for such an integration ?
Plus, can this auditing be distributed and shared ? I have set up a group of volunteer professionals to work on ReactOS.
CK Raju
ros-dev-request(a)reactos.org wrote: Welcome to the Ros-dev(a)reactos.org mailing list!
---------------------------------
Office firewalls, cyber cafes, college labs, don't allow you to download CHAT? Here's a solution!
Hi,
You actually have to define YDEBUG to see messages produced by DPRINT()
If NDEBUG is defined (default), no message is shown.
DPRINT1 is used in case of error/ fix needed.
Kind regards,
Sylvain Petreolle (aka Usurp)
--- --- --- --- --- --- --- --- --- --- --- --- ---
Run your favorite Windows apps with free ReactOS : http://www.reactos.org
Listen to non-DRMised Music: http://www.jamendo.com
----- Message d'origine ----
De : "breakoutbox(a)web.de" <breakoutbox(a)web.de>
À : Ros-dev(a)reactos.org
Envoyé le : Jeudi, 19 Avril 2007, 16h21mn 55s
Objet : [ros-dev] DbgPrint() - DPRINT() - DPRINT1()
Hello,
can please anybody explain me how You want DbgPrint() - DPRINT() - DPRINT1() to be used ?
I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but it is not shown on serial debug (?)
(and also SOME ot these DPRINT1() .. )
1)
If I use DPRINT1() instead, it is always shown.
If I use DbgPrint() instead, it is only shown when #DEBUG is defined in the file + in *.rbuild
But what's the sense of DPRINT() then ?
=>
2)
2nd stage: on installing from BootCD I can see serial debug only when I select DEBUG from startup options.
Is this DPRINT1() suppressed when I DON'T select DEBUG ?
3)
Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in other files in /DRIVER/ and /NTOSKRNL/ ..) ?
I now have to change every serial debug output to be able to see anything .. ( if You don't explain me ... ;-) )
Best regards,
Peter.
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev