(no subject)

[wld]

On 1/13/06, oleksandr korneta <mai11ist at fastmail.fm> wrote:
> Hello,
>
> I have 2 hard drives in my box with linux and windows on hda and hdb
> respectfully. My grub is on mbr of hda. And windows loader is on mbr of
> hdb. I can boot with no problems into windows when I set hdb to be
> master drive. However when I try to boot into windows from current
> configuration the only message I get is
>
> chainloader +1
>
> which is the string from the grub.conf
> Nothing more happens.
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/hda3
> #          initrd /initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> #hiddenmenu
> title Fedora Core (2.6.14-1.1637_FC4)
>          root (hd0,0)
> #       kernel /vmlinuz-2.6.14-1.1637_FC4 ro root=LABEL=/1 vga=792
>          kernel /vmlinuz-2.6.14-1.1637_FC4 ro root=LABEL=/1
>          initrd /initrd-2.6.14-1.1637_FC4.img
> title w2k
>          rootnoverify (hd1,0)
>          chainloader +1
>
> # end of grub.conf
>
>
> and here is the content of my boot.ini
>
> [boot loader]
> timeout=3
> default=multi(0)disk(1)rdisk(1)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> Professional" /fastdetect
>
> I tried to change the partition number  here from 0 to 1to tell the OS
> that it is actually on the slave drive.
>
> I suspect that for some reason windows does not like to have its
> bootloader on a slave drive. This is just a pure guess (assuming that
> everything I've done is ok). But if it is true, is there any workaround
> or do I have to replace my grub with ntldr like the fellow couple
> threads above?
>

I have the same setup as yours. You should 'lie' to Windows
so that it believes that it is on the master drive. Use grub's 'map'
command. See my Windows section in grub.conf below:

title w2k
        map (hd0) (hd1)
        map (hd1) (hd0)
        rootnoverify (hd1,0)
        chainloader +1

--
V.Rudenko