Usually when I get nearer to the problem the OP would show up a can of worms and things that have been hidden from me. May be trying to see how good I can speculate.
Well in a PC the (hd0) is the first disk to be booted. Therefore it is a data only disk then Grub must be using the MBR of the hda.
Therefore if Windows was installed as the 2nd disk in the PC then it will be fired by commands
Code:
title Windows in the 1st partition of 2nd disk
rootnoverify (hd1, 0)
chainloader +1
because sda is (hd1) as recorded by Grub as the 2nd disk.
However if Windows was originally installed as the 1st disk and then you changed the disk order in the Bios then a different set of commands is needed, like this
Code:
title Windows installed as (hd0,0) but now boot as (hd1,0)
rootnoverify (hd1, 0)
map (hd1) (hd0)
map (hd0) (hd1)
chainloader +1
The two map statements re-map the windows disk from (hd1) back to (hd0) position for the purpose of booting and then revert back when Windows exits.
So take your pick or show me another can of worm.
---------------------------------------------
seelenbild28 ,
There is nothing wrong Lilo. It is stable. It is not old-fashion either because it is the official Linux boot loader stands for "
Linux
Loader" .
It is still actively maintained where Grub, the lagacy version v0.97 we are using, has been declared obsolete and no longer be maintained. GNU/Grub has since switched to Grub2 but they haven't any documentation for the new system. It has been in this situation for the last three years.
Also it is true that the kernel 2.6.20 has led to a major change of device names but this does not affect OP's booting problem with Windows. Every Linux boots a Windows by chainloading and no Linux device name is needed by Grub in chainloading.