To create multiboot dvd with XP and Vista,

first we have to add XP to bcd store of Vista DVD's bcd

copy vista dvd to folder say d:\vista-l

Copy XP CD to the same folder (i386,WINIP etc should be in the root of the disc along with sources, boot etc)

open cmd and type
(get bcdedit.exe from Vista DVD's boot folder)



okay, now the boot store is ready.

Now create the DVD image as usual using cd image



Similarly any NT based os (atleast XP, 2003) can be booted using bootmgr

Even More!!!

u can use boomgr without vista source
ie, it can be used for creating multiboot dvd of XP, 2003 etc
only u need the "boot" folder and "bootmgr" at root of DVD/CD

Testing :
I did it with vLited Vista and nLied XP Pro

UPDATE:

1. Delay in XP setup due to UDF filesystem
It is been reported that -u1 switch for cdimage causing delay in XP setup.
Possible reason 4 this will be due to XP setup reluctantancy to load files from mirror
UDF filesystem than joliet (-j1) file system.

AFAIK joliet filesystem max. single file size is 2GB
if u r install.wim is < 2GB then no problem occurs on avoiding -u1
otherwise u need u include -u1.

2. multibooting vista/server 2k8
Since the path (and name) of install.wim is hardcoded to <DVD_ROOT>\Sources\install.wim
it is impossile to install them along in same dvd using bootmgr.
If anybody know workarounds please post it.

Suggested solution is to merge the install.wim's
Thus making single install.wim with versions of Vista and Server 2k8 (like merging Vista x86 & x64 into one wim)
and selecting required version from unattened.xml


3. To remove ems support (the vista entry shows Windows Vista Setup [EMS Enabled])

I tried running your code all went well except for the last two lines of code the errors are listed below along with the code I ran

c:\EasyBoot\Disc1>bcdedit /store C:\EasyBoot\disc1\bcd /displayorder {NTLDR} /addlast
An error has occurred setting the element data.The system cannot find the file specified.

c:\EasyBoot\Disc1>bcdedit /store C:\EasyBoot\disc1\bcd /set {bootmgr} displaybootmenu yes
An error occurred while attempting to reference the specified entry.The system cannot find the file specified.

Am i missing something here ??

Thnx in advance

Using this same method, could you give directions for creating a multiboot CD with WinPE 2.0 and Windows XP? Even better, could you explain how to install WinPE 2.0 on the hard drive? Thanks so much in advance!

Here is a link to microsoft website that will help u out
Install WinPE onto HDD

try "-store" instead of "/store"

The command require Admin Privilages bcoz it uses HKLM registry hive

so in XP u require Admin account
& in Vista aministrator Privilaged Command Window

Thanks for the great tip, I got this to work very well for multi-booting Windows PE 2.0 (the new Vista based version) and several editions of Windows 2003 on a single DVD. However I cannot get the resulting ISO to boot once I add a second instance of Windows PE to the bcd store, has anyone tried doing this and gotten it working?

Here are the docs I worked from:
Boot Configuration Data Editor Frequently Asked Questions
http://technet.microsoft.com/en-us/windows...a/aa905126.aspx

Here is what I did:
Started with Windows PE 2.0 files from WAIK (x86).
[Root]
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {bootmgr} displaybootmenu yes
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {default} DESCRIPTION "Windows PE 2.0"
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {default} EMS no
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /deletevalue {bootmgr} TIMEOUT

[Boot Option #1]
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /create /application OSLOADER /d "Windows Server 2003 R2 - Standard Edition - Automated Install"
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {2770bd0a-4174-11dc-97f6-005056b27ab4} device boot
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {2770bd0a-4174-11dc-97f6-005056b27ab4} path \STDO\SETUPLDR.BIN
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /displayorder {2770bd0a-4174-11dc-97f6-005056b27ab4} /addlast
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {2770bd0a-4174-11dc-97f6-005056b27ab4} DESCRIPTION "Windows 2003 R2 - Standard Edition - Automated Install"

[Boot Option #2]
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /create /application OSLOADER /d "Windows Server 2003 R2 - Standard Edition - Manual install"
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {3963abdf-4174-11dc-97f6-005056b27ab4} device boot
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {3963abdf-4174-11dc-97f6-005056b27ab4} path \STDM\SETUPLDR.BIN
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /displayorder {3963abdf-4174-11dc-97f6-005056b27ab4} /addlast
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {3963abdf-4174-11dc-97f6-005056b27ab4} DESCRIPTION "Windows 2003 R2 - Standard Edition - Manual install"

[Boot Option #3]
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /create /application OSLOADER /d "Windows Server 2003 R2 - Standard Edition EVAL License - Automated Install"
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {4828a50f-4174-11dc-97f6-005056b27ab4} device boot
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {4828a50f-4174-11dc-97f6-005056b27ab4} path \STDE\SETUPLDR.BIN
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /displayorder {4828a50f-4174-11dc-97f6-005056b27ab4} /addlast
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {4828a50f-4174-11dc-97f6-005056b27ab4} DESCRIPTION "Windows 2003 R2 - Standard Ed. EVAL License - Automated Install"

This config boots up to here.

[Add second instance of Windows PE to menu]
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /copy {default} /d "System Quick Restore (Windows PE)"
This config boots up to here too.

D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {4d28b85c-4183-11dc-97f6-005056b27ab4} device ramdisk=[boot]\sources\restore.wim,{4d28b85c-4183-11dc-97f6-005056b27ab4}
D:\multiboot\boot\bcdedit /store D:\multiboot\boot\bcd /set {4d28b85c-4183-11dc-97f6-005056b27ab4} osdevice ramdisk=[boot]\sources\restore.wim,{4d28b85c-4183-11dc-97f6-005056b27ab4}
Editing these two lines causes the ISO to no longer boot.
Any ideas?

Is this approach also works for creating Multibootable DVD of Windows vista alongwith Windows server 2008 code name Longhorn?

Waiting for answer..........

Cool Stuff Guyz.

I did mine a month ago, but differently.

using vista's boot sector and easyboot's xp boot sector, I even managed (with some research) a GuiRunOnce in the vista unattended file. Only downfall is that Windows post installer is not vista compatible so I had to use windows commandscript instead. It Sucks.

Also using my oem license i got it to activate by itself.

Unfortunately I wont be uploading the iso due to the fact that my oem key is an original.

But I'm willing to help you create your own via this forum

:thumbsup

Hi friends,
I have tried the same approach for making bootable DVD of Windows Vista and Windows Server 2008 code name Longhorn.

I have taken Longhorn Installation Image in "Root" folder and created a folder named "Vista" in it and copied Vista Installation Image into that folder.

I have edited the bcd file of longhorn and given path of vista bootmgr into it.(i.e. \Vista\bootmgr ).

The DVD booted fine and shown two options

Windows Setup
Windows Vista

When I selected "Windows Setup", it successfully started longhorn installation.
But when I selected "Windows Vista" it again shown the previous window. I tried again and again it shown the same window. It is an Infinite Loop.

I guess, when I selected "Windows Vista" the bootmgr of Vista is loaded but it is using the same bcd file of Longhorn and showing the same options again.

If my guess is right, Can u tell me, How can I modify bootmgr so that it can read \Vista\boot\bcd file instead of \boot\bcd?

Thanks in advance.........

bootmgr is the "bootloader" not the Boot Configuration Data (aka BCD)

the dvd bootsector ( etfsboot.com ) always loads the bootmgr from ROOT of the DVD
this bootmgr checks for the boot configuration data in <DVD_ROOT>\Boot\bcd file
(This is same as what u seen in HDD install too The bootmgr in C: drive loads only C:\Boot\bcd)

So you have to edit the <DVD_ROOT>\Boot\bcd store in order to load any other

u did wat is to instruct <DVD_ROOT>\bootmgr to load <DVD_ROOT>\Vista\bootmgr --> Okay this is working

but then <DVD_ROOT>\Vista\bootmgr searches <DVD_ROOT>\Boot\bcd and loads the file

Thus it goes in a loop.

Okay to solve the issue

first understand how <DVD_ROOT>\Vista\Boot\bcd loads the OS ( bcdedit /store <DVD_ROOT>\Vista\Boot\bcd /enum /v )

then copy the same conf to <DVD_ROOT>\Boot\bcd by creating ne entry in the store

u should change the bcd parameters like
osdevice which by default will be ramdisk=[boot]\boot.wim,{GUID}
to ramdisk=[boot]\<properpath>\boot.wim,{GUID}

I figured out how to get multiple Win PE 2.0 WIMs in the menu with help from the posting here:
http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/27/Default.aspx

This is what I ended up with:



Now everything works nicely.

Hi Ausmith1,

Can u be more specific and tell me the solution for making Windows Vista and Windows Server 2008 Codename Longhorn in a single bootable DVD?

I am sorry, but I don't understood what u want to say?

Can u be more specific...........

u have to create the boot configuration data for loading Vista's WIM
int \boot\bcd

ie the "Windows Vista" should have a proper defnition in the bcd like "Windows Setup" no just loading the \Vista\bootmgr

try to copy the settings of "Windows Setup" and change the paths of osdevice and device options

Thats gr8.......

thank u very much........

Vista is booted properly but still have a problem.......

After I clicked on Install Now, a message box came telling

"A reqiured CD/DVD drive device driver is missing. If you have a driver floppy disk, CD, DVD or USB flash drive,
Please insert it Now."

Can you tell me why this message came and how I can solve it?

bocoz the install.wim is now in \Vista\sources dir

which is supposed to be in \sources dir

i dunno how to change the path of install.wim in the setup.

bocoz the install.wim is now in \Vista\sources dir
which is supposed to be in \sources dir

Can anybody tell me how do i cahnge the path of sources\install.wim to Vista\sources\install.wim?

any suggestion is appreciated........

So...if you want to have, say, Vista and VistaPE bootable, you can load them both from bootmgr, but if say you wanted Linux as well, you'd have to have 2 separate loaders?

Wrayal

I have Vista x64 & XP x64 booting fine using this method. Is it possible for me to add a third entry for XP 32bit? I try to use bcdedit /store Y:\USB_AIO\boot\bcd /create {name} /d "Windows XP Install" and it tells me the indentifier is invalid. When I put {ntldr} it just tells me that the entry already exists.

1. The problem due cozing Invalid store will be the HKLM registry key access
u need admin access to get write on HKLM key
bcdedit uses this ket to mount the store

2. first start with a clean bcd store
add entries one by one
{ntldr} is an alias for actual GUID 466f5a88-0af2-4f76-9038-095b170dc21c
so it cannot be recreated
instead of "/create" use "/copy" and alter that entries parameter to u requirment

Thanks that worked out fine. I have an entry for XP x86 on there now, the only problem is when I actually try to install it. I created a folder called BALLS and copied the x86 nlited (even tried un-nlited) disc to this folder. When I start the install I get a message about the txtsetup.sif missing or being corrupt. I have the bcd path set to \BALLS\I386\SETUPLDR.BIN. I thought it might be failing because the entries inside of txtsetup.sif had entries like "\I386" and I changed them all to \BALLS\I386 and so on for any directory entries it had, but I still got the same message. If anyone knows what's going on I could sure use the help.

Thats' a silly multiboot mistake
Consider Reading the Multiboot forum, guides much deeper

U dont need to change all the entries,
instead
find [SetupData] section of txtsetup.sif

and

SetupSourcePath = "\"


and replace with

SetupSourcePath = "\BALLS\"

I actually tried that earlier this morning after reading a guide about this and it didn't work. Thanks for trying to help though I really appreciate it. I still haven't read far enough into all the info or maybe I misunderstood something I did read so if there's anything else I can try I could use the help.

Is it possible to put in this :



So i never have to press F8 again during a Vista x64 setup with integrated drivers.

I mean edit the BCD that is on the DVD "DVD_ROOT\BOOT\BCD"

yes

first run through bcdedit /enum /v to get the GUID of the vista entry
then do bcdedit -store <store_name> /set {GUID} loadoptions DDISABLE_INTEGRITY_CHECKS

BUT it will apply only on the booting DVD, it wont be ther wen it is written to the HDD

afterall this affect only to the WinPE which is booting from the DVD

the vista u need to do that will booted only after first reboot of setup

am still unable to integrate this option in DVD
i tried to mount the install.wim
and by editing the bcd template in System32\config of the image

no use, its not working.

Does anybody know from wher the installer in WinPE phase copied a default set of bcd store to hdd?
or is it creating dynamically by the setup routine ??

Hi innocent devil, I've tried your guide, every entry is successfully added, I copied the folders, made the image with CDimage and burned it, the DVD boots, I get the two options(1-Windows Setup and 2-XP SP2 Pro Setup)

the thing is when I choose to install windows xp, The normal blueish screen of the textsetup mode insn't displayed, all I get is a blank black screen up until the time it says "searching for previous operating systems(or something like that)" why doesn't it show the whole txtsetup fase... because it kinda makes you think that the DVD isn't working(I actually resetted the machine twice before I decided to wait it out and see)...

other thing is, windows XP setup is taking way longer than usual after making the DVD image(from the usual 6-7 minutes to 30-35 minutes now)

My questions:
1-Isn't there a way to make the normal blue setup screen appear instead of the black blank screen being displayed for a while?
2-Is there something that I should modify in the CDimage options(switches) before I make it, in order to stop the sluguishness? maybe the UDF format or ISO format?
-----------------------------------------------------------------------
3-how can I change the "Windows setup(EMS enabled)" entry to something like "Windows Vista Ultimate Setup"?

anyhow, thanx for a quick, effortless guide to multiboot....

1) that seems unusual, i never been in such situaton, i usually get the press f6 to install 3party driver screen
(hint: it might due to the dvd filesystem)

2) better to put -j1 or -n(not verified)
but if u install.wim is >2gb no way to use -j1 (joliet restriction) else it better use j1 rather than u1

3) just disable ems support (go deep with bcdedit /v /enum to get is guid or try with bcdedit help)

( sorry i 4 got the details, & not able to check that as am not at home)

Hi, I managed to get it to display that screen and the Installation is no longer sluguish, all I did was to remove the "-u1" from ur example of CDimage(I'm using CDFS now, I hope this is not a problem for vista though)

as for question 3, I'll try that when I get home too, I hope u remember it soon though bcoz I think browsing the BCD we'll be like a fishing expedition for me, no certainty of success....

Peace....

ya, i think the XP setup is little bit hesitant to a mirror udf (-u1) filesystem, thats y u got that delay

Okay i managed to get acopy of bcdedit.exe

just running a bcdedit.exe /? gives


then running bcdedit.exe /bootems /?


So to turn off the [EMS Enabled] run

where BCD file is the BCD store that is to be put in the DVD

I actually hit a dead end yesterday when I tried it, so thanks 4 the help, Now if I disable the "EMS Enabled" what will show instead(Windows Vista Ultimate setup would be great) but anyways I'll see for myself at home, but just in case it just disables the EMS thing(what is anyways) and just leaves "Windows Setup" how can then rename it accordingly.

You've been very helpful, thanks again

to rename a bcd entry


here to chage the Name from Windows Vista to Windows Vista Ultimate
run

bcdedit -store <BCD-file> /set {GUID} description "Windows Vista Ultimate"

Dude, None of the examples are working(neither the one to disable EMS nor the one to rename)

Here's how I did it:

bcdedit -store c:\vista\boot\bcd /bootems {bootmgr} OFF
bcdedit /store c:\vista\boot\bcd /set {bootmgr} description "Windows Vista Ultimate Final Setup"

Dude Could u just Put an example u used for urself... I'm a newbie, so sometimes I might not know what to put in place of something like "<ur file here>" please use ur own paths and stuff with nothing that I might have to replace or figure out...

thanx anyways

THATS not possible

first u should do a bcdedit -store C:\vista\boot\bcd /v /enum

Then look fo an entry having description [i]"Windows Setup"[/b] copy down its GUID (say {my_guid})

after thta change the description
by


for the ems entry


if still u not getting the point, plz attach or send me the bcd file i wll do it

Hi, sory 4 d late reply, It's just that after replying to ur previous post I was kinda busy packing up tp move... I moved back to my original country, so I'm not staying In SA anymore(I've made the necessary adjustments to my info)... anyways I'm back online now and yeah 'll try this other code u gave me, but I don't think I used the "/v enum" before(so that must be why the prob arised)

will give u feedback

P.S: what OS do U recommend I use(XP or Vista) to change the BCD, I've been using vista though....

Peace

it doesnt matter , watever maybe that, it should run the bcdedit to edit bcd store,

Hi i've tried to create a multiboot dvd with this guide and all works perfectly
Do you think there's possibility to add a live cd created with bartpe using bcdedit....since i've no idea how to do this??

thanks

That i have to check, hasnt tried yet.

wen i reach hom on 15th , i'll check that.

Hey dude, Just wanted to let you know that it worked, sory 4 d late reply(the holidays)...

no probz, hope u enjoyed the holydays

Hey, devil, you wouldn't happen to know why I would be getting an NTDETECT failed message when I start my XP x64 install off of my USB flash drive, but not in VMware off of a .iso file would you? The files are exactly the same, just copied to the flash drive. Vista x64 is still loading fine off the USB drive so I'm not sure what is going on.

I used the bcd commands in this order:

bcdedit /store H:\boot\bcd /create {ntldr} /d "Windows XP x64 Install"
bcdedit /store H:\boot\bcd /set {ntldr} device boot
bcdedit /store H:\boot\bcd /set {ntldr} path \I386\SETUPLDR.BIN
bcdedit /store H:\boot\bcd /displayorder {ntldr} /addfirst
bcdedit /store H:\boot\bcd /set {bootmgr} displaybootmenu yes
bcdedit /store H:\boot\bcd /set {default} description "Windows Vista x64 Install"
bcdedit /store H:\boot\bcd /default {ntldr}

SETUPLDR is supposed to load from a CD/DVD not from removable (HD) medium as in the case of memory stick

when trying to load SETUPLDR from Stick, it finds that is being loaded from a HD and not optical medium tires to load OS (XP) not the setup thats why it fails.

There is a thread telling how to load an 5.x windows from usb
Here it is http://www.msfn.org/board/boot-install-USB...html&st=480

(bolding is mine)

I don't think that a \I386\ SETUPLDR will load x64 files?

The NEW link to the Install XP from USB is this one:
http://www.msfn.org/board/install-XP-USB-t111406.html
but it is \I386 related, not x64.

jaclaz

jaclaz:
but the SETUPLDR.BIN is in I386 dir of X64 cd not in AMD64 dir

so its not due to I386

its due to the loader recognizes what the source it is booting (CD or HD or removable hd or stick).

About 3 months ago I installed XP x64 off my flash drive using your method of multibooting the vista and xp installs and it worked just fine. I wonder what it is I did to get it work. It was heavily nlited as is my new XP x64 source so I don't know if I've changed anything my removals that could have gotten around this check.

then try gold xp x64 , so we can confirm whether it is caused by nlite or not

I meant it was nlited when it did work...
It's still nlited, but I don't recall which version I used when it worked as this was several months ago and I'm sure I've changed several removals since then.

Thansk for the script

for me it reports errors on the

Lines, i've modded them to :

I'm using a french bcdedit version

help me


Before I worked perfectly!

I would be getting an NTDETECT failed message when I start my XP PRO install off of my hard disk, but not in VMware off of a .iso file would you? I used the bcd commands in this order:

bcdedit /store H:\boot\bcd /create {ntldr} /d "Windows XP Professional"
bcdedit /store H:\boot\bcd /set {ntldr} device boot
bcdedit /store H:\boot\bcd /set {ntldr} path \I386\SETUPLDR.BIN
bcdedit /store H:\boot\bcd /displayorder {ntldr} /addfirst
bcdedit /store H:\boot\bcd /set {bootmgr} displaybootmenu yes
bcdedit /store H:\boot\bcd /set {default} description "Windows Vista"
bcdedit /store H:\boot\bcd /default {ntldr}


thank you

I have solved the problem, my mistake. Not necessary change things by UltraISO otherwise you lose the parameters of boot BCEdit.

Thank you