Ros-dev December 2005

ros-dev@reactos.org

81 participants
142 discussions

by Murphy, Ged (Bolton)

-----Original Message----- From: Royce Mitchell III [mailto:royce3@ev1.net] Sent: 23 December 2005 03:18 To: ReactOS Development List Subject: Re: [ros-dev] Change log Ged Murphy wrote: > Ge van Geldorp wrote: > >>> From: Magnus Olsen >>> >>> U need give lest 2-3 day when u request changelog not every are on >>> same time line >>> >> >> >> The branch was created 2 weeks ago. Plenty of time for everyone to >> get their >> changelog entries in place. >> >> GvG >> > > > I also announced the creation of the changelog exactly 2 weeks ago, > and various at times since then > > http://www.reactos.org/archives/public/ros-dev/2005-December/006728.html > Could we get a page setup describing how to pull down ( via cmd line and tortoise ) a list of changes that occured between a previous release and the current one? We didn't receive this information until about 2 days ago. Yes I know I could probably find it on the net, but it would also help to have this page list the revision #'s associated with each release, just so that all info is in one place to make it easy for us to record our respective contributions to the release. Thanks. In Tortoise, I just download the whole history for the branch and then filter it with the date pull downs in the top left. It's as easy as that and gives more information than the text version. Ged ************************************************************************ 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

19 years, 3 months

Carets

by James Tabor

Hi! Has anyone notice that the help carets don't work anymore? AbiWord too! Four weeks or so. Thanks, James

19 years, 3 months

FreeLdr build docs?

by Michael B. Trausch

