We have Suse 9.2 installed on dual bood amd64 system. This has a SATA drive, /dev/sda. A few days after installation, we added a second drive, and IDE drive, dev/hdd. Suse recognized the drive, I mapped it to /windows/DOS. This all works fine. The only guy here who wants to use dos wants to be able to boot dos from the second drive without going into the BIOS and setting the boot order. I have modified the GRUB list etc via YAST and added the following. Disk order /dev/sda, /dev/hdd title MSDOS 6.22 map (hd0) (hd1) map (hd1) (hd0) makeactive rootnoverify (hd1,0) chainloader +1 When you boot from grub and select MSDOS, you get a flash, then back to grub. It is too fast to read what is on the screen. I changed the listing to title MSDOS 6.22 unhide (hd1,0) hide (hd0,0) makeactive rootnoverify (hd1,0) chainloader +1 When I boot and select MSDOS, I know get an error 12: invalid device. Would appreciate any help or a link to where I could get more info on this. Art
On Thu, 03 Mar 2005 13:52:20 -0800, Art Fore <art.fore@comcast.net> wrote:
We have Suse 9.2 installed on dual bood amd64 system. This has a SATA drive, /dev/sda. A few days after installation, we added a second drive, and IDE drive, dev/hdd. Suse recognized the drive, I mapped it to /windows/DOS. This all works fine.
The only guy here who wants to use dos wants to be able to boot dos from the second drive without going into the BIOS and setting the boot order. I have modified the GRUB list etc via YAST and added the following.
Disk order /dev/sda, /dev/hdd
title MSDOS 6.22 map (hd0) (hd1) map (hd1) (hd0) makeactive rootnoverify (hd1,0) chainloader +1
When you boot from grub and select MSDOS, you get a flash, then back to grub. It is too fast to read what is on the screen.
In all the examples and configurations I have seen so far (yes, they are for windows), makeactive is the last option, after the chainloader +1. It may not be the solution, but you may give it a try.
Art
Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
On Friday 04 March 2005 00:05, Sunny wrote:
On Thu, 03 Mar 2005 13:52:20 -0800, Art Fore <art.fore@comcast.net> wrote:
We have Suse 9.2 installed on dual bood amd64 system. This has a SATA drive, /dev/sda. A few days after installation, we added a second drive, and IDE drive, dev/hdd. Suse recognized the drive, I mapped it to /windows/DOS. This all works fine.
The only guy here who wants to use dos wants to be able to boot dos from the second drive without going into the BIOS and setting the boot order. I have modified the GRUB list etc via YAST and added the following.
Disk order /dev/sda, /dev/hdd
title MSDOS 6.22 map (hd0) (hd1) map (hd1) (hd0) makeactive rootnoverify (hd1,0) chainloader +1
When you boot from grub and select MSDOS, you get a flash, then back to grub. It is too fast to read what is on the screen.
In all the examples and configurations I have seen so far (yes, they are for windows), makeactive is the last option, after the chainloader +1.
It may not be the solution, but you may give it a try.
I suspect the problem is that makeactive is before rootnoverify. I don't think it matters that it's before chainloader, but if it's before the root instruction, it will likely make the wrong partition active
Moving the makeactive after the rootnoverify (hd1,0) did the trick and I am using the map function instead of the hide/unhide. Turns out that windows would not boot after the hide/unhide before I made the makeactive change. The MSDOS portion of the grub comfig now looks like map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd1,0) makeactive chainloader +1 I had copied the previous from a web page, but guess it was wrong where the makeactive was before the rootnoverify. Anyhow, thanks for the info. Art Anders Johansson wrote:
On Friday 04 March 2005 00:05, Sunny wrote:
On Thu, 03 Mar 2005 13:52:20 -0800, Art Fore <art.fore@comcast.net> wrote:
We have Suse 9.2 installed on dual bood amd64 system. This has a SATA drive, /dev/sda. A few days after installation, we added a second drive, and IDE drive, dev/hdd. Suse recognized the drive, I mapped it to /windows/DOS. This all works fine.
The only guy here who wants to use dos wants to be able to boot dos from the second drive without going into the BIOS and setting the boot order. I have modified the GRUB list etc via YAST and added the following.
Disk order /dev/sda, /dev/hdd
title MSDOS 6.22 map (hd0) (hd1) map (hd1) (hd0) makeactive rootnoverify (hd1,0) chainloader +1
When you boot from grub and select MSDOS, you get a flash, then back to grub. It is too fast to read what is on the screen.
In all the examples and configurations I have seen so far (yes, they are for windows), makeactive is the last option, after the chainloader +1.
It may not be the solution, but you may give it a try.
I suspect the problem is that makeactive is before rootnoverify. I don't think it matters that it's before chainloader, but if it's before the root instruction, it will likely make the wrong partition active
participants (3)
-
Anders Johansson -
Art Fore -
Sunny