Re: Not able to map hd1->hd0 for booting Windows on hd1

[Ground Zero]

Let's summarize all the alternative booting options that have been proposed
to me and the outcome. I'm trying to boot Windows98 from the 2nd hard-disk
where it has a classic setup (C on primary, D on logical in extended):

CASE 1:

        map (hd0) (hd1)
        map (hd1) (hd0)
        rootnoverify (hd1,0)
        chainloader +1
        makeactive
or
        root (hd1,0)
        map (0x81) (0x80)
        map (0x80) (0x81)
        makeactive
        chainloader +1

OUTCOME: Guess what, that freeze was only apparent. It wasn't a freeze, just
a very long (15-20 seconds) delay. After that the second drive does boot, but
it has my old problem: the extended partition is not recognized (DOS fdisk
shows type UNKNOWN instead of FAT32). This, remember, even though I've
changed the motherboard with a completely different product.

********

CASE 2:

        root (hd0,0)
        chainloader +1

OUTCOME: boots the 1st hard disk, 1st partition, which is my /boot and has
some leftover LILO on its boot sector.

********

CASE 3:

        root (hd1,0)
        makeactive
        chainloader +1
or
        root (hd1,0)
        makeactive
        chainloader (hd1,0)+1

OUTCOME: these ones don't use map and they really produce a freeze.

********

I also tried booting from a floppy, as suggested. When the Window disk is
slave, same outcome as above. When it is master it boots immediately (no
delay) and D: is recognized properly.

-- 
GZ