Following situation: Windows 2000 is installed on first hard disk sda, W2K
boot loader in /dev/sda1, Linux will be installed on second hard disk sdb
with LILO in MBR (boot=dev/sda)
I have a FAT32 partition for data exchange with W2K on sda6. The installer
lets me choose /dev/sda6 to be included in LILO ALTHOUGH this partition is
not bootable and the W2K boot manager is on /dev/sda1. But this partition
can't be selected from within anaconda. I have to do it manually after the
installation is finished. This should be fixed for future versions since
W2K and NT can meanwhile perfectly boot from within LILO.
Same situation occurs for Windows NT.
Strange. The installer looks for FAT partitions that are marked as active, so I
can't explain why this would happen.
Can you send the output of 'fdisk -l /dev/sda'?
Okay, here is the output of fdisk -l /dev/sda
Disk /dev/sda: 255 heads, 63 sectors, 2221 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 522 4192933+ 7 HPFS/NTFS
/dev/sda2 523 2221 13647217+ f Win95 Ext'd (LBA)
/dev/sda5 523 1044 4192933+ 7 HPFS/NTFS
/dev/sda6 1045 1299 2048256 b Win95 FAT32
/dev/sda7 1300 1758 3686886 7 HPFS/NTFS
/dev/sda8 1759 2221 3719016 7 HPFS/NTFS
/dev/sda6 has been proposed by anaconda, but /dev/sda1 should be included.
Ok, I can explain this behavior. The installer scans for FAT partitions. We
don't currently handle NTFS partitions at all in the installer. If your
/dev/sda1 partition was FAT instead of NTFS, then things would have gone
smoothly. Some people apparently have problems booting NTFS from LILO. So,
even if we let you add a boot image manually, it still may not work.
We do need some work on the bootloader, but we can't handle it in the current
development cycle. We will address this issue in the future, but I'm deferring
it for now.
This will be handled better, allowing you to add undetected options, for the