I've done this on SATA and IDE drives and combos of the same and I never got XP to boot unless I used rootnoverify (hd0,0). Macro$haft insists on being first in my experience. FWIW.
Make a grub boot disk(if you haven't already) and practice until you find the proper sequence of commands; then you can put them into a conf file and do a grub-install. I'd do that first. A false move could wipe out your MBR. As I recall I completey destroyed the boot partition on a brand new HD while fumbling with GRUB. But it was still under warranty "Whew!" --- [EMAIL PROTECTED] wrote: > I just put in a SATA drive into an otherwise PATA > machine. I put Windows XP > on the new drive. I added the following to my > grub.conf: > > title=Windows XP > rootnoverify (hd2,0) > makeactive > chainloader +1 > > but when I tell grub to boot this item, I get an > otherwise blank screen with > the text: > > rootnoverify (hd2,0) > makeactive > chainloader +1 > > and nothing else happens. > > I have never had difficulty getting grub to play > with Windows in the past, but > that was always with PATA hardware. > > I have tried editing the grub configuration at boot > time to see if grub > doesn't like my drive number or something. I used > the TAB autocompletion > feature which lists three disks (hd0, hd1, and hd2). > The former two are > definitely my raid array based on the number of > partitions they contain. The > latter has only one partition (according to grub's > TAB autocompletion) which > is as it should be given that it is obviously the > Windows disk. > > I'm at a loss here. Any help would be greatly > appreciated. I'm afraid I have > to use my BIOS to switch boot disks until I resolve > this. > -- > gentoo-user@gentoo.org mailing list > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
