Hi! I have a problem concerning one of my babies. This baby of mine has two OS, Slackware and Winbloze. I think one of the system file of my Winbloze got absolutely corrupted and I'm experiencing difficulty at the moment, it frequently freezes after booting. So, I thought it would be best if I format the partition where winbloze is and reinstall it. My dillema is that, if I format that partition and reinstall winbloze, it will overwrite the MBR where lilo resides and I may not be able to boot Slack. I don't want my Slack partition to be lost since I use it for work. Can I just reinstall LILO after installing winbloze? or are there other ways to deal with this thing? My /boot and / resides in the disk where winbloze partition is the other partitions are on another disk.

Yes, it's no problem to run LILO again. As long as winbloze doesn't do anything stupid (and there is never a guarantee for this ) you should be fine. Many people install multiple distros on the same drive as winbloze.

After you have reinstalled bloze, boot your Slackware from the installer (follow instructions on screen) or use a live CD. You can chroot into your Slackware system and run lilo from a root console.

lilo -v -b /dev/hda (if hda is your drive)

Rand

I normally boot off a boot CD, chroot into the Slack environment and just run lilo

thanks for the quick reply guys. i almost thought i was desperate.

Don't worry, nothing on Slackware is desperate except my problems

@Randux

hmm unfortunately i still havent fixed my problems. i get these messages after chrooting to /dev/hda2 after booting from the slackware cd:

Warning:'/proc/partitions' does not exist, disk scan bypassed
Warning: Unable to determine video adapter in use in the present system.
Added Windows *
Fatal open /boot/vmlinuz

my partitions are:

/dev/hda1 = winbloze
/dev/hda2 = /
/dev/hda3 = /boot

is there a way to pass a parameter to lilo where it could detect my /boot ?

In the chroot, you will have to run before you run .
The warnings about proc can be overcome by running before running lilo, but the warnings are probably harmless anyway.

Eric

on a side note. i will be installing lilo into /dev/hda1 which is the mbr. will that be a problem reinstalling lilo?

I hope you meant you'll be installing lilo into /dev/hda which is the mbr? In that case, there won't be a problem.

Eric

yeah. that was a mistake on my part

thank you very much, its working now, with the exception of the graphical part being lost, i think its just a minor problem. thank you very much.