I may be just an idiot or blind, but I can't seem to find any information on building freeldr, and it doesn't seem to have a makefile. Everything that I can find points to it being loadable by GRUB and the like, but I'm not sure why I can't find the *how* on building it. Am I just blind, or missing something extremely obvious? (Yes, I have been searching Google for a little while now... I'm not turning anything up, yet.) Thanks, Mike -- Michael B. Trausch fd0man(a)gmail.com "Why geeks like computers: unzip, strip, touch, finger, grep, mount, fsck, more, yes,fsck,fsck,fsck,umount, sleep." :-)

19 years, 3 months

RE: [ros-dev] Loopback problem

by Murphy, Ged (Bolton)

Phillip Susi wrote: > Wait a second... why is it sending only one byte at a time? > The caller > is only send()ing one byte at a time? This is true. Although Send() will return indicating the data has been sent, nagling should hold the actual packet back until it is full, however this should only happen if there is unconfirmed data i.e. no ACK. To avoid any confusion, you can switch nagling off with the TCP_NODELAY flag I'm interested in this bug, but I'm not around tonight to play about with it :( ************************************************************************ 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

19 years, 3 months

RE: [ros-dev] Loopback problem

by Murphy, Ged (Bolton)

Ge van Geldorp wrote > If there are no objections, I want to commit the attached > patch. Looks good +1 ************************************************************************ 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

19 years, 3 months

How does one make a MP build anyway?

by WaxDragon

Gang, I have been unsuccessful in building a working MP bootcd for a while now. I conferred with Hartmut about some of the details, but still cannot get it working. This is what I tried: 1. Set MP=1 in config.xml 2. Hacked the hal xml files to make halmp.dll hal.dll on the bootcd, per Harmut Index: halx86/up/halup.xml =================================================================== --- halx86/up/halup.xml (revision 20282) +++ halx86/up/halup.xml (working copy) @@ -1,6 +1,6 @@ <module name="halup" type="kernelmodedll"> <importlibrary definition="../../hal/hal.def" /> - <bootstrap base="reactos" nameoncd="hal.dll" /> + <bootstrap base="reactos" /> <include base="hal_generic">../include</include> <include base="ntoskrnl">include</include> <define name="_DISABLE_TIDENTS" /> Index: halx86/mp/halmp.xml =================================================================== --- halx86/mp/halmp.xml (revision 20282) +++ halx86/mp/halmp.xml (working copy) @@ -1,6 +1,6 @@ <module name="halmp" type="kernelmodedll"> <importlibrary definition="../../hal/hal.def" /> - <bootstrap base="reactos" /> + <bootstrap base="reactos" nameoncd="hal.dll"/> <include base="hal_generic">../include</include> <include base="ntoskrnl">include</include> <define name="_DISABLE_TIDENTS" /> 3. make bootcd, as normal The resulting bootcd fails to boot under "qemu -smp 2" with the following trace: (./ntoskrnl/ke/main.c:295) --------------------------------------------------------------- (./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20051221-r20282) (hal/halx86/mp/apic.c:420) Getting VERSION: 50011 (hal/halx86/mp/apic.c:423) Getting VERSION: 50011 (hal/halx86/mp/apic.c:454) Getting ID: 0 (hal/halx86/mp/apic.c:457) Getting ID: f000000 (hal/halx86/mp/apic.c:554) CPU0: (hal/halx86/mp/apic.c:555) Physical APIC id: 0 (hal/halx86/mp/apic.c:556) Logical APIC id: 0 (hal/halx86/mp/apic.c:557) 00000000 00000000 f0000000 (hal/halx86/mp/apic.c:584) CPU0: (hal/halx86/mp/apic.c:585) Physical APIC id: 0 (hal/halx86/mp/apic.c:586) Logical APIC id: 1 (hal/halx86/mp/apic.c:587) 00000000 01000000 f0000000 (hal/halx86/mp/apic.c:588) 0 (hal/halx86/mp/apic.c:619) enabled ExtINT on CPU#0 Used memory 131072Kb (./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits. InitTop = 0x8013c000, Init = 0x80139000 (./ntoskrnl/mm/mm.c:283) No current process (hal/halx86/mp/processor_mp.c:112) Attempting to boot CPU 1 (hal/halx86/mp/apic.c:1014) Attempting to boot CPU 1 (hal/halx86/mp/apic.c:1044) 80572be0 25000 80001000 0 (hal/halx86/mp/apic.c:554) CPU1: (hal/halx86/mp/apic.c:555) Physical APIC id: 1 (hal/halx86/mp/apic.c:556) Logical APIC id: 0 (hal/halx86/mp/apic.c:557) 01000000 00000000 f0000000 (hal/halx86/mp/apic.c:584) CPU1: (hal/halx86/mp/apic.c:585) Physical APIC id: 1 (hal/halx86/mp/apic.c:586) Logical APIC id: 2 (hal/halx86/mp/apic.c:587) 01000000 02000000 f0000000 (hal/halx86/mp/apic.c:588) 1 (hal/halx86/mp/apic.c:624) masked ExtINT on CPU#1 CPU 1 is now running (ntoskrnl/ke/i386/exp.c:539) Ignoring P6 Local APIC Spurious Interrupt Bug... (./ntoskrnl/ke/ipi.c:88) CPU0, waiting longer than 5 seconds to start the ipi routine KeBugCheck at ./ntoskrnl/ke/ipi.c:89 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2630> ./ntoskrnl/ke/bug.c:0 () <ntoskrnl.exe:2668> ./ntoskrnl/ke/bug.c:504 (KeBugCheck) <ntoskrnl.exe:414f> ./ntoskrnl/ke/ipi.c:0 () <ntoskrnl.exe:4470> ./ntoskrnl/ke/ipi.c:0 () <ntoskrnl.exe:44df> ./ntoskrnl/ke/ipi.c:174 (KeIpiGenericCall) <ntoskrnl.exe:abd71> ./ntoskrnl/mm/i386/page.c:1043 (MmDeleteVirtualMapping) <ntoskrnl.exe:ac891> ./ntoskrnl/mm/i386/page.c:431 (MmDeletePageTable) <ntoskrnl.exe:d52ce> ./ntoskrnl/mm/mminit.c:459 (MmInit3) <ntoskrnl.exe:cf7c0> ./ntoskrnl/ex/init.c:622 (ExpInitializeExecutive) <ntoskrnl.exe:66fc> ./ntoskrnl/ke/main.c:106 (KiSystemStartup) <ntoskrnl.exe:cd851> ./ntoskrnl/ke/main.c:300 (_main) <ntoskrnl.exe:104b> ./ntoskrnl/ke/i386/main_asm.S:46 (NtProcessStartup) An MP bootcd I made several months ago (~18xxx) did the same thing on a Abit BP6 with dual Celerons, so I'm fairly confident qemu is acting properly. I still have the BP6 and am willing to test MP builds, but I wasted about 10 CD-R's trying to get a working MP bootcd before giving up. Am I just doing something wrong? I would like to get this worked out and documented somewhere. WD -- <Russell> argh <Russell> iterator shenanigans :/

19 years, 3 months

Re: [ros-diffs] [mbosma] 20285: Add a link to the new faq entry in the "You are already logged in" error message. (Untested)

by Ged Murphy

19 years, 3 months

Loopback problem

by Ge van Geldorp

I've been tracking down a problem with ibrowser being extremely slow for me (it took 64 sec to load http://www.reactos.org). It turns out to be a problem associated with the loopback interface. The attached test program (gcc -o loop.exe loop.c -lws2_32) is the minimum test program to demonstrate the problem. It occurs when you send a small amount of data over the loopback interface when there is no pending recv (so you send, then start a recv for the data, then another send, then another recv, no recv waiting while you send). Sequence of events: - Start first send - TCP/IP stack queues the data at the receiving end - First send returns - Start first recv - Queued data is retrieved, but it is determined that there's plenty of space in the TCP window left, so there is no ACK sent back - First recv returns - Start second send - tcp_output determines that the connection is not idle (there is some un-ACKed data) and queues the data at the sending end - Second send returns - Start second recv - Since there is no data waiting at the receiving end, recv just sits there - An internal timer with a period of 2.5 sec expires - The timer proc notices that there is an ACK pending - ACK is sent back to the sending end - Sending end determines connection is idle now and sends the queued data to the receiving end - Timer proc terminates and reschedules itself - Data has now arrived at the receiving end and can be retrieved by the waiting recv. Again no ACK is sent back - Second recv returns - Third send starts, queues its data at sending end and returns - Third recv starts, has to wait 2.5 sec for the internal timer to timeout and then returns - etc. Although I understand what's wrong, I have a bit of difficulty trying to figure out how to fix it. Attached is a proposed fix, which basically attacks the problem at the sending end by removing the check if the connection is idle or not. With that fix the loop.c program works as I expect and http://www.reactos.org loads in a much more reasonable 2-3 sec in ibrowser. The problem that I have with the fix is that it's a change in code we borrowed from the BSD stack. I can hardly imagine that a piece of software so heavily used as the BSD stack would have such a fundamental problem. Any thoughts? GvG

19 years, 3 months

Re: [ros-svn] [ekohl] 20281: Add missing RtlMakeSelfRelatedSd prototype.

by James Tabor

Hi, ekohl(a)svn.reactos.com wrote: > Add missing RtlMakeSelfRelatedSd prototype. > > > Updated files: > trunk/reactos/include/ndk/rtlfuncs.h > [CC] lib/rtl/sd.c lib/rtl/sd.c:431: error: conflicting types for 'RtlMakeSelfRelativeSD' include/ndk/rtlfuncs.h:742: error: previous declaration of 'RtlMakeSelfRelativeSD' was here lib/rtl/sd.c:431: error: conflicting types for 'RtlMakeSelfRelativeSD' include/ndk/rtlfuncs.h:742: error: previous declaration of 'RtlMakeSelfRelativeSD' was here make: *** [obj-i386/lib/rtl/sd.o] Error 1 Thanks, James

19 years, 3 months

Daily-updated Doxygen documentation

by Ge van Geldorp

I've installed a script on the webserver which will run Doxygen (a source cross-referencing tool, see http://www.doxygen.org) on our complete source tree. The script runs once a day. The results can be viewed on http://www.reactos.org/generated/doxygen (or choose "Doxygen" from the "Development" menu on the website). GvG

19 years, 3 months

← Newer
1
2
3
4
5
6
7
...
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev December 2005