- Ros-dev - ReactOS.org

What is difference in installation procedure w/wo DGG, KDBG set ?

by David Kredba

For a many month I am unable to install ReactOS with DBG=1 and KDBG=1 enabled. On the same hardware, version with DBG=0 and KDBG=0 installs and runs fine. DBG=1, KDBG=1 enabled ReactOS booted by freeldr asks for COMUTERNAME, Name, password, time zone etc. etc. and asks for reboot. Then it bugchecks with : bt Frames: vmwinst.exe: vmwinst.c: 75 (DetectVMware) bugcheck KeBugCheck at dbg/kdb.c: 1495 Bug detected (code deaddead param 0 0 0 0) Page fault at high IRQL was 2 KeBugCheckWithTf at ke/catch.c:165 Bug detected (code 1e param 0 0 0 0) KMODE_EXCEPTION_NOT_HANDLED Page fault Exception: 14(0) Processo: 0 CS:EIP 8:c00b8cb7 <ntoskrnl.exe: rtl/message.c:108 (RtlFindMessage)> cr2 e07a4604 cr3 1d84a000 Proc: c0eb1c90 Pid:7 <vmwinst> Thrd: c0ebd08 Tid: 2c DS 10 ES 10 FS 30 GS 10 kernel stack base df255000 KeBugCheckWithTf KeBugCheckEx KeBugCheck DbgBugCheckCommand KdbDoCommand KdbMainLoop KdbInternalEnter KdbEnterDebuggerException KiDispatchException ke/i386/usertrap.c: 139 KiUserTrapHandler ke/i386/exp.c: 613 KiTrapHandler /tmp/ccphDdwg.s: 146 KeUserModeCallback vmwinst.c: 75 DetectVMware vmwinst.c:1016 WinMain 1047 WinMain kernel32.dll: BaseProcessStart <DEADBEEF> If someone is interested in more debugging informations, I can send processor registers and map files. Regards, David -- David Kredba <kredba at ibot.cas.cz> GPG: ID 1024D/5B6B02DE Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE

20 years, 6 months

4
8
0 0

Support of NIC Realtek 8139

by Gge

PLease find the status of the Reactos support for the Nic Realtek8139 as per my testing. 1) Detection of Pci Bus2 = Fixed The problem of enumerating cards located on PCI BUS 2 has been fixed by Eric Khol . The bug# 436 can be closed 2) Start Nic driver failure The RTL8139.SYS driver loads successfully but fails to start due to the "NdisMQueyAdapterResources" function which is unimplemnted . The Bug#446 has been created => This is a blocking point for networking with this popular Nic Best regards Gerard

20 years, 6 months

4
7
0 0

AFD_IMMEDIATE' undeclared

by David Kredba

Are you getting this ? (DBG=1, KDBG=1) make[1]: Entering directory `/home/dave2/ros/reactos/lib/msafd' mingw32-gcc -I./include -Wall -Werror -fno-builtin -DUNICODE -D__USE_W32API -I.-I../../include -I../../w32api/include -pipe -march=i486 -D_M_IX86 -g -c misc/sndrcv.c -o misc/sndrcv.o misc/sndrcv.c: In function `WSPRecv': misc/sndrcv.c:66: error: `AFD_IMMEDIATE' undeclared (first use in this function) misc/sndrcv.c:66: error: (Each undeclared identifier is reported only once misc/sndrcv.c:66: error: for each function it appears in.) misc/sndrcv.c: In function `WSPRecvFrom': misc/sndrcv.c:214: error: `AFD_IMMEDIATE' undeclared (first use in this function) misc/sndrcv.c: In function `WSPSend': misc/sndrcv.c:365: error: `AFD_IMMEDIATE' undeclared (first use in this function) misc/sndrcv.c: In function `WSPSendTo': misc/sndrcv.c:503: error: `AFD_IMMEDIATE' undeclared (first use in this function) David -- David Kredba <kredba at ibot.cas.cz> GPG: ID 1024D/5B6B02DE Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE

20 years, 6 months

3
3
0 0

RE: [ros-diffs] [CVS reactos] fix broken work item impl.

by Hartmut Birr

