below V
V
On 4/13/06, Jimmy Montague <rhetoric101@xxxxxxx> wrote:
Tim wrote:
> On Thu, 2006-04-13 at 08:41 -0500, Jimmy Montague wrote:
>
>> So my problem is that, having installed Core 5, I can't boot Core 5
>> because the boot loader seems to have installed itself on the Linux
>> drive INSTEAD of on the Windoze drive. That's to say that, whenever I
>> boot the system, the Windoze boot loader appears INSTEAD of the Grub
>> boot loader. My attempts to repair and/or reinstall Core 5 yield the
>> same result.
>>
>> Anyone got a solution?
>>
>
> Install GRUB to the right place...
>
> Well, that is what you need to do, and you can work out how to do this
> from the GRUB info file (the man file is quite abbreviated). If you
> can't follow it, and/or want more specific help, supply more information
> about how your drives are on your system. Post us the output from the
> following command, issued as the root user: fdisk -l
>
> (That's a letter l, not a number 1.)
>
>
Tim:
Read this post in a full-screen window.
My system has two 40g Maxtor ide drives. Both are on the primary strap.
One is jumpered Master; the other is Slave.
Windoze is on the Master drive. FC5 is installed on the Slave. Sorry: I
can't decipher the MAN page. I don't know how to copy bootloader to the
MBR of the Windoze drive..
When I ran fdisk -l, as you suggested, here is the result:
Disk/dev/hda: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track/ 4866 cylinders
units = cylinders of 16065 * 512 = 8225280 bytes
Disk/dev/hdb: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track/ 4866 cylinders
units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
dev/hda1 * 1 4865 39078081 7 HPFS/NTFS
dev/hdb1 * 1 13 104391 83
Linux
dev/hdb2 14 4866 38981722+ 8e Linux LVM
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Hi Jimmy & All:
Master (boot per above) Slave (not boot per above). Try strapping the linux drive as Master and the windows drive as Slave. Also go into CMOS (during the pre boot process) and check that the linux drive is to be booted from.
The linux drive should have an MBR from your load process that points to it's Grub loader and should be bootable. It simply lookes like the CMOS sees the windows drive as the one to boot from on that IDE strap.
Good Hunting!
Tod
