"BOOTMGFR" is missing in windows 7 need HELP Please.
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
"BOOTMGFR" is missing in windows 7 need HELP Please.
hello Guys i installed slack 13.0 on acer laptop :/ a friend help me then he go after he go i found up that i cant load windows 7 :/ BOOTMGR Is MISSING bla bla bla i tried to edit the lilo.conf but nothing same this is a paste of my "fdisk -l"
root@darkstar:~# fdisk -l
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5f6100de
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 13064 104830976 7 HPFS/NTFS
/dev/sda3 13064 30402 139262976 83 Linux
Disk /dev/sdb: 2030 MB, 2030043136 bytes
255 heads, 63 sectors/track, 246 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc3072e18
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 246 1975963+ b W95 FAT32
and this is the lilo.config
root@darkstar:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
label = win7
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = slack
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
root@darkstar:~#
hope to help my Guys :-s cuz i dont have any one to fix it for me
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Ah, the joys of Microsoft.
Looks like /dev/sda1 is bootable -- you need to change that: use cfdisk or whatever you choose and turn off the boot flag on /dev/sda1 and turn on the boot flag on /dev/sda3 (your Slackware partition). For example,
Code:
cfdisk /dev/sda
will show you something like this when you've got it.
Code:
cfdisk (util-linux-ng 2.14.2)
Disk Drive: /dev/sda
Size: 250059350016 bytes, 250.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 30401
Name Flags Part Type FS Type [Label] Size (MB)
-----------------------------------------------------------------------------------------------------------------
Unusable 1.05 *
sda1 Primary NTFS 104.86 *
sda2 Primary NTFS [^B] 20866.67 *
sda3 Boot Primary Linux ext3 10001.95 *
sda5 Logical Linux swap 5996.23 *
sda6 Logical Linux ext3 20003.89 *
sda7 Logical Linux ext3 20003.89 *
sda8 Logical Linux ext3 20003.89 *
sda9 Logical Linux ext3 20003.89 *
sda10 Logical Linux ext3 20003.89 *
sda11 Logical Linux ext3
Lol @ microsoft ur lilo.conf looks ok just changer the bootable flag in fdisk to /dev/sda3 then if you still can't get windows you may need a new bootmgr file. If you can get tpo a windows command prmpt you can make a new one, but the easiest way would be to boot slack, mount win7 (I'm pretty sure slack auto mounts it when it detects it at installation) throw a win7/vista dvd or iso into ur comp, copy the bootmgr file off the root of the dvd/iso to the root of the win7 dir, unmount and reboot.
GNU/Linux Slackware doesn't need or use the boot flag. The OP seems to lack a bootloader period.
If you want to attempt to use the current install and the 'lilo' boot loader is just the problem. Then the easiest way would be to use the install CD1/DVD to boot the system as if you were going to install.
After you get to the login then from the cli (command line);
Code:
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #this is the device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #your_device= sda or hda this will only test
~#lilo -v -b /dev/your_device #this will write MBR to your_device
When you edit the 'lilo.conf' file to include any additional information or stanza for windows, another Linux or whatever then you will need to re-run the 'lilo' command as illustrated above. If you follow the above and your original install was OK then you should now be able to re-boot your system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.