Hi Gunnar, for synchronisation between an unlimited count of objects (or 256) in a wait queue and more than one waiters which removes this objects, there _must_ be used a semaphore (or equivalent code). Please revert your changes. - Hartmut -----Original Message----- From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of gdalsnes(a)osexperts.com Sent: Tuesday, November 16, 2004 12:15 AM To: ros-diffs(a)reactos.com Subject: [ros-diffs] [CVS reactos] fix broken work item impl. Commit in reactos/ntoskrnl/ex on MAIN work.c <> +16 -18 1.20 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.20&c ontent-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c.diff?r1=te xt&tr1=1.20&r2=text&tr2=1.21&f=h> > 1.21 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.21&c ontent-type=text/x-cvsweb-markup> fix broken work item impl. _____ reactos <http://cvs.reactos.com/cgi-bin/cvsweb/reactos> /ntoskrnl <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl> /ex <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex> work.c 1.20 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.20&c ontent-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c.diff?r1=te xt&tr1=1.20&r2=text&tr2=1.21&f=h> > 1.21 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.21&c ontent-type=text/x-cvsweb-markup> diff -u -r1.20 -r1.21 --- work.c 22 Oct 2004 20:18:37 -0000 1.20 +++ work.c 15 Nov 2004 23:14:36 -0000 1.21 @@ -1,4 +1,4 @@ -/* $Id: work.c,v 1.20 2004/10/22 20:18:37 ekohl Exp $ +/* $Id: work.c,v 1.21 2004/11/15 23:14:36 gdalsnes Exp $ * * COPYRIGHT: See COPYING in the top level directory * PROJECT: ReactOS kernel @@ -36,7 +36,7 @@ /* * PURPOSE: Worker threads with nothing to do wait on this event */ - KSEMAPHORE Sem; + KEVENT Event; /* * PURPOSE: Thread associated with work queue @@ -84,7 +84,7 @@ } else { - KeWaitForSingleObject((PVOID)&queue->Sem, + KeWaitForSingleObject((PVOID)&queue->Event, Executive, KernelMode, FALSE, @@ -102,9 +102,10 @@ InitializeListHead(&WorkQueue->Head); KeInitializeSpinLock(&WorkQueue->Lock); - KeInitializeSemaphore(&WorkQueue->Sem, - 0, - 256); + KeInitializeEvent(&WorkQueue->Event, + SynchronizationEvent, + FALSE); + for (i=0; i<NUMBER_OF_WORKER_THREADS; i++) { PsCreateSystemThread(&WorkQueue->Thread[i], @@ -164,30 +165,27 @@ ExInterlockedInsertTailList(&EiNormalWorkQueue.Head, &WorkItem->List, &EiNormalWorkQueue.Lock); - KeReleaseSemaphore(&EiNormalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiNormalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; case CriticalWorkQueue: ExInterlockedInsertTailList(&EiCriticalWorkQueue.Head, &WorkItem->List, &EiCriticalWorkQueue.Lock); - KeReleaseSemaphore(&EiCriticalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiCriticalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; case HyperCriticalWorkQueue: ExInterlockedInsertTailList(&EiHyperCriticalWorkQueue.Head, &WorkItem->List, &EiHyperCriticalWorkQueue.Lock); - KeReleaseSemaphore(&EiHyperCriticalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiHyperCriticalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; #ifdef __USE_W32API email" href="http://www.badgers-in-foil.co.uk/projects/cvsspam/">CVSspam 0.2.8

20 years, 6 months

4
5
0 0

ReactOS eating CPU time

by Casper Hornstrup

In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware? Casper

20 years, 6 months

10
14
0 0

CVS Logs?

by Filip Navara

Can someone please send a change log of CVS since 03/11/2004 (eg. generated using cvs2cl)? Thanks, Filip

20 years, 6 months

2
1
0 0

RE: [ros-diffs] [CVS reactos] Fix handling of debug traps in GDB stub/KiDispatchException.

by Hartmut Birr

