hto wrote:It's up to You. I don't know, maybe it is better to wait for new Fireball's loader.
I have edited the source freeldr.c as follows:
**********************************************
VOID BootMain(LPSTR CmdLine)
{ CmdLineParse(CmdLine);
+ printf("1: CmdLineParse DONE - Press any key.\n");
+ MachConsGetCh();
MachInit(CmdLine);
+ printf("2: MachInit DONE - Press any key.\n");
+ MachConsGetCh();
DebugInit();
+ printf("3: DebugInit DONE - Press any key.\n");
+ MachConsGetCh();
DbgPrint((DPRINT_WARNING, "BootMain() called.\n"));
+ printf("4: DbgPrint DONE - Press any key.\n");
+ MachConsGetCh();
if (!MmInitializeMemoryManager())
{ printf("Press any key to reboot.\n");
MachConsGetCh();
return;
}
+ printf("5: MmInitializeMemoryManager DONE - Press any key.\n");
+ MachConsGetCh();
RunLoader();}
**********************************************
Before, all 3 old PCs did hang with black screen after loading BLUE.SYS ..
.. and now - with the edited freeldr.sys - I have different behaviore on my "zoo of PCs" (with bootCD-dbg SVN 25662):
- OK: "actual" PC AMD +1500 - DOES boot up to "Welcome to ReactOS Setup"
- OK: Dell GX260 (P 1,8 GHz) - DOES boot up to "Welcome to ReactOS Setup"
- MMX200 (Award Modular Bios 4.51PG) DOES go through ALL 5 "MachConsGetCh()"
but then hangs on "detecting hardware" (without "MachConsGetCh()"it did run
until loading BLUE.SYS and THEN it failed to show "Welcome to ReactOS Setup")
- MMX400 does add two empty lines on the "DOS"-screen and then hangs (very early .. !)
- AMD 650 Duron on K7S41GX does not even show "printf("1: ...) " but makes a hard RESET and reboots ..
Any ideas ?