Mailinglist Archive: opensuse (3666 mails)

< Previous Next >
Re: [SLE] Suse 9.2 & MSDOS Drive
  • From: Anders Johansson <andjoh@xxxxxxxxxx>
  • Date: Fri, 4 Mar 2005 00:27:55 +0100
  • Message-id: <200503040027.55566.andjoh@xxxxxxxxxx>
On Friday 04 March 2005 00:05, Sunny wrote:
> On Thu, 03 Mar 2005 13:52:20 -0800, Art Fore <art.fore@xxxxxxxxxxx> 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

< Previous Next >
Follow Ups
References