Hi, this changes breaks the handling of exceptions if KDB isn't set. In KiDispatchException the variable Action is preinitialized with kdContinue. After your changes, KiDispatchException does always return without any action. After this changes, I'm not able to install reactos. At the second stage setup I do never see the reboot page. - Hartmut -----Original Message----- From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of Gregor Anich Sent: Sunday, November 14, 2004 12:00 AM To: ros-diffs(a)reactos.com Subject: [ros-diffs] [CVS reactos] Fix handling of debug traps in GDB stub/KiDispatchException. _____ reactos <http://cvs.reactos.com/cgi-bin/cvsweb/reactos> /ntoskrnl <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl> /ke <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke> catch.c 1.51 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c?rev=1.51& content-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c.diff?r1=t ext&tr1=1.51&r2=text&tr2=1.52&f=h> > 1.52 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c?rev=1.52& content-type=text/x-cvsweb-markup> diff -u -r1.51 -r1.52 --- catch.c 11 Nov 2004 12:27:40 -0000 1.51 +++ catch.c 13 Nov 2004 23:00:15 -0000 1.52 @@ -16,7 +16,7 @@ * along with this program; if not, write to the Free Software * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */ -/* $Id: catch.c,v 1.51 2004/11/11 12:27:40 ekohl Exp $ +/* $Id: catch.c,v 1.52 2004/11/13 23:00:15 blight Exp $ * * PROJECT: ReactOS kernel * FILE: ntoskrnl/ke/catch.c @@ -80,13 +80,13 @@ else if (KdDebuggerEnabled && KdDebugState & KD_DEBUG_KDB) { Action = KdbEnterDebuggerException (ExceptionRecord, Context, Tf); - if (Action == kdContinue) - { - return; - } } #endif /* KDBG */ - if (Action != kdDoNotHandleException) + if (Action == kdContinue) + { + return; + } + else if (Action != kdDoNotHandleException) { if (PreviousMode == UserMode) { @@ -94,7 +94,7 @@ { PULONG Stack; ULONG CDest; - char temp_space[12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT)]; // FIXME: HACKHACK + char temp_space[12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT)]; /* FIXME: HACKHACK */ PULONG pNewUserStack = (PULONG)(Tf->Esp - (12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT))); NTSTATUS StatusOfCopy; @@ -125,10 +125,11 @@ } else { - // Now it really hit the ventilation device. Sorry, - // can do nothing but kill the sucker. + /* Now it really hit the ventilation device. Sorry, + * can do nothing but kill the sucker. + */ ZwTerminateThread(NtCurrentThread(), ExceptionRecord->ExceptionCode); - DPRINT1("User-mode stack was invalid. Terminating target thread\nn"); + DPRINT1("User-mode stack was invalid. Terminating target thread\n"); } Tf->Eip = (ULONG)LdrpGetSystemDllExceptionDispatcher(); return; email" href="http://www.badgers-in-foil.co.uk/projects/cvsspam/">CVSspam 0.2.8

20 years, 6 months

2
1
0 0

Our ne2000 driver and tcpip

by art yerkes

I found the bug in our ne2000 driver that perplexed filip. The bug was that the meaning of the PACKET_HEADER part in ne2000 that was skipped was a simple header put on each packet to determine what buffer page would be used next. This header is only 4 bytes and has nothing to do with the ethernet frame header. I've now factored in the ethernet frame header and made tcpip work the right way, that is to remove consideration of the ethernet frame header at layers above lan in the receive pipe. This should make all adapters work the same way for larger packets (and ne2000 now work right). I found few references to how this actually works so I could still be wrong, but I'm going on what filip said and this: http://cvs.sourceforge.net/viewcvs.py/openh323/pwlib/tools/PacketVxD/epacke… Which basically confirms filip's opinion. Please try it out. -- 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

20 years, 6 months

1
0
0 0

Genesi

by Jason Filby

Just came across this: http://www.genesi.lu/ Appears to be a new PPC based platform with published specs - would be great to have ROS running on this! Cheers Jason

20 years, 6 months

5
6
0 0

RE: [ros-cvs] CVS Update: reactos

by Hartmut Birr

