Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
01-14-2010, 07:32 AM
|
#1
|
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 2,446
|
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...
Any clues?
Last edited by tronayne; 01-14-2010 at 07:33 AM.
|
|
|
|
01-14-2010, 07:44 AM
|
#2
|
|
LQ Newbie
Registered: Sep 2009
Distribution: Cent OS
Posts: 25
Rep:
|
I also got stuck in the same way , couldnt figure out anything so i just rolled back to Windows XP 
I had configured lilo in the same manner as for xp but still it said no boot manager
|
|
|
|
01-14-2010, 07:58 AM
|
#3
|
|
Member
Registered: Aug 2005
Location: Fountain Valley, CA / Thailand
Distribution: Slackware64® 14.0
Posts: 976
Rep:
|
|
|
|
|
01-14-2010, 11:15 AM
|
#4
|
|
Senior Member
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 3,669
|
You can solve this easily, if you're willing to use Windows' boot manager:
- Boot into Slackware, change lilo.conf to put lilo on the front on the HD, rerun LILO, and reboot. You'll end up back in Windows.
- Install EasyBCD (http://neosmart.net/dl.php?id=1). Have it overwrite the MBR, and use it to create a boot menu with both Linux and Windows on it.
It only takes a few minutes, will work, and won't cost you any data.
|
|
|
|
01-14-2010, 11:30 AM
|
#5
|
|
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 2,789
|
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:
Code:
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 11:31 AM.
|
|
|
|
01-14-2010, 04:08 PM
|
#6
|
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 2,446
Original Poster
|
I've just finished installing Win7 (after wiping the entire drive completely clean). It created
Code:
no-name pir/log Free Space 1.06M
sda1 boot primary ntfs 104.86M
sda2 primary ntfs 20866.87M
and left me free space of 229084.17M for installing Slackware 13.0 64-bit.
From what you suggest, I'll turn off the boot flag on sda1, leave everything else alone, install Slackware starting at sda3 with the root partition bootable.
And, with crossed fingers and toes, that ought to work.
Thanks.
|
|
|
|
01-14-2010, 04:20 PM
|
#7
|
|
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 2,789
|
I hope you will succeed. Let us know the outcome.
Cheers,
|
|
|
|
01-14-2010, 04:56 PM
|
#8
|
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 2,446
Original Poster
|
So far, so good -- installed Slackware and at the initial reboot, Win7 started up, shut it down and booted Slackware and I'm in the middle of adding back man gigabytes of stuff backed-up on DVD.
All appears to be well and thank you again for your help.
[EDIT]
Callin' it good -- everything works as expected.
Last edited by tronayne; 01-15-2010 at 06:32 AM.
|
|
|
|
11-17-2012, 12:38 PM
|
#9
|
|
LQ Newbie
Registered: Nov 2012
Posts: 6
Rep: 
|
lilo Windows 7 boot says BOOTMGR is missing
Hi all,
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.
lilo relevancies:
boot = /dev/sdb
change-rules
reset
# 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
read-only
# 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).
All help is greatly appreciated.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:29 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|