Hi!

I have now installed a new systemdisc that i have the following partitions on:

Primary partition 1: Linux ext2 Start Cyl:0 End Cyl:792
Primary partition 2: ntfs Start Cyl:792 End Cyl:1849

Primary logic:
Logical 1: ext2 Start Cyl:1849 End Cyl:2112
Logical 2: swap Start Cyl: 2113 End Cyl: 2179
Logical 3: Ntfs Start Cyl:2180 End Cyl: 10336


When i add the primary ntfs partition to my lilo.conf it fails.
Do i only use my primary ext2 partition, then everything works just fine.
But i need the dualboot.

The error i get from lilo when i add the primary ntfs partition is this:

Ignoring entry 'lba32'
Device 0x0300: Invalid partition table, 2nd entry
3D adress: 1/96/792 (804384)
Linear adress: 1/0/11886 (11981088)

I have also tried with lba32 and without lba32.
Also tried lilo -L.

You can se my lilo.conf below:

boot = /dev/hda
message = /boot/boot_message.txt
prompt
change-rules
reset
vga = normal

other = /dev/hda2
label = DOS
table = /dev/hda

image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only

I really dont know what makes this problem, i have been using linux for a couple of years and never experienced anything like this....

What happens if you remove the table=... entry? I've never need to use this.

cheers

Jamie...

Same error without table..

I think i need that anyway..
Anything else?

Should your NTFS partition really start on cylinder 792 or should this say 793? If it really is 792 I'm wondering if your ext2 partition has overwritter the start of your ntfs partition, hence the invalid partition tables.

cheers

Jamie...

I have got it workin now=)
I used cfdisk instead of another partition manager..

Now it works just great..
Just one question left=)
Should the /boot partition be Bootable ?

As far as I know it should be, but I'm not sure how necessary it is if you boot manager come into play first.

cheers

Jamie...