I extracted the latest binaries from Casper's site on the new partition, and extracted the freeloader files from the latest boch-image and placed them on the partition as well.
Then i edited my GRUB config acording to this.
My guess is that you need to edit freeldr.ini and set the correct partition number in the SystemPath entry.
Just tried to do that but it didn't help
But i'm also pretty sure this is a GRUB error, here's a new and improved version of the error code, which apears right after I choose "ReactOS" in GRUB:
tgc wrote:But i'm also pretty sure this is a GRUB error, here's a new and improved version of the error code, which apears right after I choose "ReactOS" in GRUB:
root (hd0,6)
Filesystem type unknown partition type 0x83
kernel /freeldr.sys DefaultOS=ReactOS TimeOut=0
Error 17: Cannot mount selected partition
After this message I just press a key to return to the GRUB menu.
Yes, that's most definitely a GRUB error. Partition type 0x83 is EXT2, so I'm surprised GRUB is having a problem with it. Maybe you created the partition as EXT2 in fdisk (or whatever its called in Linux ) and then formatted it as FAT? Just guessing here.
GvG wrote:Yes, that's most definitely a GRUB error. Partition type 0x83 is EXT2, so I'm surprised GRUB is having a problem with it. Maybe you created the partition as EXT2 in fdisk (or whatever its called in Linux ) and then formatted it as FAT? Just guessing here.
You're more or less right. I've now change the partition type flag to match the filesystem: FAT32. And now i get some new errors:
Failed to read the PVD.
Press any key
Partition not found
Press any key
Error opening partition on boot drive 0xe8 for file access.
Failed to read the PVD.
Press any key
No active partition.
Press any key
Error opening active (bootable partition) on boot drive 0xe8 for file access.
Press any key to reboot
And then it goes back to the GRUB menu, so i guess it's still a GRUB error.
Any ideas?
Yes, without problems. Could the problem be that GRUB can't mount FAT-diskes? I tried looking into the way GRUB normally boots windows, ("chainloader +1" etc.) but that requires that the bootloader is at the first block on the partition, which isn't the case on the partition in question...
Hmm, i'm getting nowhere
I've been playing the GRUB start commands, and i get the "best" results with the "chainloader" option, where it just hangs instead of displaying erorrs... I'll probably have to re-partition my harddisk to get ROS to work on my PC, or i'll have to get a spare harddisk, so it'll have to wait until later.