Booting problem [0.2.0]: can't find exports & mouse - Ros-general

10 Mar 2004

  I wrote on ~Feb 24 that has a problem booting ROS (binary dist. v0.2.0). JH 
asked me for debug log, so after a small delay here it comes (my own comments 
're prepended by dash #):

# running
# > loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=SCREEN bootc.lst
# Now I'm in a blue screen & receiving next messages
# ...
DriverBase for \SystemRoot\System32\kbdus.dll: ce488000
(ntuser/input.c: 86) Win32K: Failed to open mouse
# although I have Microsoft-compartible mouse on COM1
LdrGetExportByOriginal (Original 167) = 76168223
LdrGetExportByOriginal (Original 71) = 76167600
LdrGetExportByOriginal (Original 151) = 76168a2c
LdrGetExportByOriginal (Original 328) = 7616948e
LdrGetExportByOriginal (Original 386) = 7616a345
LdrGetExportByOriginal (Original 332) = 761696da
LdrGetExportByOriginal (Original 334) = 7616979f
LdrGetExportByOriginal (Original 339) = 76169cc9
LdrGetExportByOriginal (Original 338) = 76169c6f
LdrGetExportByOriginal (Original 154) = 76168af2
LdrGetExportByOriginal (Original 169) = 76167fe6
LdrGetExportByOriginal (Original 73) = 76167b6a
LdrGetExportByOriginal (Original 152) = 76167ede
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of 
'wineoss.drv' (Status c0000135)
(NTDLL: ldr/utils.c: 1191) LdrGetExportByName(): failed to find 
GetModuleHandle16
(NTDLL: ldr/utils.c: 1191) LdrGetExportByName(): failed to find LoadLibrary16
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of 
'msacm.drv' (Status c0000135)
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of 
'midimap.drv' (Status c0000135)
# after this point it hangs up

  Can anybody deal with this? ROS is unpacked into c:\reactos (as should be), 
loaded from clear DOS (which is itself booted from floppy). If you need more 
info, ask.
  One more problem: this log is handwritten from screen, I've no machine near 
me to write a log to it through COMx, so how do I make ROS loader write log 
to a file (you see, those errors appear after drives're detected)?