[SOLVED] Win7 Installed, Slackware64 13.0 Installed BOOTMGR is missing
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Win7 Installed, Slackware64 13.0 Installed BOOTMGR is missing
Arrgghh! I discovered that I could not install Win7 64-bit in VirtualBox (because an Intel T4300 doesn't have VT-x/AMD in it, drat) so, OK, let's just install Win7 64-bit then install Slackware 13.0 64-bit and dual-boot the thing for a while.
Win7 worked fine -- got all those important security updates and all that. Installed Slackware. Works fine. Shut down Slackware, reboot, select Windows from the Lilo start-up, BOOTMGR is missing, press ctrl+alt+del to restart...
Distribution: Slint64-14.2beta2 on Lenovo Thinkpad W520
I have a dual boot Windows 7 + Slackware64-13.0.
1) Format your HDD (with gparted, fdisk, cfdisk, whatever):
- Keep one partition for W7 (the installer will probably add a small boot partition in it during install and will use the remaining space as another partition for W7 itself)
- Format remaining space for Slackware as you see fit.
2) Install Slackware
3) Make Windows boot partition not bootable but Slackware's root partition bootable with fdisk or cfdisk
4) create or edit /etc/lilo.conf including:
boot=/dev/sda4 # Adapt to your layout, here sda4 is Slackware's root partition
other = /dev/sda1 # Here sda1 is Windows' boot partition (*not* bootable)
label = Windows
table = /dev/sda
Should work. At least, works here
Last edited by Didier Spaier; 01-14-2010 at 12:31 PM.
Got the latest Slackware distr. and loaded it onto /dev/sdb1, Windows 7 was already on /dev/sda1 and had lilo already on /dev/sda working fine.
Now, Linux boots, but when I attempt to boot Windows 7, lilo reports "Loading Windows", then the screen shows "BOOTMGR is missing, press ctrl-alt-del to reboot". I've tried the suggestions above to no avail. I wrote lilo to /dev/sda and /dev/sdb, made /dev/sdb the first drive in the boot sequence.
boot = /dev/sdb
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb1
label = Linux
# Linux bootable partition config ends
I did overwrite the older lilo (which would boot Windows 7) with the the lilo from the Slackware install (probably the real issue, but don't know how to fix).