I installed Salix 13.32 on a different partition on my c drive. It uses lilo for dual booting. When I try to boot Windows 7 from lilo it tells me I need to fix the mbr. But if I try to boot Salix all is fine. What do I need to do so I can boot either one?

The Windows disc usually has the MBR. I believe you have to do a "recovery" from the windows disc to repair it, but I'm not sure how it will effect your other partition.

/etc/lilo.conf contains bootloader configuration.

A sample code will be like this :
check whether your file contains windows partition details.

If you can't correct it with the advice above, while booted into Salix go to the site below and download the bootinfoscript and run it. You will get a results.txt file with lots of useful information on drives/partitions, uuids and boot files and location. You can post it here to get help.

http://bootinfoscript.sourceforge.net/

boot_info_script version: 0.60 [17 May 2011]

"blkid" could not be found.
"fdisk" could not be found.
"filefrag" could not be found.
"losetup" could not be found.

Please install the missing program(s) and run boot_info_script again.
jb[Downloads]$

When I ran the boot script program I got this.


boot_info_script version: 0.60 [17 May 2011]

"blkid" could not be found.
"fdisk" could not be found.
"filefrag" could not be found.
"losetup" could not be found.

Please install the missing program(s) and run boot_info_script again.
jb[Downloads]$

When I went into lilo.conf it shows this

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

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/salix.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,20,255,20,255,20
# 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,29,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 = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# 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/sda2
label = Linux
read-only
# Linux bootable partition config ends

I was afraid to change anything before I asked for help. I want to thank you guys for helping me because I like this distro after trying out 15 other live distros.

I solved the problem by reinstalling. I chose the make your own lilo and chose add windows and then set it to boot from /dev/sda3. Lilo was setting it for /dev/sda1 which of course didn't work. I hope this will help some other person in the future. Many thanks to all who sent me suggestions! I appreciate it!