Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ):
(ntoskrnl\ke\main.c:289) --------------------------------------------------------------- (ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050809-r17251) Used memory 65536Kb (ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f7000, Init = 0x800f4000 (ntoskrnl\mm\mm.c:283) No current process (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Pci, 0x800f6a80) (ntoskrnl\io\driver.c:518) Initializing boot module (ntoskrnl\io\driver.c:562) Module loading (Status 0) Peripheral Component Interconnect Bus Driver (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6850) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6850) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6a60) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6a60) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6a80) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service Ne2000 failed (Status c0000001) Advanced Configuration and Power Interface Bus Driver ACPI: System firmware supports: +------------------------------------------------------------ | Sx states: +S0 -S1 -S2 -S3 -S4 +S5 +------------------------------------------------------------ Power Button: found Sleep Button: found (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6bc0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\io\driver.c:562) Module loading (Status 0) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6bc0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000034) (ntoskrnl\io\driver.c:562) Module loading (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6be0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\io\driver.c:562) Module loading (Status 0) (ne2000/8390.c:86)(NICCheck) Adapter NOT found! (ndis/miniport.c:1425)(NdisIPnPStartDevice) MiniportInitialize() failed for an adapter. (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented, have a nice day
Royce Mitchell III wrote:
Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ): ... (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented, have a nice day
Sometimes, ReactOS hangs while booting. I see the same debug messages except the last line. On the screen, the last message is 'Loading i8042prt...'.
- Hartmut
Hartmut Birr wrote:
Royce Mitchell III wrote:
Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ): ... (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented, have a nice day
Sometimes, ReactOS hangs while booting. I see the same debug messages except the last line. On the screen, the last message is 'Loading i8042prt...'.
- Hartmut
I've tried 3 times, and it's hanging every time.
From: Royce Mitchell III
Hartmut Birr wrote:
Royce Mitchell III wrote:
Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ): ... (drivers\input\i8042prt\registry.c:215) Can't read
registry: c0000034
(drivers\input\i8042prt\registry.c:226) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented,
have a nice
day
Sometimes, ReactOS hangs while booting. I see the same debug messages except the last line. On the screen, the last message is 'Loading i8042prt...'.
- Hartmut
I've tried 3 times, and it's hanging every time.
Maybe you can change it to bugcheck in NtSetEaFile, to get a backtrace?
Gé van Geldorp.
Royce Mitchell III wrote:
Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ): [snip]
This looks like the syscall tables are mismatched between ntoskrnl and ntdll. Have you tried clean build?
- Filip
-
Filip Navara -
Ge van Geldorp -
Hartmut Birr -
Royce Mitchell III