Hi, I think some of your changes in apc.c are wrong. Apc's are always thread local. They have nothing to do with the dispatcher database lock. The only locking object is the ApcQueueLock from the thread structure. - Hartmut > -----Original Message----- > From: ros-cvs-bounces(a)reactos.com > [mailto:ros-cvs-bounces@reactos.com] On Behalf Of ion(a)cvs.reactos.com > Sent: Thursday, November 11, 2004 2:24 PM > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/ntoskrnl/ps/ > Changes by: ion(a)mok.osexperts.com 04/11/11 14:23:53 > > Modified files: > reactos/include/ddk/: kefuncs.h ketypes.h > reactos/ntoskrnl/include/internal/: ke.h ps.h > reactos/ntoskrnl/ke/: apc.c process.c wait.c > reactos/ntoskrnl/mm/: marea.c virtual.c > reactos/ntoskrnl/mm/i386/: page.c > reactos/ntoskrnl/ps/: psmgr.c > > Log message: > Kernel: > - apc.c: Fixed some bugs and used Dispatcher Lock. > Simplified some functions and renamed/inlined others. > - wait.c: Fixed some assumptions about Dispatcher Lock > and Waiting/Alertability > - process.c: Fully implemented KeStackAttachProcess and > KeStackDetachProcess. Made all functions use PKPROCESS and > not PEPROCESS. > Memory Manager: Fixed calls to > KeAttachProcess/DetachProcess to typecast PKPROCESS > Process Manager: Removed call to empty function in apc.c > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

20 years, 6 months

2
1
0 0

Re: [ros-dev] taskmgr crashes in regobj.c - CmiObjectParse on VirtualPC

by Theodor Willax

Hi James, >I can start taskmgr but it does not display at all! I've even seen it >running >by executing ps.exe. I started with cmd at boot time and executed taskmgr >from >the cmd prompt and I get the gui loaded but w/o the taskmgr displayed. >After >a Alt-F4 and a click of the mouse I get this. > >(objects/gdiobj.c:711) called from: objects/color.c:453 >(objects/gdiobj.c:537) Invalid ObjectHandle 0x00050022 >(objects/gdiobj.c:709) GDIOBJ_LockObj failed for 0x00080021, reqtype >0x00080000 >reason 1 >(objects/gdiobj.c:711) called from: objects/color.c:453 >KeBugCheckWithTf at ke/catch.c:164 >Bug detected (code 1e param 0 0 0 0) > KMODE_EXCEPTION_NOT_HANDLED > >Page Fault Exception: 14(0) >Processor: 0 CS:EIP 8:dd7af992 <win32k.sys: 13992> >cr2 f000e8e2 cr3 3ce4e000 Proc: c0b24228 Pid: 4 <csrss> Thrd: c0b7c900 Tid: >27 >DS 10 ES 10 FS 30 GS 10 >EAX: f000e816 EBX: 00000000 ECX: f000e816 >EDX: ccfc0eb0 EBP: ddc26dcc ESI: 00d2feb0 ESP: ddc26d40 >EDI: ddc26f84 EFLAGS: 00010282 kESP ddc26d40 kernel stack base ddc24000 >Frames: <win32k.sys: 130c7> <win32k.sys: 13290> <win32k.sys: 1d1e6> ><win32k.sys: > 1d7f7> <win32k.sys: 1db26> <ntoskrnl.exe: 35cd> <77E7036B> > >This was with real hardware. > I will try it on real hardware in the next days too. > >Sorry I'm still hacken it, >James What are you hacking? Theo _________________________________________________________________ So einfach geht das. MSN Toolbar mit Pop-up-Blocker. http://toolbar.msn.de/ Jetzt kostenlos downloaden und gut ist!

20 years, 6 months

2
1
0 0

Reactos Sound - Testing

by Gge

Hello, As some work is being done on sounds , i am willing to make some testing as well on my real hardware configuration based on "SB live value!" sound card In order to be efficient , and to merge effort , I 'd like to know on what basis the test can be done : 1) drivers - Reactos drivers - Oem drivers - Drivers available as Gpl 2) Applications - Winamp version 2 or 5 , version lite , full ? - other applications 3) Test progress - results How to share the test progress ? Wiki page ?Reactos Reactos Best regards Gerard

