Ros-dev March 2005

ros-dev@reactos.org

64 participants
200 discussions

by James Tabor

Wow! Current SVN (Head)! Used memory 1015744Kb (mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80133000, Init = 0x80130000 (mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong) for NtQueryVirtualMemory() (ke/bug.c:56) Found Bugcheck Resource Data! (ke/bug.c:67) Got Pointer to Bugcheck Resource Data! (ke/clock.c:80) KiInitializeSystemClock() (ke/clock.c:99) Finished KiInitializeSystemClock() No current process Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x9c could not be read: Page not present. No current process KeBugCheckWithTf at ke/catch.c:224 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0xc0000005,0x8002f410,0x00000000,0x00000018) *** ntoskrnl.exe - Address 0x8002f410 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:8002f410 <ntoskrnl.exe:2f410> cr2 18 cr3 26000 Proc: 0 DS 10 ES 10 FS 30 GS 10 EAX: 00000000 EBX: 00000680 ECX: 00026000 EDX: 00000064 EBP: 8013245c ESI: 80132834 ESP: 801323ac EDI: 80132be0 EFLAGS: 00210046 kESP 801323ac Frames: <ntoskrnl.exe:300fc> <ntoskrnl.exe:de31> <ntoskrnl.exe:1285> <ntoskrnl.exe:1aff> <ntoskrnl.exe:382d> <ntoskrnl.exe:c4a3e> <46C> KeBugCheckWithTf at ke/catch.c:224 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0x80000003,0x80005c47,0x00000000,0x00000000) *** ntoskrnl.exe - Address 0x80005c47 base at 0x80000000, DateStamp 0x0

19 years, 6 months

Att: Thomas. 2nd Token Bug.

by Alex Ionescu

Steps to repro: 2nd stage installer, pressing enter really fast to get through the screens. At the last screen: Note that the backtrace seems to be missing kernel-mode stuff beyond the syscall. The crash is actually at token.c:1723. In asm: 800b6657: 3b 02 cmp (%edx),%eax edx is 0x00929004 which is invalid: Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x929004 could not be read: Page not present. Either this function is missing seh, or something has been changed with the token rewrite which messes things up. More info: KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0xc0000005,0x800b6657,0x00000000,0x00929004) *** ntoskrnl.exe - Address 0x800b6657 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:800b6657 <ntoskrnl.exe:b6657 (se/token.c:1723 (NtAdjustPrivilegesToken))> cr2 929004 cr3 6d8b000 Proc: 80ab8290 Pid: ac <setup.ex> Thrd: 80aba0c8 Tid: b0 DS 10 ES 10 FS 30 GS 23 EAX: 00000007 EBX: 00000000 ECX: 8cada688 EDX: 00929004 EBP: 9d8c8d54 ESI: 0064ec20 ESP: 9d8c8c88 EDI: 8cada688 EFLAGS: 00000206 kESP 9d8c8c88 kernel stack base 9d8c6000 Frames: <ntoskrnl.exe:39c2 (/home/alex/tmp/cc6fkKWh.s:178 (KiSystemService))> <advapi32.dll:13dca (token/token.c:58 (AdjustTokenPrivileges))> kdb:> bt Frames: <ntoskrnl.exe:39c2 (/home/alex/tmp/cc6fkKWh.s:178 (KiSystemService))> <advapi32.dll:13dca (token/token.c:58 (AdjustTokenPrivileges))> <syssetup.dll:2aff (wizard.c:1164 (DateTimePageDlgProc))> <user32.dll:ea41 (windows/message.c:982 (IntCallWindowProcA))> <user32.dll:eaef (windows/message.c:1031 (CallWindowProcA))> <user32.dll:1717e (windows/dialog.c:1458 (DefDlgProcA))> <user32.dll:ea41 (windows/message.c:982 (IntCallWindowProcA))> <user32.dll:f456 (windows/message.c:1491 (SendMessageA))> <comctl32.dll:28aac (propsheet.c:1713 (PROPSHEET_Next))> <comctl32.dll:28d83 (propsheet.c:3075 (PROPSHEET_DoCommand))> <comctl32.dll:2ab1a (propsheet.c:3412 (PROPSHEET_DialogProc))> <user32.dll:ea06 (windows/message.c:964 (IntCallWindowProcW))> <user32.dll:eb75 (windows/message.c:1057 (CallWindowProcW))> <user32.dll:1700e (windows/dialog.c:1519 (DefDlgProcW))> <user32.dll:ea06 (windows/message.c:964 (IntCallWindowProcW))> <user32.dll:f364 (windows/message.c:1428 (SendMessageW))> <user32.dll:17aca (windows/dialog.c:2220 (IsDialogMessageW))> <user32.dll:17c5a (windows/dialog.c:531 (DIALOG_DoDialogBox))> <user32.dll:17df8 (windows/dialog.c:1608 (DialogBoxIndirectParamW))> <comctl32.dll:27b57 (propsheet.c:729 (PROPSHEET_CreateDialog))> <comctl32.dll:299ce (propsheet.c:2841 (PropertySheetW))> <syssetup.dll:2f4a (wizard.c:1482 (InstallWizard))> <syssetup.dll:172c (install.c:491 (InstallReactOS))>--- Press q to abort, any other key to continue --- <setup.exe:1333 (setup.c:79 (WinMain))> <setup.exe:145b (setup.c:116 (WinMain))> <setup.exe:116a> <setup.exe:1038> <kernel32.dll:20c30 (process/create.c:339 (BaseProcessStart))> <deadbeef> kdb:> regs CS:EIP 0x0008:0x800b6657 SS:ESP 0x0028:0x80105cb9 EAX 0x00000007 EBX 0x00000000 ECX 0x8cada688 EDX 0x00929004 ESI 0x0064ec20 EDI 0x8cada688 EBP 0x9d8c8d54 EFLAGS 0x00000206 PF IF IOPL0 kdb:> cregs CR0 0xe001003b PE MP TS ET NE WP NW CD PG CR2 0x00929004 CR3 0x06d8b000 Pagedir-Base 0x06d8b000 CR4 0x00000080 PGE GDTR Base 0x800d6100 Size 0x0058 LDTR Base 0x00000000 Size 0x0000 IDTR Base 0x80130320 Size 0x0800

