27 Aug
2005
27 Aug
'05
2:36 a.m.
greats news, it can be done :)
do me a great favor, and paste your lilo.conf :-)
Here you go:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hde
#compact # faster, but won't work on all systems.
prompt
timeout = 300
lba32
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hde2
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
other = /dev/hde1
label = Windows
other = /dev/hdf1
label = FreeLdr
Actually here is how it is setup:
Drive 1:
Partition 1: Windows XP Professional (NTFS)
Partition 2: Slackware Linux 10.x (ext3fs)
Drive 2:
Partition 1: ReactOS (used to be my shared drive between OSes) (FAT32)
Partition 2: Extra ext3fs partition.
One thing to notice here is that ReactOS is on my second hard drive
(FAT32). This makes it a lot easier except that the BPB was WRONG on my
second drive.
Now to get this working I had to hack the fat32.asm so that the Freeloader
installer (the one you run in XP) correctly writes the stuff to the second
drive. By default it did not do this. Actually it turned out that one of the
developers had this problem as well. I don't remember his name or irc handle
but he made the changes to fat.asm and helped me with fat32.asm. He checked
the fat.asm into CVS under the handle phreak.
Hope this helps...
- Devin