Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having some trouble setting up a dual boot with Win XP and Slackware 13.1. Lilo lists both Linux and Windows, but when I select Windows, all I get is a black screen. I have two hard drives, sda1 and sdb1. I first installed Windows on sdb1 (it is a smaller, older drive). I then installed Slackware on sda1 and selected to install Lilo on the MBR. I'm guessing that by doing this, I wrote over the Windows information that was already there. Could this be my problem? I feel like this should be an easy fix, but I just don't know where to start in order to fix it.
If it helps, here is the end of my lilo.conf file.
# Windows bootable partition config begins
other = /dev/sdb1
label = Windows
table = /dev/sdb
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends
installed Slackware on sda1 and selected to install Lilo on the MBR. I'm guessing that by doing this, I wrote over the Windows information that was already there Could this be my problem?
Yes, part of it at least. This usually happens in the reverse, installing windows automatically overwrites the mbr without asking or notifying the user. At least you were notified. Another part of the problem is that windows is not on the first drive so it needs to be mapped. I haven't used Lilo for years so don't know how to do this. You could try searching "boot windows from second drive with lilo" or something similar.
I tried mapping the drives, and now I get an error
NTLDR missing... press ctrl alt delete to restart
I guess that is at least a step in some direction, because before I just got a black screen.
Could I fix the MBR using the Windows CD and then re-install Lilo (or maybe Grub) somewhere else? Or, if I fixed the MBR, would I have to re-install Lilo?
Probably just a matter of getting the correct partition. Sounds like you picked the recovery partition. Try /dev/sdb2 before messing with other installs.
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459
Rep:
What happens when you boot to the other drive,I mean you have two sda1 and sdb1...using the F number at first boot select the drive to boot from,on my N01 box I use F11 on my N02 box I use F8,if you have,nt got an F number you can change the boot order in the BIOS.
While you are working on the problem you can discover other ways to boot an OS...for example Smart Boot manager on the UBCD will boot your windoze and from the 13.1 DVD you can use pkgtool and create a boot stick for Slack.
There are several ways to do most things... ! I wish I knew more of them. LOL
I do have the right partition. I tried changing /dev/sdb1 to /dev/sdb2 in lilo.conf and when I ran lilo I got a fatal error about not being able to load /dev/sb2.
fdisk -l gives...
Device Boot Start End Blocks Id System
/dev/sda1 * 1 38305 307684881 83 Linux
/dev/sda2 38306 38913 4883760 5 Extended
/dev/sda5 38306 38913 4883728+ 82 Linux swap
Device Boot Start End Blocks Id System
/dev/sdb1 1 30400 244187968+ 7 HPFS/NTFS
If I just reinstalled everything, and put Windows on the first drive and Slack on the second, could that fix my problem? I would physically switch the drives first, because I want the Slack drive to be the bigger drive. I don't want to do this though, because it would take a good part of my day.
-If you have one, try to boot from windows CD,
-select repair mode,
-change direcory (cd) to CD ROM drive
-and then copy the NTLDR, maybe in i386 directory. cp NTLDR c:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.