Hi. here's the thing: got 2 HDs. HDA Master: C (with WinXP) and D, both NFTS. HDB Slave: X & Y NTFS too. Got 5 Gig. of ext3 partition on HDB (at the begining), where I installed Slackware Linux 9.0. AT first I had only WinXP. After installing Slackware Linux 9.0 on HDB, lilo only lets me boot to Linux. I can't mount any other partition. I want to dual boot my PC. I don't know on wich HD is my MBR. Can anyone help plz?

Your MBR will probably be on /dev/hda. I'm guessing that all you need to do is add an entry for XP in your /etc/lilo.conf and then type "lilo" to actually write it to your MBR. If you didn't make a boot floppy during installation, I would suggest making one now. The command is "makebootdisk". Now edit /etc/lilo.conf, make sure that you have "boot = /dev/hda" towards the top (this indicates where lilo will write to, if you wanted to create a boot floppy you would change it to /dev/fd0). At the end of the file create the following entry: other = /dev/hda1 label = XP table = /dev/hda Now save the file, quit your editor and run "lilo" as root, reboot and you should now be able to select XP from the menu.

Hello. Thanks for answering. I used WindowsXP CD to make a fixboot, and now my XP is boting. To get in Linux I use a floppy. I don't know why, but when I tried to boot from Lilo, it freezed while in the dots ............ and it booted ok from the floppy. And Slackware doesn't seem to have Grub, that doesn't use MBR. Isn't there a way to use Windows XP boot selector program? 2200+ XP 256 DDR... huh ... who cares?

Go and read about dual / multiple booting on my website (Homepage link). You will probably find what you are looking for. I use the NT boot loader as my boot manager. Hope it helps. ___________________________________________ ☺ When everything else fails, read the instructions.

Grub also uses the MBR. If the boot loader on your floppy works, you can copy it to your MBR with: # dd if=/dev/fd0 of=/dev/hda bs=512 count=1 If it doesn't have an entry for windoze and your /etc/lilo.conf isn't working, try creating a new lilo.conf with just the bare essentials....post up your lilo.conf if you can.