Slackware - dual boot Windows with LILO

[MDesigner]

I figure JohnT will eventually come in here and tell me to check his web site :) (which I've already done). I know that one way of doing it is to install Linux, then copy the bootblock into a file, and then install Windows and point the C:\boot.ini to that bootblock file.

But I'd really rather have lilo in control of the boot process, so I can easily add new entries and such. My question is, can I swap the process around and install Windows first, then Slackware? When Slackware installs, will it see the Windows partition and automatically create a lilo.conf entry for it? If not, what should I put in lilo.conf, assuming Windows is on /dev/hda1? Just this?:

other = /dev/hda1
label = Windows

[tmcG]

I have this exact setup MDesigner.

I installed XP first and then Slack.
Slack does not automatically create an entry in lilo.conf for Windows.
(If you are using NTFS as your Windows partition, you will need to use modprobe ntfs to install the module so you can read the NTFS partition).

I edited LILO in exactly to same way as you suggested and they co-exist fine.

Remember to issue the lilo command as root after modifying lilo.conf!

Good luck!:)

[JohnT]

Windows is installed first. With the installation of 10.0 it detected my NT and inserted the configs in Lilo, but I never used them and removed and customized Lilo to my preferences. Its no big thing to do it the way I outlined on mysite, but I big thing when Lilo and NTLDR dont play well together, so make a bootdisk by all means.

[tmcG]

I apologise if I mis-informed MDesigner. I use Slack 9.1 and it does not detect the NTFS partition during installation (unless I am doing some thing wrong but I have installed Slack quite a few times with Windows on the same disk and it has never detected it)

Is this a new feature in Slack 10.0?

[JohnT]

Originally posted by tmcG
I apologise if I mis-informed MDesigner. I use Slack 9.1 and it does not detect the NTFS partition during installation (unless I am doing some thing wrong but I have installed Slack quite a few times with Windows on the same disk and it has never detected it)

Is this a new feature in Slack 10.0? Yes, anyone that has used Slack for awhile will notice changes in 10.0. NTFS, as well as FAT is detected during install and the option to add to /etc/fstab at first boot. Some executables have been moved around also. Some script changes in /etc....I'm sure there are more these are just the ones I have encountered so far.

[MDesigner]

Wow, it was amazing. Slackware detected my Windows partition and even created a lilo entry for me. :) Both OSs boot perfectly.

I can't create a bootdisk, I have no floppy drive. Is it common in a Linux/Windows dual boot environment for Windows to just not boot one day?

PS: It was nice to see Slackware install on a REAL machine (so far I've installed it on some pretty sub-par systems). Installation flew by on my 2GHz Athlon.. it was a sight to behold. :)

[JohnT]

Is it common in a Linux/Windows dual boot environment for Windows to just not boot one day? Its not common, but lets be realistic, anything is possible. The only time I've had a problem with my set-up is when some errant installing distro automatically places a boot manger somewhere I don't want it. A boot with a cd and a fix/mbr takes care of that problem though. I will never understand why people only provide one failsafe boot (cdrom) when floppy drives are so cheap. :confused:

[MDesigner]

Bah! Floppy drives. :) It's an ancient technology and I'd rather not contribute to it by purchasing floppy-related products. We should be using CD-ROMs, USB drives, and the like. Mark my words: one day, operating systems will allow you to create an emergency boot *CD*.. not a floppy.

Anyway, I already tested my boot configuration.. Slackware & WinXP both boot fine, so I should be OK.