I would like to see a 0.2.7 release soon. 0.3.0 is getting closer
every day, but it's not there yet IMHO. On the other hand, we have
had lots of big patches from Mr. Ionescu (and others), major changes,
go in and appear to be stable since we have released 0.2.6. I would
like to see us have another release in this lull, instead of having a
release right after committing a pile of patches *right before* the
release like we did with 0.2.6.
I know it's been less than a month since 0.2.6, but my the time we
branch and do a couple RC's, it will have been over a month.
I just have this feeling that we miss some regressions from release to
release, since alot of us just use HEAD on a regular basis?
Just my $0.2US
WD
--
"<tinus_> and also win32k should be fixed up a bit"
ion(a)svn.reactos.com wrote:
>Change optimization settings for retail builds. Change to -Os for smaller executables which are not slower, and enable more advanced optimizations. funitatatime is already included by default in GCC 4.0. Strip debug info from retail builds, since we don't parse the symbols anyways. I hope these options don't break anything, they don't for me; Debugging is unaffected.
>
>
The direct result of this is that, for non-debug builds (which don't
support reading data from symbols anyways, not even during bugcheck),
the following data are now true:
1) ntoskrnl is 612kb on my system, down from 1.5MB
2) win32k is 316kb on my system, down from 800kb
3) taskmgr shows 6% idle cpu time, down from 9%
4) memory usage shows 32MB, down from 40MB+
5) total ISO size is now 12.5MB, down from 14.2MB.
Booting up the system to be much faster and everything is more
responsive, probably due to the smaller size and new optimizations.
Nothing has changed for DBG builds.
Best regards,
Alex Ionescu
hbirr(a)svn.reactos.com wrote:
>- Set the IOSB on error for async irp's with a sync FO (fix bug #609).
>
>
>
Clearly, the problem is that someone is reading the Iosb instead of
reading the FileObject->FinalStatus.
Do you know who is doing that? Fixing the caller would fix the bug,
instead of adding the hack into the IRP Code.
Thanks for the commit,
Best regards,
Alex Ionescu
> From: weiden(a)svn.reactos.com
>
> more fixes for GCC4
>
> Updated files:
> trunk/reactos/tools/wrc/lex.yy.c
Hmm, this is going to be a problem, lex.yy.c is a generated file.
Gé van Geldorp.
You will likely need to remove the w32api directory before you "svn up" next time.
Casper
> -----Original Message-----
> From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of
> chorns(a)svn.reactos.com
> Sent: 8. maj 2005 19:43
> To: ros-svn(a)reactos.com
> Subject: [ros-svn] [chorns] 15140: Delete old w32api
>
> Delete old w32api
>
>
> Deleted files:
> trunk/reactos/w32api/
You are really abusing the version control system here.
By not using a vendor import for the external project w32api, you make it much harder to keep local changes separate from the
non-local changes to w32api and thus complicating the synchronization of the two. This is what Gé is currently doing with the shared
wine code and eventually all external code should be imported this way to minimize maintenance.
By re-importing the data from trunk instead of merging it from trunk, you effectively screw up the versioning. When the time comes
to merge your changes to trunk, you cannot since there is no common history. The only way to get it to trunk is to use "svn delete"
and "svn copy" and thus you loose any changes made to include/ and w32api/ on trunk since you created the branch.
I'd suggest you read Gé's introduction at http://reactos.com/wiki/index.php/Using_code_from_other_projects and
http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-4 and do it this way instead.
Casper
> -----Original Message-----
> From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of
> ion(a)svn.reactos.com
> Sent: 8. maj 2005 03:31
> To: ros-svn(a)reactos.com
> Subject: [ros-svn] [ion] 15097: Wipe out current includes to start fresh.
>
> Wipe out current includes to start fresh.
>
>
> Deleted files:
> branches/new_headers/reactos/include/
> branches/new_headers/reactos/w32api/
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-svn
I just loaded reactos with svn 15089 , built during the night , and
networking is completely broken.
I cannot ping my dsl router ( request timeout )
Regards
Gerard
Copied from the archive because I will receive the mail in some hours:
>hbirr at svn.reactos.com wrote:
>>- Guard the copying to the IOSB.
>>- Do the main processing on success or if previous STATUS_PENDING was
returned.
>> Do not use some of the IRP and FO flags at this point.
>>
>>
>Ok, I was going to complain about this, but I realize that it must be
>used since defintely some parts of ROS don't work properly with those
>flags set.
It isn't possible to use the flags, because some functions are always
synchronous independently which flags are set. Ntoskrnl may set the
flags correctly, but a driver may possible not.
>>- Set all results before signaling the events.
>>- Signal the FO event previous the user event.
>>- Made the code a little bit shorter.
>>
>>
>>
>I like your changes and have no complaints, except that the signaling
>semantics of the File/User events should be different in the failure
>case (my "else" path). You've completely removed that path and thus
>changed the logic.
If the driver has returned STATUS_PENDING and completes the irp later
with an error, both events must be signaled, because two different
threads may waiting on this events. The IOSB must be also set. The apc
must be also deliver (I've tested this with the apc sample and some
modifications on windows). There is no difference between completing the
irp with and without an error if the driver has returned STATUS_PENDING.
- Hartmut
sedwards(a)svn.reactos.com wrote:
>remove trailing whitespace at end of lines
>
> *[truncated at 1000 lines; 37354 more skipped]*
Steven,
This patch is unacceptably large, and your commit message is way too
short to explain all the changes. Please revert the patch immediately
and work on a branch, submitting small patches at a time so that other
developers can review them. Also, formatting patches are prohibited, so
I don't think your patches can be accepted at all, even if in a branch.
Best regards,
Alex Ionescu
<If anyone did not notice the sarcasm, please shoot yourselves. Great
work Steven; I hoped you used an automated tool!>
hbirr(a)svn.reactos.com wrote:
> - initialize a user profile before loading syssetup.dll.
> - this makes it possible to install ros over an existing ros.
>
>
>
> Updated files:
> trunk/reactos/subsys/system/setup/makefile
> trunk/reactos/subsys/system/setup/setup.c
>
Harmut ,
Does this apply if Ros is started from a freeldr diskette ?
Regards
Gerard
Hi,
There are currently some files in ntoskrnl/rtl, lib/rtl, and /lib/crt
which are duplicated. Stuff like vsprintf, sprintf, etc.
I think they should be massaged into lib/string so that all the modules
can share the code instead of duplicating it THREE times(!).
Best regards,
Alex Ionescu
--- J M <open.proyects(a)gmail.com> a écrit:
> Hi list,
>
> I am having "problems" with debugging support. I have my build
> environment in Windows. I set up gcc/g++/nasm ok and i'm building last
> SVNs without any problem.
>
> I'd like to debug some code and i get problems here. I test vmware
> with the following results ...
>
> VMWare (config => KDB=1, DBG=1)
> ---------------------------------------
> * DEBUGPORT=COM1 BAUDRATE=115200 => CRASH, FREEZE!!!
> * DEBUGPORT=FILE => REBOOT
im getting the same problem with DEBUGPORT=FILE on real hardware.
no clue found at the moment.
>
> Can we debug ReactOS with VMWare ?
>
> How can i update the ReactOS files in a QEMU's .img file ?
mount it with winimage on windows,
and with the loopback under linux.
mount -o lo qemufile.img /mnt/ros_c
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi list,
I am having "problems" with debugging support. I have my build
environment in Windows. I set up gcc/g++/nasm ok and i'm building last
SVNs without any problem.
I'd like to debug some code and i get problems here. I test vmware
with the following results ...
VMWare (config => KDB=1, DBG=1)
---------------------------------------
* DEBUGPORT=COM1 BAUDRATE=115200 => CRASH, FREEZE!!!
* DEBUGPORT=FILE => REBOOT
Can we debug ReactOS with VMWare ?
How can i update the ReactOS files in a QEMU's .img file ?
Thanks in advance!
Hi,
since some time, I'm not able to install ros from the bootcd over an
existing ros. The first stage setup works perfect. The second boot hangs
after loading most of the drivers. The last line on the debug port comes
from framebuf.dll:
...
DriverBase for \??\E:\ReactOS\system32\win32k.sys: 9d62b000
DriverBase for \??\E:\ReactOS\system32\freetype.dll: 9d803000
DriverBase for \SystemRoot\System32\kbdgr.dll: 9d78f000
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
DriverBase for \SystemRoot\System32\framebuf.DLL: 9dfab000
Has anyone the same problem? The install works again, if I delete all
registry files from the existing installation. Usually I use the 'make
install' command to install ros over the network on my test machines.
- Hartmut
Hi,
I find the problem is caused by msys or by msys's make.exe, the command
line:
$(CABMAN) /C bootdata/packages/reactos.dff /L $(BOOTCD_DIR)/reactos /I
Will be expanded like this:
$(CABMAN) c:/ bootdata/packages/reactos.dff c:/msys/1.0/L
(BOOTCD_DIR)/reactos i:/
I don't know why. And when I use "mingw32-make bootcd", everything is ok.
And if we use cabman.exe in msys, the command line should like this:
$(CABMAN) //C bootdata/packages/reactos.dff //L $(BOOTCD_DIR)/reactos //I
It goes well.
-----邮件原件-----
发件人: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] 代
表 Hartmut Birr
发送时间: 2005年5月5日 19:32
收件人: ReactOS Development List
主题: Re: [ros-dev] about rules.mak, a small bug fixed
Your patch breaks compiling on windows without msys. I've commit a
different fix which will solve your problem. There does exist one
problem, it isn't possible to build the bootcd. There is somewhere a
'c:/..' on the path, which isn't correct within a simulated posix system
like msys.
- Hartmut
greatlrd(a)svn.reactos.com wrote:
> tinus
> implement MouseResolution setting
>
> Me (Magnus Olsen)
> remove old psuax drv from hiveinst.inf and add tinus mouse drv settings
> add MouseResolution setting to reg
>
>
>
>
> Updated files:
> trunk/reactos/bootdata/hiveinst.inf
> trunk/reactos/bootdata/hivesys.inf
> trunk/reactos/drivers/input/i8042prt/i8042prt.h
> trunk/reactos/drivers/input/i8042prt/mouse.c
>
The mouse is moving slowly in my machine.
What are the possible values for MouseResolution setting in Hivesys.inf
Regards
Gerard
weiden(a)svn.reactos.com wrote:
> - directly forward GetSecurityDescriptorLength to NTDLL.RtlLengthSecurityDescriptorguard dumping the stack trace to prevent infinite exception loopsguard dumping the stack trace to prevent infinite exception loops
my svn client somehow screwed up the message, it's supposed to be only
- directly forward GetSecurityDescriptorLength to
NTDLL.RtlLengthSecurityDescriptor
Best Regards,
Thomas
hbirr(a)svn.reactos.com wrote:
>- Free always the name string and the completion context in IopDeleteFile.
>
>
>Updated files:
>trunk/reactos/ntoskrnl/io/file.c
>
>
>
The lack of a Device Object signifies there is something REALLY wrong
with the file, and should be treated as invalid. It might not be wise to
do any further operations on it, since they probably already have been done.
Best regards,
Alex Ionescu
Mark Junker wrote:
> The build system seems to be sub-optimal <g>.
There is a new xml build system coming into place soon which is much better
than the current one.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
1) Assertion gets hit on:
Assertion PdoNameInfo->Name.Length failed at io/deviface.c:606
Entered debugger on embedded INT3 at 0x0008:0x80005813.
2) Cmd.exe outputs garbage.
3) DHCP crashes during boot.
Best regards,
Alex Ionescu
hbirr(a)svn.reactos.com wrote:
>- Guard the copying to the IOSB.
>- Do the main processing on success or if previous STATUS_PENDING was returned.
> Do not use some of the IRP and FO flags at this point.
>
>
Ok, I was going to complain about this, but I realize that it must be
used since defintely some parts of ROS don't work properly with those
flags set.
>- Set all results before signaling the events.
>- Signal the FO event previous the user event.
>- Made the code a little bit shorter.
>
>
>
I like your changes and have no complaints, except that the signaling
semantics of the File/User events should be different in the failure
case (my "else" path). You've completely removed that path and thus
changed the logic.
Best regards,
Alex Ionescu