lilo w2000pro boot problems
 

I have a problem with booting windows2000 pro with lilo.

I have lilo installed on my first hdd (hda) and w2000 pro on the second one (hdc, ntfs). I can boot linux (debian) w/o problems but when I select the w2000 option nothing happens and I have to restart my computer.

Anyone now what the problem might be?

lilo.conf:
lba32
boot=/dev/hda
root=/dev/hda3
install=/boot/boot-menu.b
map=/boot/map
delay=20
prompt
timeout=150
vga=normal
default=Linux

image=/vmlinuz
label=Linux
read-only

image=/vmlinuz.old
label=LinuxOLD
read-only
optional

other=/dev/hda1
label="Linux(hda1)"

other=/dev/hdc1
table=/dev/hdc
label="Win2000(hdc1)"

other=/dev/hdc5
label="Win2000(hdc5)"

Why do you have two "Win2000" entries (hdc1/hdc5)? Your boot loader cares only where the bootable OS itself is, not where any other partitions are (such as, perhaps, a data drive in W2K). Your OS will figure that out on it's own and mount them, as appropriate, as it loads.

I don't know why there's two Win2000... the debian installer (or whatever) made that...

But i've tried to remove one of them but the computer stills hangs up when i try to boot from either of them...

Oh goodness things look so strange when they are not on your console.
Hmmmm... Did you type lilo at console after the modification.I know its a bit too obvious to do so but may be U forgot to.
Have you read the Lilo manual I guess it might help.
Compare ur lilo.conf with the one in man page for lilo.conf : http://man.linuxquestions.org/index....pe=2&section=5

Also, make sure your W2K installation is actually on the partition LILO is calling for it (according to the above, it's likely hdc1, but it COULD be hdc5). Use fdisk, cfdisk, or a 3PP software (like Partition Magic) to confirm your partitioning scheme, and make sure the file system for W2K is correct and where you say it is.

Wow, that's an odd looking lilo.conf file...

Anyway, winbloze likes to be #1. You know that, I know that, Bill makes it that way, and lilo doesn't care and will work with it. All you need to do is make it "believe" it's still number one, then it will be happy. How? Add this line to your winbloze entry (which should be the /dev/hdc1 entry):
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80

You might need the 81's to be 82's, but give that a try first. So now your lilo.conf entry for winbloze should look like:

And like was suggested above, don't forget to run /sbin/lilo -v after everytime to tweak your lilo.conf file.

Cool

After a short reading around, it does look like you'll want 82's. So give this a try first:
Since winbloze is your Secondary Master. 81 is for Primary Slave.

To determine this, you can post here the output of (as root) fdisk -l (FDISK -L lowercase), or simply look at the jumpers on the back of your drive(s).

Cool

Ok, I tried to do the map-drive thing so now, instead of just halting, the computer says "Hardrive read error, press ctrl-alt-del to restart" (or something like that, translated from swedish) when I select windows form the lilo menu...

fdisk -l (as root) output::

Disk /dev/hda: 128 heads, 63 sectors, 787 cylinders
Units = cylinders of 8064 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 4 16096+ 83 Linux
/dev/hda2 5 97 374976 82 Linux swap
/dev/hda3 98 581 1951488 83 Linux
/dev/hda4 582 787 830592 83 Linux

Disk /dev/hdc: 255 heads, 63 sectors, 14593 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 2089 16779861 7 HPFS/NTFS
/dev/hdc2 2090 14592 100430347+ f Win95 Ext'd (LBA)
/dev/hdc5 2090 14592 100430316 7 HPFS/NTFS

I must say the the latter part of /dev/hdc looks a little bit strange, I only have two partitions on that drive, one on 16gb and another on about 100gb...
maybe that has something to do with it, if lilo can't handle big drives or something...

and... I almost forgot, when i run lilo it says
Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80... but that's not the drive which win is on if i'm not mistaken...