SlackwareThis Forum is for the discussion of Slackware Linux.
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 opted to install LILO into the Master Boot Record and now I can get into Slackware fine but when I select Windows, the screen switches over but I just get a blinking '-' in the top left hand corner of the screen. I've read afew solutions, one on a Microsoft website itself. I was just wondering if any of you here have had some first hand experience with this sort of thing. I did set a recovery point just before I started to install Slack so if there is anyway I can get to that, or just edit the /etc/lilo.conf file to point to the right place, that'd be great. I'm fairly sure that XP is on hda1. Thanks for the help.
My best recommendation to you when dual booting Linux and Windows is to let windows have controll over the MBR and use the NT Bootloader to start up Linux! Yes this is possible, all you need is a program called 'bootpart' which can be found here: http://www.winimage.com/bootpart.htm
However, before you do that, you will need to do two things. The first one is to reinstall LILO into the primary linux partition and NOT the MBR. Once you have done that, you will now need to rewrite the NT Bootloader onto the MBR since you wiped it out with LILO. This can be easily done by booting from your WindowsXP CD and telling it to go into the "Recovery Console". Once you are in the recovery console, simply issue the command 'fixmbr'.
The next time you restart your computer you should boot directly into Windows XP. Once in windows extract the bootpart zip file above and read the included documentation, it's short, very easy to follow and has lots of examples, including one specifically for linux.
After you have done all that the docs say to do, the next time you restart your computer you will be prompted with the NT Bootloader Menu (very similar to the LILO menu) and one of the menu options should be "Linux". Just choose that option and low and behold linux should start to boot.
Another nice feature of this is that if you decide that you want to totally remove linux all you have to do is format the partition that linux is on and it wont mess with your ability to boot into windows.
If you use this method, lemme know how it works out.
I would use the recovery CD's but when I booted the first one up, it said "Continuing will result in loss of all user information" or something like that. I still want to keep the contents of my winxp partition if at all possible. Does your method allow this? Thanks for the suggestion.
EDIT: Do you mean recovery CD's or the actual WinXP install CD? I bought a Compaq and it came with alot of software but no XP CD. It has the product ID key label on my tower but it didn't include the CD so if that's what the method calls for...
Last edited by a_priebe47; 07-30-2004 at 06:41 PM.
My method does not touch any DATA partitions, all it does is mess with the MBR. I was talking about the XP Install CD. I hate it when OEM computers dont come with the original CD's. One option is to go to www.bootdisks.com and grab a '98 or ME bootdisk and boot from that. Once at the A:> prompt type "fdisk /mbr" and that should also do the trick.
Do you have LBA enabled on your harddrive? If not, enable it in CMOS, and try to boot into windows, again. And use Lilo.
You should not have to allow Windows to load your duel boot. Lilo works just fine. I'm running Slack and XP =). Besides, Lilo is the easiest route to take without having to mess with creating an image disk and repairing your MBR. Screw that, man!
I couldn't find LBA anywhere, however, I did find an 'Onboard Lan Boot ROM' that was disabled. And I know that this next question will sound (and is) very newbish, but how do you write to floppies?
Hang back on creating a floppy. I bet you've got an option to enable LBA, just gotta find it. If you select your harddrive (in CMOS), it should give you an option for that. If that doesn't work for you, enter CMOS and note it's version. Then, google a string related to LBA and your CMOS version. You should be able to find something to help you in that department. Here's what I did to duel boot:
1. Enabled LBA for Harddrive 0 (aka hda) in CMOS;
2. Uninstalled Lilo as root, "localhost# lilo -U";
3. Reinstalled Lilo, "localhost# lilo";
4. Rebooted
Bingo, it worked. I've also allowed Windows to manage my boot options, but Lilo is much easier =)
But when I selected Windows, it still gave me the blinking hyphen. Did the commands:
lilo -U
and lilo
install lilo to my / or did it rewrite it to the MBR? And if I just uninstalled lilo now and rebooted, would I not be able to enter anything or would it just boot Windows?
Last edited by a_priebe47; 07-31-2004 at 12:42 AM.
Lilo writes to the MBR *not* /. You ran "lilo -U" which removes lilo from the MBR. The command "lilo" writes a new image to the MBR. If LBA is enabled and you wrote a new MBR with Lilo, you should be good to go. Give it a shot, and be sure to have a boot diskette handy just in case =).
I like to be the voice of dimwitted simplicity, so here we go: what happens if you try to re-install LILO using expert mode, and to the MBR (which I have found is the best option for dual-booting slackware and windows XP, at least on my comp). The expert mode should show you exactly what OS is on what partition, and give you the automatic option of adding it to the LILO bootloader or not. Anyway, I managed to forget the exact command (it's late, it's Friday, blablabla), but I think it's "liloconfig" (do a "whereis liloconfig" to make sure it exists before freaking out if it doesn't work).
Reading how the original poster has poked at the LILO, if the problem was with MBR, it should have been fixed by now. It starts to look more and more like a WIndows issue, rather than MBR.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.