So far I haven't encountered regressions.
LOL. ;0)
I spent several hours with Alex hacking away at this patch. It's getting farther than with Thomas's patch, but I'm still seeing crashes. I'm not going to have much time this weekend, so I'm dumping status here. I've uploaded the last bootcd I made to http://waxdragon.homeip.net/~ford/ReactOS-21808M-NDK-May6th.7z Attached is the patch, and this is the crash I am currently seeing trying to boot the bootcd:
(ntoskrnl/ke/main.c:291) --------------------------------------------------------------- (ntoskrnl/ke/main.c:292) ReactOS 0.3-SVN (Build 20060505-r21808) (ntoskrnl/ex/init.c:264) NPXThread offset: 640 Used memory 524288Kb (ntoskrnl/mm/mminit.c:387) Kernel Stack Limits. InitTop = 0x800fc000, Init = 0x800f9000 (ntoskrnl/mm/mm.c:283) No current process Assertion '(KeGetCurrentIrql() == APC_LEVEL) || (Thread == NULL) || (Thread->CombinedApcDisable != 0) || (Thread->Teb == NULL) || (Thread->Teb >= (PTEB)MM_SYSTEM_RANGE_START)' failed at ntoskrnl/ex/fmutex.c line 151 KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1241 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
Technical information:
*** STOP: 0x0000001E (0x80000003,0x800a6c71,0x00000000,0x00000010)
*** ntoskrnl.exe - Address 0x800a6c71 base at 0x80000000, DateStamp 0x0
Exception: -1160049408(0) Processor: 0 CS:EIP 8:800a6c71 ntoskrnl.exe:a6c71 cr2 8d7feee4 cr3 2c000 Proc: 80c04c20 Pid: 0 <System> Thrd: 80c05660 Tid: 0 DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 800d51c0 ECX: 0000000a EDX: 00000000 EBP: 800fbc28 ESI: 80104680 ESP: 800fbb98 EDI: 80107780 EFLAGS: 00200286 kESP 800fbb98 kernel stack base 800f9000 Frames: ntoskrnl.exe:21f53 ntoskrnl.exe:2233d ntoskrnl.exe:87573 ntoskrnl.exe:c3771 ntoskrnl.exe:60a9 ntoskrnl.exe:c17da <0>
WD -- ReactOS is a hub, follow the spokes and you'll immediately find absolutely everything you need to know about Windows. ReactOS is not just software, it's people. kjk_hyperion