I built a dual-boot machine (w2k and rh 8.0) on a machine with a cdrom and
had no problems booting to either os.
I needed to move the drive to a machine without a cdrom, now I can boot to
the rh os, but not the w2k. Any ideas on how I can repair?
I have checked the list for similar problems
I have sent the query below twice and each time I get a reply from
bug-grub-bounces. Why?
I am using grub 0.90 which came with red hat linux and uses linux kernel
2.4.7-10. It has done everything I need so far loading Linux and Windows
from 2 disks.
However using PowerQuest
However using PowerQuest Partition Manager I created 2 extended partitions
on the second disk, Fat16 and Fat32, and copied partitions into them with
Norton Ghost. I can see these partitions under Windows and Linux
fdisk but I
can't get Grub to see them so that I can boot them. I address them
I needed to move the drive to a machine without a cdrom, now I
can boot to
the rh os, but not the w2k. Any ideas on how I can repair?
Perhaps the drive ordering is different now and you are using the same
device.map as the old machine? I assume GRUB is installed in your MBR. Can
you send the
And that's the reason i wanted a full functional bootfloppy first ;-)
Stages and menu so far work well. Great the commandline.
Now I've got my linux /boot on the second hd (ide1 primary) and tried two
titles: kernel on (hd0,1) and kernel on (fd0).
Grub also starts the kernel successfully.
can this be done in a way that makes the next update a 'just drop the
new drive in' way.
what I mean is something automated, or that just uses the code as is.
making updates much easier.
Just a thought.
On Tue, Mar 18, 2003 at 01:22:46PM -0600, Randy Couey wrote:
I am currently negotiating
Whether or not an update occurs, I would suggest that patches have a
place on the grub ftp site, as the official releases will always fall
behind the newest hardware. An unsupported patches directory, with a
use-at-your-own-risk policy, would be a useful source for adminstrators