Technology, Support, and News Forum

[jbullard]

I should say, though, the above method assumes you've installed Linux after Windows, opted not to install LILO on the MBR and that the Linux install is on the same drive as the Windows install.

I tried to use it to boot an Ubuntu install on a seperate drive using the Windows Boot-Loader and Ubuntu stalled waiting for boot device.

Thanks for the info.

Sounds like a PITA.

Jason

[Spacebunny Profile]

I should say, though, the above method assumes you've installed Linux after Windows, opted not to install LILO on the MBR and that the Linux install is on the same drive as the Windows install.

I tried to use it to boot an Ubuntu install on a seperate drive using the Windows Boot-Loader and Ubuntu stalled waiting for boot device.

huh...

1)If you installed linux first then say vista, you can boot linux using its install disk or rescue floppy
Then use the ''dd'' command and use ''yast'' to set ''Grub'' to install on the linux partition
You can also install ''Grub'' to the MBR, then you get the options --> bios --> Grub --> vista loader
''It doesn't seem to overwrite the Vista's osloader'' --But maybe I'am just lucky ?--

2)As stated above windows has it own partition, same goes for Linux (Reiserfs)
''there are Not installed on the same partition''

Got Suse working on my own machine and Linux Mandriva 2006 on friends pc

However there is a small problem,
After getting linux to work, I wanted to backup the settings using ''VistaBootPRO 2.1''
then try to get win2000 to work

But ''VistaBootPRO 2.1'' gives the following error at startup :
Index and count must refer to a location within the string.
Parameter name: count

[Absolute-Zero Profile]

1)If you installed linux first then say vista, you can boot linux using its install disk or rescue floppy
Then use the ''dd'' command and use ''yast'' to set ''Grub'' to install on the linux partition
You can also install ''Grub'' to the MBR, then you get the options --> bios --> Grub --> vista loader
''It doesn't seem to overwrite the Vista's osloader'' --But maybe I'am just lucky ?--

Yeah, I should have said "assumes you can still access your Linux install" rather than "assumes you've installed Linux after Windows". Lilo & Grub will pick up the Windows Bootloader but if you don't want to have two or three bootloaders (Linux, Vista, Ntldr) then you don't want to install your *nix loader onto the MBR.

2)As stated above windows has it own partition, same goes for Linux (Reiserfs)
''there are Not installed on the same partition''

I wasn't suggesting that they need to be in the same partition, just on the same drive. My install of Ubuntu won't boot using the 'dd' method, regardless of how I do it, I either have to use a boot floppy or the BIOS boot menu to select the drive with Linux installed. I'm guessing this is because it's on a seperate drive and the 'pointer' for the root file system isn't valid when trying to boot from the Windows System drive.

[Spacebunny Profile]

hmm..
Have you tried part 8 from the second manual

How to peel of the Lnx file from your linux rescue floppy

[Spacebunny Profile]

Ooooh righty then !!!!

All the problem are solved, all OSes are booting

Windows 2000 :
Windows Boot Loader
-------------------
identifier {40a12fe2-315e-11db-86ef-0020ed35b919}
device partition=D:
path \ntldr
description Microsoft Windows 2000
osdevice partition=D:
systemroot \WINNT

Windows XP
Windows Boot Loader
-------------------
identifier {40a12fe1-315e-11db-86ef-0020ed35b919}
device partition=E:
path \WINDOWS\system32\winload.exe
description Microsoft Windows MediaCenter NL
osdevice partition=E:
systemroot \WINDOWS

Vista :
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Vista Ultimate 2007
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {50c73d50-e6b3-11da-bc73-d30cdb1ce216}
nx OptIn

Suse Linux :
Windows Legacy OS Loader
------------------------
identifier {40a12fe6-315e-11db-86ef-0020ed35b919}
device boot
path \bootsect2.lnx
description SuSe Linux

Mandriva on second HD :
Windows Legacy OS Loader
------------------------
identifier {40a12feb-315e-11db-86ef-0020ed35b919}
device boot
path \bootsect.lnx
description Mandriva Linux

After this configuration,
I got a error missing NTLDR When trying to boot win2000
I copyed
NTLDR
AUTOEXEC.BAT
NTDETECT.COM
boot.ini
IO.SYS
MSDOS.SYS
from c: to the windows 2000 partition
next :
I got a black screen when trying to boot windows 2000
then I remebert that NTLDR was newer then then rest of the files
Copyed a older version of NTLDR to windows 2000 partition
Thats it... the old bootmanger is back ( the one that uses boot.ini )

So final result:
Bios --> Vista Osloader -- suse or mandriva or winxp or vista or ''win2000'' -->Winxp/win2000 Bootloader--> windows 2000

[gries818]

Good to hear! cheers!