19 years, 6 months

Re: [ros-dev] SM: a blocking bug I can

by ea＠iol.it

Hi Hartmut, > I'm not sure but a native application can only import ntdll.dll. If you > enable the code, smss will import smdll.dll. You are probably right. It is the time to make smdll static. Thank you. Emanuele ____________________________________________________________ Navighi a 2 MEGA e i primi 3 mesi sono GRATIS. Scegli Libero Adsl Flat senza limiti su http://www.libero.it

19 years, 6 months

FreeWin

by ea

This one seems a derivative work of ros. Is it already known? http://gro.clinux.org/projects/freewin

19 years, 6 months

Mac OS X clone???

by rlangschultz＠cox.net

I was wondering if there was a project that would be doing a binary compatible OS X system. What reactos does for windows maybe this project can do for OS X. I was just wondering. I know that pearpc emulates a ppc processor, but wether or not a full os exists is the question. I know also that some versions of linux exist for ppc. Thanks Also - is reactos going to do a mips, ppc, arm, ia64 system?

19 years, 6 months

Re: [ros-svn] [weiden] 14045: Alex Ionescu <ionucu@videotron.ca>

by James Tabor

Hi! Well, this was a surprise! Love the new debugger! My test, building ros on ros two cmd consoles up plus taskmgr. weiden(a)svn.reactos.com wrote: > Alex Ionescu <ionucu(a)videotron.ca> > Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x54 could not be written: Page not present. kdb:> bt Frames: <ntoskrnl.exe:83727 (mm/ppool.c:598 (RFreeMerge))> <ntoskrnl.exe:837a8 (mm/ppool.c:620 (RPoolReclaim))> <ntoskrnl.exe:83fa7 (mm/ppool.c:926 (RPoolFree))> <ntoskrnl.exe:842b7 (mm/ppool.c:98 (ExFreePagedPool))> <ntoskrnl.exe:8267f (mm/pool.c:244 (ExFreePool))> <ntoskrnl.exe:abe2b (se/token.c:576 (SepDeleteToken))> <ntoskrnl.exe:92ce9 (ob/object.c:981 (ObpDeleteObject))> <ntoskrnl.exe:92eea (ob/object.c:1038 (ObpDeleteObjectDpcLevel))> <ntoskrnl.exe:9314d (ob/object.c:1148 (ObfDereferenceObject))> <ntoskrnl.exe:9a709 (ps/process.c:474 (PiDeleteProcessWorker))> <ntoskrnl.exe:9a7f3 (ps/process.c:502 (PiDeleteProcess))> <ntoskrnl.exe:92ce9 (ob/object.c:981 (ObpDeleteObject))> <ntoskrnl.exe:92eea (ob/object.c:1038 (ObpDeleteObjectDpcLevel))> <ntoskrnl.exe:9314d (ob/object.c:1148 (ObfDereferenceObject))> <ntoskrnl.exe:96092 (ps/create.c:394 (PiDeleteThread))> <ntoskrnl.exe:92ce9 (ob/object.c:981 (ObpDeleteObject))> <ntoskrnl.exe:92eea (ob/object.c:1038 (ObpDeleteObjectDpcLevel))> <ntoskrnl.exe:9314d (ob/object.c:1148 (ObfDereferenceObject))> <ntoskrnl.exe:987f2 (ps/kill.c:52 (PsReapThreads))> <ntoskrnl.exe:9eeaf (ps/thread.c:379 (PiReaperThreadMain))> <ntoskrnl.exe:3880 (/tmp/ccoqgJZs.s:83 (PsBeginThread))> kdb:> proc Current process: PID: 0x00000154 State: Terminated (0x1) Image Filename: rdel.exe kdb:> proc list PID State Filename 0x00000164 Active make.exe 0x00000164 Terminated make.exe 0x0000015c Active ctm.EXE 0x0000012c Active make.EXE 0x0000010c Active taskmgr.exe 0x00000100 Active cmd.exe 0x000000f0 Active cmd.exe 0x000000e4 Active explorer.exe 0x000000d4 Active userinit.exe 0x000000c8 Active umpnpmgr.exe 0x000000bc Active eventlog.exe 0x000000ac Active services.exe 0x0000008c Active winlogon.exe 0x00000070 Active csrss.exe 0x00000058 Active smss.exe 0x00000004 Unknown System kdb:> regs CS:EIP 0x0008:0x80082bce SS:ESP 0x0010:0x9d46bac0 EAX 0x8cfccdb4 EBX 0x80c6abc0 ECX 0x8cfc7bdc EDX 0x00000040 ESI 0x00000000 EDI 0x00000000 EBP 0x9d46bac8 EFLAGS 0x00210202 IF IOPL0 RF ID kdb:> cregs CR0 0x8001003b PE MP TS ET NE WP PG CR2 0x7c900000 CR3 0x1652e000 Pagedir-Base 0x1652e000 CR4 0x00000680 PGE OSFXSR OSXMMEXCPT GDTR Base 0x800cf100 Size 0x0058 LDTR Base 0x00000000 Size 0x0000 IDTR Base 0x8012a320 Size 0x0800 kdb:> sregs CS 0x0008 Index 0x0001 GDT RPL0 DS 0x0010 Index 0x0002 GDT RPL0 ES 0x0010 Index 0x0002 GDT RPL0 FS 0x0030 Index 0x0006 GDT RPL0 GS 0x0010 Index 0x0002 GDT RPL0 SS 0x0010 Index 0x0002 GDT RPL0 kdb:> dregs DR0 0x00000000 DR1 0x00000000 DR2 0x00000000 DR3 0x00000000 DR6 0xffff0ff0 DR7 0x00000400 kdb:> thread Current Thread: TID: 0x00000000 State: Running (0x2) Priority: 8 Affinity: 0xffffffff Initial Stack: 0x8011c570 Stack Limit: 0x80119570 Stack Base: 0x8011c570 Kernel Stack: 0x8011c570 Trap Frame: 0x9d46ba28 NPX State: Invalid (0x1)