20 years, 6 months

1
0
0 0

ReactOS Versions

by Rick Langschultz

When ReactOS is built and runs windows executables stabily I think we should have a program for windows that will let you customize the platform like windows ce and compile it with all the features you want. I think that it would be a great idea because of different types of systems such as PBX/VOIP servers, application servers, and domain name servers. This would allow security to be integrated into ReactOS by limiting programs allowing open ports, and Denial of service attacks. Maybe even support for multiple architectures like SH, ARM, X86, AMD64, PPC??? With FAT, FAT32, NTFS, XFS, EXT3, EXT2, and many others. Maybe even a rom based os. Please tell me what you all think.

20 years, 6 months

6
6
0 0

taskmgr crashes in regobj.c - CmiObjectParse on Virtual PC

by Theodor Willax

Hi, I'm getting repeatedly kernel crashes in regobj.c - CmiObjectParse (line 168). To reproduce the crash start task manager with a right click on the taskbar, minimize this instance of taskmanager and start a new one. Here the code ---- else { if ((FoundObject->KeyCell->Flags & REG_KEY_LINK_CELL) && !((Attributes & OBJ_OPENLINK) && (EndPtr == NULL))) { DPRINT("Found link\n"); RtlInitUnicodeString(&LinkPath, NULL); ---- FoundObject->KeyCell is NULL. Does anybody else have the same problem? I've attached two screenshots of the BSODs. Clean compile of last cvs snapshot. Regards, Theo _________________________________________________________________ Tun Sie Ihrem Rechner was Gutes. MSN Hotmail mit McAfee® Anti-Virus. http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden!

20 years, 6 months

2
1
0 0

RE: Ekush

by Ge van Geldorp

> From: nazmul ahsan [mailto:nahsan@hotmail.com] > > I am not associated with the Ekush project, but as a > Bangladeshi I feel > embarassed at the boneheadedness of a fellow countryman. > > However, while you're demanding that he/them be brought to > justice, please be aware of the nature of Bangladeshi law > enforcement: > http://www.hrcbmdfw.org/bk_news/press_release_09082004.htm Please note that we have not demanded that the people of the Ekush project be brought to justice. The only thing we demand is that they either stop distributing Ekush as long as it contains our code, or comply with the GPL by putting back copyright notices and publishing source. Since the Ekush website is currently down, effectively stopping the distribution I don't think we'll be taking further action. Gé van Geldorp.

20 years, 6 months

1
0
0 0

Race Condition?

by James Tabor

