I've compiled from the latest SVN build, and almost everything works. The only problem is that after I hit "finish" from the setup wizard, it freezes.
Unfortunately, I don't know how to bypass the setup wizard... the Shift-F10 command prompt "bug"/feature from WinXP setup doesn't seem to have been implemented in ReactOS :-p
This happens under QEmu as well as VMWare Player. VMWare gets just a little bit farther--enough to show a blue screen:
Code: Select all
ExEnumHandleTable at ntoskrnl/ex/sysinfo.c:51 is unimplemented, have a nice day ExEnumHandleTable at ntoskrnl/ex/sysinfo.c:51 is unimplemented, have a nice day (dll/ntdll/ldr/utils.c:1198) LdrGetExportByName(): failed to find mxdMessage (dll/ntdll/ldr/utils.c:2024) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (dll/ntdll/ldr/utils.c:2024) Failed to create or open dll section of 'midimap.drv' (Status c000013 5) (lib/rtl/process.c:325) Failed to receive the process cookie! Status: 0xc0000003 (ntoskrnl/mm/anonmem.c:651) Region size would overflow into kernel-memory (lib/rtl/heap.c:725) Could not allocate c0010000 bytes (lib/rtl/heap.c:1038) Heap 00640000: block 6A385020 is not inside heap SYSREG_CHECKPOINT:SYSSETUP_COMPLETE (subsystems/win32/csrss/win32csr/exitros.c:786) FIXME: Need to close all user processes! (base/system/winlogon/sas.c:447) FIXME: Call SMSS API #1 (lib/rtl/error.c:910) RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping (lib/rtl/error.c:910) RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping (lib/rtl/error.c:910) RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping *** Fatal System Error: 0x0000001e (0x10000004,0x800474C6,0x07FBFB04,0x00000000) <ntoskrnl.exe:25b5 (ntoskrnl/ke/bug.c:1078 (KeBugCheckEx))> <ntoskrnl.exe:8140e (ntoskrnl/ke/i386/exp.c:995 (KiDispatchException))> <ntoskrnl.exe:8365b (ntoskrnl/ke/i386/trap.s:654 (CommonDispatchException))> <ntoskrnl.exe:474c6 (include/ddk/winddk.h:5624 (LpcpFreeToPortZone))> <ntoskrnl.exe:476f2 (ntoskrnl/lpc/close.c:173 (LpcpDestroyPortQueue))> <ntoskrnl.exe:47a81 (ntoskrnl/lpc/close.c:338 (LpcpDeletePort))> <ntoskrnl.exe:65ca7 (ntoskrnl/include/internal/ob_x.h:328 (ObpDeleteObject))> <ntoskrnl.exe:67bfb (ntoskrnl/ob/obref.c:322 (ObfDereferenceObject))> <ntoskrnl.exe:60e32 (ntoskrnl/ob/obhandle.c:669 (ObpCloseHandleTableEntry))> <ntoskrnl.exe:62486 (ntoskrnl/ob/obhandle.c:1803 (ObpCloseHandleCallback))> <ntoskrnl.exe:1c511 (ntoskrnl/ex/handle.c:206 (ExSweepHandleTable))> <ntoskrnl.exe:62780 (ntoskrnl/ob/obhandle.c:1974 (ObKillProcess))> <ntoskrnl.exe:6d3b8 (ntoskrnl/ps/kill.c:739 (PspExitThread))> <ntoskrnl.exe:6da45 (ntoskrnl/ps/kill.c:843 (PsExitSpecialApc))> <ntoskrnl.exe:14c3 (ntoskrnl/ke/apc.c:442 (KiDeliverApc))> <ntoskrnl.exe:82dd5 (ntoskrnl/ke/i386/trap.s:267 (KiServiceExit))>
I've tried to reinstall as well. The wierd thing is that an extra copy of the "serial" driver, two copies of "atapi.sys" and a copy of "pci.sys" is loaded for each time I complete the setup wizard. Right now, "serial" is being loaded 6 times, and "atapi.sys" is loading about 14 times in a row.
Now, I would be interested in how to debug this problem. Is there a registry entry that I can set in order to bypass the setup wizard. Is there a way of debugging why this freeze is happening? I know C programming fairly well, so I would be willing to hack a few things to add a printk or something if it would help.