19 years, 6 months

Re: [ros-svn] [weiden] 14045: Alex Ionescu <ionucu@videotron.ca>

by Alex Ionescu

weiden(a)svn.reactos.com wrote: >Alex Ionescu <ionucu(a)videotron.ca> > > Dispatcher Objects Rewrite (minus Queues, coming in next patch). > > > There is now only one large patch left + a smaller one related to it, which will complete the Dispatcher fixes. After those two patches, everything in my branch will have been committed. The branch will be destroyed and I will create the Winsock branch on which Arty and I will work. Best regards, Alex Ionescu

19 years, 6 months

Vote: Allow 3rd-party distribution of ROS through XDCC Bot.

by Alex Ionescu

Hi, Right now, someone has set up an XDCC IRC bot to distribute copies of ReactOS. While I welcome the move, it raises a question on who is responsible for the quality of those files. Even if the person means no harm, the files can get corrupted/infected by the following events: 1) Download corruption 2) Viral infection 3) Hard-disk damage And perhaps many more. In all cases, this would result in unusable, dangerous or even damaging releases of ReactOS, which we could not control. As such, I propose a vote: [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc channel and ROS-XDCC-001 bot. (support and encourage this distribution) [ ] Yes, allow 3rd-party distribution of the OS, but it must clearly distance itself from officially supported releases (tolerate but do not support this distribution) [ ] No, only sourceforge and other official ReactOS distribution points should be used. Myself I vote for the first choice, but I would like the following to be done: 1) Create MD5 Hashes to verify authenticity 2) Set up official communications with the bot's maintainer and establish a set of guidelines. Best regards, Alex Ionescu

19 years, 6 months

Re: [ros-svn] [greatlrd] 14043: GetDeviceData

by Richard Campbell

screens? :P greatlrd(a)svn.reactos.com wrote: >GetDeviceData >fix the choppy mouse in UT and fix some other small bugs. >I can now use the mouse with out any problem in UT > > > > >Updated files: >trunk/reactos/lib/dinput/mouse.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > >

19 years, 6 months

Re: [ros-dev] Vote: Allow 3rd-party distribution of ROS through XDCC Bot.

by Steven Edwards

Hi, --- Jason Filby <jason.filby(a)gmail.com> wrote: > Another question is: can we really say limit people from > redistributing ReactOS? I don't think that our license(s) prohibit > this. > > Perhaps some guidelines for such people are all that is needed. I think we should allow use of the name in limited situations. As another poster stated having a "Dropline ReactOS" is not a bad thing provided that we setup standards on what has the right to be called "ReactOS" and what does not. If anyone making or distributing a custom version of ReactOS violates the standards we set forth then we have the right to refuse use of the name. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

19 years, 6 months

← Newer
1
...
8
9
10
11
12
13
14
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev March 2005