[SOLVED] Can't boot win7

ITCowboy · 06-12-2012, 01:16 PM

FOR GOOGLERS WHO HAVE JUST ARRIVED HERE, CHECK MY SECOND POST, WORKED FOR ME, PM ME IF YOU HAVE ANY QUESTIONS.

Hello fellow...linuxers(I guess). I recently (2 months ago) installed Slackware 13.37 and with it, LILO. This is the first time I've needed to dual boot between Slackware and another OS. Below is my lilo.conf file

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# 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

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda3
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = Linux
read-only
# Linux bootable partition config ends

So basically, my question is this, is there a way to fix my Windows 7 without having to reinstall Windows 7 and Slackware 13.37 again. Any help will be greatly appreciated, and I need Windows 7 for a freelance job I'm about to start next week.

PS, I've googled around solutions to this, but to no avail. EasyBCD only works on windows (from what I gather).
When I try to boot Windows 7 it says the MBR is broken (can't remember the exact wording, but the concept is basically that).

camorri · 06-12-2012, 02:33 PM

Have a look at this -->http://www.codecoffee.com/tipsforlinux/articles/6.html

Quote:

The lines we are concerned with is default=win and the last 2 lines

You may only need to add the default=Windows.

Hope this helps.

jefro · 06-12-2012, 04:29 PM

Might be able to use liloconfig to try to fix it.

See this. http://tldp.org/HOWTO/Linux+WinNT-3.html

I doubt you would need to re-install them. It is just a boot loader issue.

Side note.
It may become an issue later if you borked the recovery partition.

EDDY1 · 06-12-2012, 07:22 PM

http://neosmart.net/blog/2009/window...-repair-discs/

ITCowboy · 06-14-2012, 12:32 AM

Changed the other line from

Quote:

other = /dev/sda3

to

Quote:

other = /dev/sda2

sda2 is labeled recovery and is 100MB. Has worked wonders for me and didn't have to change lilo.conf that much.

Thanks everyone for helping me out.