Re: [ros-dev] Re: cdron.sys freezes the system

[Hartmut Birr]

Jan Schiefer wrote:

>   I'm running it with QEMU 0.7.0.
>  Command line: qemu -user-net -cdrom ReactOS-LiveCD.iso -serial stdio
>  -boot d
>
>  When I starts "Loading cdrom.sys..." is the last thing displayed.
>
>  This is the debug output:
>
>  (ntoskrnl/ke/main.c:292)
>  ---------------------------------------------------------------
>  (ntoskrnl/ke/main.c:293) ReactOS 0.3-SVN (Build 20050621-r16205)
>  Used memory 131072Kb
>  (ntoskrnl/mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80100000,
>  Init = 0x800fd000
>  (ntoskrnl/mm/mm.c:327) No current process
>  (ntoskrnl/ldr/loader.c:327) Could not open module file:
>  \SystemRoot\system32\drivers\ne2000.sys
>  (ntoskrnl/io/pnpmgr.c:1785) Initialization of service Ne2000 failed
>  (Status c0000001)
>
>  It seems that ne2000.sys can't be opened.
>  When I search for ne2000.sys it is found in
>  reactos/output-i386/drivers/net/dd/ne2000 and
>  reactos/output-i386/livecd/reactos/system32/drivers.
>  
I think it has something to do with the hardware detection routine of
the ne2000.sys driver. On qemu for windows I see:

(ntoskrnl\ldr\loader.c:327) Could not open module file:
\SystemRoot\system32\drivers\ne2000.sys
(ntoskrnl\io\pnpmgr.c:1785) Initialization of service Ne2000 failed
(Status c0000001)
(drivers\net\dd\ne2000\ne2000\8390.c:71)(NICCheck) Found adapter at 0xc100

The plug and play manager does try to start the same driver at different
points while booting. The first two lines comes from the very early boot
phase, where only some low level drivers are available which are loaded
by freeldr. The third line comes from the second try to load ne2000.sys.
You should change the debug trace level to MID_TRACE or MAX_TRACE in
ne2000\main.c to see what is going on.

- Hartmut