[ros-dev] Bootcd installation failure

WaxDragon waxdragon at gmail.com
Tue Sep 6 14:42:13 CEST 2005

Well, I have no idea what Lucio means by that "known problem", since
he isn't very specific.  17600 is not even close to where we forked
0.2.7.  I remember there were some problems around then.  Try 17604, I
personally tested that rev and it seemed to work ok.

In the future, if you are going to call something a "known problem"
please link to the bug in Bugzilla.  If the "known problem" isn't in
bugzilla, it isn't "known" as far as I care.


On 9/6/05, Gge <gerard.gatineau at laposte.net> wrote:
> In the wiki page related to Known problems for R..2.7 -->>
> http://www.reactos.com/wiki/index.php?title=Known_Problems&curid=786&diff=0&oldid=2923
>   , it is mentionned that "The install CD wont install reactos in some
> computers. LiveCD might boot in the same computers without problems"
> I cannot Boot using Boocd based on svn 17600 and created using the
> recommended "Built Environment" as indicated in the Wiki -->>
> http://blight.reactos.at/reactos-be/ReactOS%20Build%20Environment%200.1-3.4.2.exe
> The problem is reproductible on my 2 computers in real hardware , as per
>    debug messages below.
> => Is it the same problem ?
>   (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
> (registry.c:220) Can't read registry: c0000034
> (registry.c:231) Manually set defaults
> (ntoskrnl\ldr\loader.c:252) Could not open module file:
> \SystemRoot\system32\drivers\xboxvmp.sys
> Packet: DriverEntry
> (ndis/protocol.c:678)(NdisRegisterProtocol) Called.
> (ndis/protocol.c:685)(NdisRegisterProtocol) NDIS 3 protocol attempting
> to register
> (ndis/protocol.c:764)(NdisRegisterProtocol) Opening configuration key:
> \Registry\Machine\System\CurrentControlSet\Services\PacketDriver\Linkage
> (ndis/protocol.c:773)(NdisRegisterProtocol) Unable to open protocol
> configuration
> NPF: Failed to register protocol with NDIS
> (ntoskrnl\ob\object.c:157) Invalid Size: 18 or Attributes: 1
> (ntoskrnl\ob\object.c:243) Failed to capture, cleaning up
> (ntoskrnl\ob\object.c:825) Capture failed
> (init.c:108) SM: InitSessionManager: failed to create \SmApiPort
> (Status=c000000d)
> (ntoskrnl\ob\wait.c:246) Returning: 1
> KeBugCheckEx at ntoskrnl\ex\init.c:716
> A problem has been detected and ReactOS has been shut down to prevent
> damage to your computer.
> Technical information:
> *** STOP: 0x00000071 (0x00000001,0x00000000,0x00000000,0x00000000)
> Frames:
> <ntoskrnl.exe:24c6 (ntoskrnl/ke/bug.c:498 (KeBugCheckEx))>
> <ntoskrnl.exe:b8a5f (ntoskrnl/ex/init.c:716 (ExpInitializeExecutive))>
> <ntoskrnl.exe:6706 (ntoskrnl/ke/main.c:100 (KiSystemStartup))>
> <ntoskrnl.exe:b684e (ntoskrnl/ke/main.c:294 (_main))>
> <ntoskrnl.exe:104b ({standard input}:47 (_section_alignment__))>
> Regards
> Gge
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev

#irc.freenode.net #reactos
01:03PM <filip2307> i don't know about any bug
01:04PM <filip2307> none exist
01:04PM <filip2307> ReactOS is prefect

More information about the Ros-dev mailing list