I think the problem with the installer is perhaps twofold:
* It may only look for FAT partitions when setting up dual boot;
no one would ever want to boot between Linux and any other OS than
DOS-Based Windows, would they?
* Even if it recognizes NTFS partitions as belonging to another OS (it
_should_ recognize any non-ext2 & non-swap partitions as belonging to
another OS, I think), Microsoft did change the partition ID for NTFS
5. It shows up as... I don't remember. If you would, post the
output from `fdisk -l /dev/hda`. I'm curious.
As to solving your problem, it'll require only a little digging in
/etc/lilo.conf, and _maybe_ some disk editing from fdisk.
First, let's see that your NT root partition (I mean, "C: drive", damn
those drive letters!) is marked active in the MBR. Try this:
wopr:/root:1013# fdisk -l /dev/sda
Disk /dev/sda: 255 heads, 63 sectors, 1106 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 15 120456 6 FAT16
/dev/sda2 * 16 549 4289355 7 HPFS/NTFS
/dev/sda3 550 574 200812+ 82 Linux swap
/dev/sda4 575 1106 4273290 83 Linux
See the asterisk beside my /dev/sda2 partition? That means it's marked
"active" (aka "bootable", thus fdisk's column label of "boot"). Note that
my NT partition is active, NOT my linux partition or DOS partition (yes, I
do have three OSes on this computer).
If the asterisk is not present beside your NT's "C: drive", you'll need to
set the partition active. Run fdisk on the correct hard drive:
# fdisk /dev/sda
I'm running it on SCSI disk "a", your system may be different. Primary
Master IDE drive is "/dev/hda". Your system probably uses one of those
two devices.
Now, type "p" and <ENTER>. Note how it prints out the partition table,
just as running "fdisk -l *device*" does? Now, take note of the partition
number for your "C: drive". Type "a" and <ENTER>. It'll ask you for a
pertition number; you need to enter the one for your "C: drive".
Now, enter "w" to save changes and quit. Regardless of whether or not it
recommends a reboot, don't reboot yet. We still need to edit
/etc/lilo.conf.
Open it up in your favorite text editor. I like vi, but don't try it if
you're not familiar with it.
You probably ought to delete the "floppy" entry. I don't know why the
hell they even put it in there. I don't know of a PC bios that can't boot
from the floppy drive on it's own.
Anyhow, we need to make a new entry for NT. I hope you remembered the
device for your "C: drive"! You'll need to enter it in here. Use this
template:
other=/dev/sda2
label=nt
Again, notice that this is set up for my system. Change what you need
to. This section goes at the bottom of the file. If you'd like NT to
boot as default, add a line just before "image=/boot/vmlinuz":
default=nt
This will boot the section labeled "nt" as default. If a "default=" line
is not present, the first label mentioned will boot as default.
Now, save and exit. Run "/sbin/lilo", which updates LILO in your
MBR. Reboot. Are you, hopefully, satisfied?
A few notes:
1) I am, in here, presuming NT 5's (I mean, Windows 2000; damn their new
version numbering scheme!) boot loader behaves mostly the same as NT
4's. I'm pretty sure this is true.
2) Please, never run a "recommended" install again. I always advocate
knowing what is going on your computer, and where it's going.
3) If this is too confusing, flame me and I'll clean out all the non
sequitur cruft.
4) I'm a lot less help with the QT error. It looks like the QT libraries
aren't correctly installed, which is very, very, bad, if you plan to use
and KDE applications. I can suggest installing the QT RPMS again. Also
try booting into a non X startup - "linux 3" at the LILO
boot: prompt. That'll get you into Linux, from where you can try running
"startx" and seeing if KDE'll load on it's own. Probably not, but at
least you can log in and check on those RPMS. If in doubt, mount the
CD-ROM and run 'rpm -Uvh /mnt/cdrom/Mandrake/RPMS/qt-*'.
It won't necessarily fix your problems, but it ought to guarantee that the
qt RPMS _are_ in fact, installed. If it spits out errors, then you'll
know what the problem is.
-Matt Stegman
<[EMAIL PROTECTED]>
