My problem is that the only way I can get Windows to run is to plug it into the first slot, then Windows boots but I never see grub.
By first slot I guess you sata port? It's been a while since I've noticed Windows caring about device order. I have seen windows try to change its drive letter when it finds itself on a new drive port, but that was only under certain conditions.
When you move your windows drive to port 1, you don't see grub because grub is installed on the other drive. Unfortunately, I don't know anything about dual booting with grub, so maybe someone else here can tell you how...
I think if you were to place your windows drive in port 1, and then were to set up grub to run from the windows drive, it would solve the problem?
On 03/22/2011 04:19 PM, compdoc wrote:
My problem is that the only way I can get Windows to run is to plug it into the first slot, then Windows boots but I never see grub.
By first slot I guess you sata port? It's been a while since I've noticed Windows caring about device order. I have seen windows try to change its drive letter when it finds itself on a new drive port, but that was only under certain conditions.
When you move your windows drive to port 1, you don't see grub because grub is installed on the other drive. Unfortunately, I don't know anything about dual booting with grub, so maybe someone else here can tell you how...
I think if you were to place your windows drive in port 1, and then were to set up grub to run from the windows drive, it would solve the problem?
I am late to this thread, so it may already have been mentioned, but you may want to look at the map option in Grub.
rootnoverify (hd0,0) map (hd0) (hd1) map (hd1) (hd0) chainloader +1
Mikkel
On 27/03/11 18:32, Mikkel wrote:
On 03/22/2011 04:19 PM, compdoc wrote:
My problem is that the only way I can get Windows to run is to plug it into the first slot, then Windows boots but I never see grub.
By first slot I guess you sata port? It's been a while since I've noticed Windows caring about device order. I have seen windows try to change its drive letter when it finds itself on a new drive port, but that was only under certain conditions.
When you move your windows drive to port 1, you don't see grub because grub is installed on the other drive. Unfortunately, I don't know anything about dual booting with grub, so maybe someone else here can tell you how...
I think if you were to place your windows drive in port 1, and then were to set up grub to run from the windows drive, it would solve the problem?
I am late to this thread, so it may already have been mentioned, but you may want to look at the map option in Grub.
rootnoverify (hd0,0) map (hd0) (hd1) map (hd1) (hd0) chainloader +1
Mikkel
I managed to create a grub.conf that works [a minor miracle]. However I am interested in this.
I don't see the "map" option in man grub?
Info grub is hard to deal with, copied it to info.txt which produces 73 pages in an openoffice document using a font large enough that I can see ...
How do I use the "map" option?
Bob
On 3/28/11, Bob Goodwin bobgoodwin@wildblue.net wrote:
I managed to create a grub.conf that works [a minor miracle]. However I am interested in this. I don't see the "map" option in man grub? Info grub is hard to deal with, copied it to info.txt which produces 73 pages in an openoffice document using a font large enough that I can see ...
Using info from emacs (C-h i) is very convenient (unless, of course, that one finds emacs hard to deal with).
How do I use the "map" option?
Copied from the info file:
-- Command: map to_drive from_drive Map the drive FROM_DRIVE to the drive TO_DRIVE. This is necessary when you chain-load some operating systems, such as DOS, if such an OS resides at a non-first drive. Here is an example:
grub> map (hd0) (hd1) grub> map (hd1) (hd0)
The example exchanges the order between the first hard disk and the second hard disk. See also DOS/Windows.
HTH, Andras
On 28/03/11 06:41, Andras Simon wrote:
On 3/28/11, Bob Goodwinbobgoodwin@wildblue.net wrote:
I managed to create a grub.conf that works [a minor miracle]. However I am interested in this. I don't see the "map" option in man grub? Info grub is hard to deal with, copied it to info.txt which produces 73 pages in an openoffice document using a font large enough that I can see ...Using info from emacs (C-h i) is very convenient (unless, of course, that one finds emacs hard to deal with).
How do I use the "map" option?Copied from the info file:
-- Command: map to_drive from_drive Map the drive FROM_DRIVE to the drive TO_DRIVE. This is necessary when you chain-load some operating systems, such as DOS, if such an OS resides at a non-first drive. Here is an example:
grub> map (hd0) (hd1) grub> map (hd1) (hd0) The example exchanges the order between the first hard disk and the second hard disk. See also DOS/Windows.HTH, Andras
Thank you, I still hadn't found it. The explanation raises more questions. I know a few Emacs commands but not enough to use it effectively.
Tnx. Bob
On Mon, 28 Mar 2011 06:30:13 -0400 Bob Goodwin bobgoodwin@wildblue.net wrote:
On 27/03/11 18:32, Mikkel wrote:
On 03/22/2011 04:19 PM, compdoc wrote:
My problem is that the only way I can get Windows to run is to plug it into the first slot, then Windows boots but I never see grub.
By first slot I guess you sata port? It's been a while since I've noticed Windows caring about device order. I have seen windows try to change its drive letter when it finds itself on a new drive port, but that was only under certain conditions.
When you move your windows drive to port 1, you don't see grub because grub is installed on the other drive. Unfortunately, I don't know anything about dual booting with grub, so maybe someone else here can tell you how...
I think if you were to place your windows drive in port 1, and then were to set up grub to run from the windows drive, it would solve the problem?
I am late to this thread, so it may already have been mentioned, but you may want to look at the map option in Grub.
rootnoverify (hd0,0) map (hd0) (hd1) map (hd1) (hd0) chainloader +1
Mikkel
I managed to create a grub.conf that works [a minor miracle]. However I am interested in this. I don't see the "map" option in man grub? Info grub is hard to deal with, copied it to info.txt which produces 73 pages in an openoffice document using a font large enough that I can see ... How do I use the "map" option? Bob
Bob: Pretty much all about Grub: http://www.dedoimedo.com/computers/grub.html
A minor point: Fedora's configuration file for grub is grub.conf rather that menu.lst, menu.lst is a link to grub.conf.
Also, this document does *not* apply to Grub2, but since Fedora uses the old Grub 0.97 so you're good to go. For a while.
-- cmg
On 28/03/11 10:47, Carroll Grigsby wrote:
Bob: Pretty much all about Grub: http://www.dedoimedo.com/computers/grub.html
A minor point: Fedora's configuration file for grub is grub.conf rather that menu.lst, menu.lst is a link to grub.conf.
Also, this document does *not* apply to Grub2, but since Fedora uses the old Grub 0.97 so you're good to go. For a while.
-- cmg
Yes, an interesting article, answers a few questions I had.
They suggest "find" to see which drives contain what system. It doesn't provide anything useful here?
[bobg@box9 ~]$ find /boot/grub/stage1 /boot/grub/stage1
I expected to see some data listed as below? This computer has both F-14 and Windows.
"Example:
Let's say the computer has the following operating systems installed on different partitions:
* SUSE on (hd0,1) * Kubuntu on (hd0,2) * Mandriva on (hd0,4)
All these will be returned as potential roots for GRUB device (as each OS has its own files)."
I will save it. The examples are always good. I am forever looking for examples.
Thank you.
Bob
-
Andras Simon -
Bob Goodwin -
Carroll Grigsby -
compdoc -
Mikkel