[Spacebunny]

Detail system :
Partition 1 : name boot - size 135 mb = boot files + resue files
Partition 2 : name win2000 - size 17 gb
Partition 3 : name WinXP - size 17 gb
Partition 4 : name Suse - size 17 gb
Partition 5 : name Vista - size 17 gb

Boot:
Bios - grub - Vista osloader - vista
- winxp

So far, Solved:
reinstalling grub
Just seeing 2 OSes with vista loader -> vista and older versions ( older versions blackscreen )
1) /windows/system32/config/system missing ( becose its winnt )
bootsect /nt60 all
2) /ntldr missing
moving the boot files to the new c:
3) /kdcom.dll missing
copying the missing file to the OSes system32 dir

Now I got winxp running..

But windows 2000 I get
Bsod : Kmode_Exception_not_handled

ps
copying say bootsector.exe to vista's windows dir
Well Its gone on next reboot...

Any solution on how to boot a windows 2000 ?

[Spacebunny]

Hmm...

A tip :
Don't use the option uninstall vista's OSloader under VistaBootPRO 2.1
( in hope to get the winxp version back )

Lol
You will get :
I got a blinking cursor on left upper corner and endless bieping noise
( on the next reboot... with no options to boot anything )

but I solved the problem now, using the resue option on the vista install disk

I'am thinking that the windows 2000 problem is greated by kdcom.dll
but I will try again tomorrow....

[jbullard]

Spacebunny,

Thank you for your synopsis. Come to think of it, we did not even think about individuals running earlier versions of Windows (before XP). This is something that we will take a look at during the next build.

Try this to boot to Win 2000

1. bcdedit /create {legacy} /d "Windows 2000"

2. bcdedit /displayorder "Windows 2000" /addlast

Before Proceeding
- use bcdedit /enum and retrieve the GUID for your new Windows 2000 entry.

3. bcdedit /set GUID osdevice partition = YOUR_DRIVE_HERE

4. bcdedit /set GUID device partition = YOUR_DRIVE_HERE

5. bcdedit /set GUID path "\ntldr"

6. bcdedit/set GUID systemroot "\winnt"

If the above does not work, try to change the first step to this

bcdedit /copy {ntldr} /d "Windows 2000"

and then proceed with the rest of the steps.

Format for YOUR_DRIVE_HERE is C:
Replace GUID with the actual GUID retrieved

Also, as far as Linux is concerned, VistaBootPRO has no control over that. Currently it does not manage *Nix boot entries.

Let us know if that does not work.

Jason

[kd1966]

Thanks Jason! I might try that on one of my systems here at the house........ the "System/Boot" drive is Win2K on C:........... but I'm waiting for a 2nd HDD to add Vista, as I just got the Vista compatible vid card

EDIT: And it dual boots with XP

[Spacebunny]

hmm..
I only get syntax errors or The specified entry already exists.

1)I used VistaBootPRO 2.1 to make a backup
2)Then I removed win2000 using VistaBootPRO 2.1
here is the old code :
identifier {40a12fe4-315e-11db-86ef-0020ed35b919}
device partition=D:
path \WINNT\system32\winload.exe
description Microsoft Windows 2000 Eng
osdevice partition=D:
systemroot \WINNT

Then tried the commands

[jbullard]

Make sure that after you add the entry you run bcdedit /enum in order to retrieve the new GUID string.

Jason

[Spacebunny]

I gave up on the given commands and set the backup back

But....
I finaly got Vista's OSloader to boot Linux
Using the manual on this site :
http://computerbits.wordpress.com/tag/macbook/

I allready had bootsect.lnx file
for those not, read here to make one :
http://www.pmg.lcs.mit.edu/~chandra/ins ... lboot.html

here is my bcedit entry :
Windows Legacy OS Loader
------------------------
identifier {40a12fe6-315e-11db-86ef-0020ed35b919}
device boot
path \bootsect.lnx
description Suse Linux

[jbullard]

I gave up on the given commands and set the backup back

But....
I finaly got Vista's OSloader to boot Linux
Using the manual on this site :
http://computerbits.wordpress.com/tag/macbook/

I allready had bootsect.lnx file
for those not, read here to make one :
http://www.pmg.lcs.mit.edu/~chandra/ins ... lboot.html

here is my bcedit entry :
Windows Legacy OS Loader
------------------------
identifier {40a12fe6-315e-11db-86ef-0020ed35b919}
device boot
path \bootsect.lnx
description Suse Linux

What is the actual boot file for Linux. This may prove useful.

Jason

[Absolute-Zero]

Jason,

You normally have to create the boot file from within linux by copying the /boot partition and it's contents to a file using the dd command...

# dd if=/dev/? of=/bootsect.lnx bs=512 count=1

... where /dev/? is the location of the drive the Linux boot partition/folder is on.

You then copy this file to floppy, put it in the Windows boot partition and add a pointer to it to the Windows boot menu controller, like boot.ini...

C:\BOOTSECT.LNX="Linux"

[Absolute-Zero]

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.