Hi, I believe with the new cvs changes by Hartmut caused the illusive lockups I'm having to pop up more often now. Two today and yesterday. This print out looks good, but I've had debug messages overlapping each other at the beginning of the building process. Debug output before lockup, there seems to be a double print out, before just one every KernelTime, and the KernelTime looks like it had stopped, (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 22993, MC_USER 4858, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217935 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 23009, MC_USER 4864, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217913 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 23009, MC_USER 4864, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217913 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266471 PFFree: 65536 PFUsed: 0 MC_CACHE 23025, MC_USER 4870, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217891 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266471 PFFree: 65536 PFUsed: 0 MC_CACHE 23025, MC_USER 4870, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217891 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22065, MC_USER 4876, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218845 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22065, MC_USER 4876, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218845 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22081, MC_USER 4882, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218823 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22081, MC_USER 4882, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218823 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22097, MC_USER 4888, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218801 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22097, MC_USER 4888, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218801 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22113, MC_USER 4889, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218784 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22113, MC_USER 4889, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218784 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22129, MC_USER 4900, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218757 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22129, MC_USER 4900, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218757 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22145, MC_USER 4904, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218737 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22145, MC_USER 4904, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218737 (KERNEL32:mem/global.c:412) Memory Load: 13 System lockup, keyboard works???, num & scroll light works on/off. Anyone have a good guess where to start? Thanks, James

20 years, 6 months

8
15
0 0

Ekush part II

by James Tabor

Hi all! Ros Kernel task switcher, http://blight.eu.org/reactos/ekush-tskswitch.html Great job Blight! On slashdot.org! http://slashdot.org/article.pl?sid=04/11/10/1320231&tid=201&tid=190&tid=1 Thanks a mil GvG! Kick'en A$$ mode, "Lets get our hate on"! )8^| James ps Moven it over to the General list.

20 years, 6 months

3
2
0 0

Re: Ros-dev Digest, Vol 3, Issue 15

by Lucio Diaz

ReactOS is quite slow today, are we under a DoS atack?, maybe related to this ekush guy?.This is weird. Lucio Diaz. ______________________________________________ Renovamos el Correo Yahoo!: ¡100 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

20 years, 6 months

3
2
0 0

Ekush

by Ge van Geldorp

Ekush (http://www.ekush.com) published some binaries. Surprise, surprise, it looks like ReactOS very much (Check e.g. the radio buttons on the "Accept License" screen during 2nd stage setup). Their readme.rtf (epc/doc/Readme.rtf) has these entries: <quote start> Q. Is the OS completely written from scratch? A. Not really in many cases, at least 50% of the components has been shared or taken from some other projects. In fact, we mostly get the ideas and writing them for ours. Eventually we are coding them new folks are based on something else (in wish list) and slowly-slowly they will be removed from our main source tree. Q. You guys says Project published under the GPL but why dont you published sources? A. Initially we decided that, EKUSH should be published under the GPL. But, still there is some confusion within the team. We are now sharing sources between team members only and unless the confusion goes removed we cannot publish sources. Finally, we decided to use a BSD styled license for Ekush and sources or binaries whatever we publish should be free to public and covered by the same license (until a functional edition is released). Information sources and Wish List: Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe OS, FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS, Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC, BartPE, KDesktop, Line, WinPenguins, 3D Desktop, Dr. Anil Basu, Jason Robin, William Harry, Luiz Quarteiro, Fernando Adantas, Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan, James Bukan, Dr. Piera and Project 21 Team." <quote end> My guess is they are in violation of the GPL by using (some of) our source and not publishing their source. Gé van Geldorp.

20 years, 6 months

16
24
0 0

RE: [ros-dev] Ekush

by Colin Burn

Somebody should email Wine\QEmu\Whoever else and let them know about these guys. Col

20 years, 6 months

1
0
0 0

ReactOS setup CD-ROM crashes on old hardware.

by Mike Swanson

I took a picture of the screen: http://mike.warpedbelief.com/images/ros-crash.jpg It crashed immediately after I hit a key during the "Press any key to boot CD..." prompt. I can't really figure out if any hardware could cause problems. This is the configuration: Pentium 120 MHz 64 MB of RAM 2 GB hard disk (I think it's Western Digital) 2 MB ET4000 video 36x CD-ROM drive One floppy drive The hard disk partition scheme is this: One primary partition. FAT16. Windows NT 4 Server install on it. Takes up the whole 2 GB.

20 years, 6 months

4
4
0 0

Website Changes

by Steven Edwards

Hello, While you guys are working on the website changes I would like to add that the Wine application database is GPL, in CVS and is done in PHP. http://cvs.winehq.com/cvsweb/appdb/ Thanks Steven __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

20 years, 6 months

1
0
0 0

Hi!

by K McI

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 PING! ~ -Q -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBkTbW7mze81O92HkRAhWzAJ0Su/H6oOYnpwB1fxdiz3o4N1YcegCeOBBt RWLgqgJKj3IhNKE59wqmLrY= =JPza -----END PGP SIGNATURE-----

20 years, 6 months

1
0
0 0

Re: [ros-cvs] CVS Update: reactos

by Alex Ionescu

chorns(a)cvs.reactos.com wrote: >CVSROOT: /CVS/ReactOS >Module name: reactos >Repository: reactos/tools/ >Changes by: chorns(a)mok.osexperts.com 04/10/24 10:51:33 > >Modified files: > ./: ChangeLog > reactos/ntoskrnl/: Makefile > reactos/regtests/regtests/: regtests.c regtests.def > reactos/regtests/shared/: regtests.h > reactos/tools/: regtests.c >Added files: > reactos/ntoskrnl/tests/: .cvsignore Makefile setup.c stubs.tst > reactos/ntoskrnl/tests/tests/: .cvsignore > >Log message: > 2004-10-24 Casper S. Hornstrup <chorns(a)users.sourceforge.net> > > * ntoskrnl/Makefile (TARGET_REGTESTS): Define to yes. > * regtests/regtests/regtests.c (_ExitProcess): Declare. > * regtests/regtests/regtests.def (_ExitProcess@4): Ditto. > * regtests/shared/regtests.h (_ExitProcess): Ditto. > * tools/regtests.c: Exit process using _ExitProcess(); > Properly support fastcall symbols. > * ntoskrnl/tests: New directory. > * ntoskrnl/tests/tests: Ditto. > * ntoskrnl/tests/.cvsignore: New file. > * ntoskrnl/tests/Makefile: Ditto. > * ntoskrnl/tests/setup.c: Ditto. > * ntoskrnl/tests/stubs.tst: Ditto. > * ntoskrnl/tests/tests/.cvsignore: Ditto. > >_______________________________________________ >Ros-cvs mailing list >Ros-cvs(a)reactos.com >http://reactos.com/mailman/listinfo/ros-cvs > > > Hi, I can't say I'm terribly overjoyed with having the /tests directory in /ntoskrnl. Would it be possible instead to have a /tests root (on the new SVN server) where all the tests would go? like /tests/ntoskrnl, /tests/kmregtests etc... I think it would make it a bit clearer...it just bugs me to have /tests in ntoskrnl. Best regards, Alex Ionescu

20 years, 6 months

9
25
0 0

What I have learned on my time off (LinuxWorld)

by Steven Edwards

Hi Everyone, We got very good feedback from LinuxWorld.de and I will be returning next year. 90% of the people visting our booth left thinking very highly of our work. All in all the results were much better than the last expo. I very surprised that so many people came up to us and said "we have heard of ReactOS or we have tried it out". Here is my rough list of notes on where I think we need to go from here after discussion with the developers and users. 1. We need a roadmap for the future. THIS DOES NOT MEAN THAT THERE ARE FIRM DATES ATTACHED!!!! But we do need to plan our 0.3, 0.4, 0.5 and 1.0 releases. During a dinner discussion with some of the dev team I asked the question "What do we need before we can have a ReactOS Workstation 1.0" and it does not seem to be to far out of grasp. Dont get me wrong there are LOTS of little things that must be done but the major things we need to have a real replacement workstation are below. If you think about what Windows NT 4 had even with Service Pack 6 we are not that far off. Note I am not talking about a server replacement here. Just a usable client OS. - Networking (0.3) - Samba port needs to implemented (0.4) - We need to implement Windows style printing support (0.4 or 0.5) - Most applications need to install..Office 2000/XP, Quicken, etc (0.4) - We have to develop our own Hardware Compatibity List (0.5) - NTFS (????) - It must be stable (1.0) 2. We have to have regression testing in place. Lack of stablity and regressions are killing us. We have to have the Wine tests in ReactOS. We also need a suite of kernel mode tests. Casper's system seems like its going to work well for the kernel mode side but most of us seem to be worried about the lack of being able to use Winehq regression tests for user mode. 3. We need to improve our documentation and website. After much discussion and two too many beers on my part our discussions turned to documentation and the website. We all agreed that the current system is not working and we need to develop a method of storing most of the website in CVS so that people can send us a patch. Same thing with the documentation....none of us wants to use ezPublish to develop documentation when we can all use docbook right out of cvs and submit diffs. Most of us even like the Wiki system as its not hassle and can maintain a history as well. 4. We need to develop relationships with vendors. This ties in to getting ReactOS stable and usable. Once we have 0.3 out the door I expect things will change for us in ways no one can see. I am going to focus more on this in the coming months, first in the way of hardware donations. 5. Moving to subversion. There still seems to be some problems with this and while we all seem to look forward to it, CVS is doing its job for the moment. GvG has offered to setup a CVS mirror to help with some of the bandwith problems of mok. In closing it was very cool to get to meet all of the developers that were able to make it, I feel like we are going in the right direction and I look forward to your feedback. Thanks Steven __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

20 years, 6 months

4
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev