Hi,
I'm trying to run ReactOS (3.11) from Grub and without a cd. I have win98 on a SCSI C drive and Puppy Linux frugal install boot files on IDE D drive. I tried copying an "unzip'd" iso to the D drive and added the appropriate menu item to the grub menu, similar to my Puppy entry (Title, rootnoverify, kernel). When i tried booting ReactOS, it started the sys file and then said it couldnt find freeldr.ini. I tried both Live and Install iso's....same result. How do i get it to find the ini file?
Thanx
Hi,
On Wed, Jan 13, 2010 at 2:14 PM, Elliot S elliot@pcdialup.com wrote:
I'm trying to run ReactOS (3.11) from Grub and without a cd. I have win98 on a SCSI C drive and Puppy Linux frugal install boot files on IDE D drive. I tried copying an "unzip'd" iso to the D drive and added the appropriate menu item to the grub menu, similar to my Puppy entry (Title, rootnoverify, kernel). When i tried booting ReactOS, it started the sys file and then said it couldnt find freeldr.ini. I tried both Live and Install iso's....same result. How do i get it to find the ini file?
Did you configure your grub and freeldr based on the documentation here:
http://www.reactos.org/wiki/Boot_FreeLoader_from_GRUB
Thanks
On Wed, Jan 13, 2010 at 2:58 PM, Steven Edwards winehacker@gmail.com wrote:
Did you configure your grub and freeldr based on the documentation here:
Sorry I guess if it loaded the sys it seems like it is clearly a freeldr issue. Perhaps there is some confusion coming in from the mixture of scsi and ide devices.
Well i got further before hitting the ndis.sys freeze.
Instead of grub booting from the unzip'd iso, i grub booted directly from the iso via mem:
map --mem (hd0,0)/ReactOS-LiveCD.iso (hd32) map --hook chainloader (hd32) boot
It starts to load the drivers, but stops after ndis.sys. I dont have a network card, just a hardware modem. Disconnecting usb didnt help.