Forum: EasyBoot
Topic: EasyBoot All-In-One How to
started by: MrChris
Posted by MrChris on Nov. 24 2004,14:28
Where can I get a how-to doc on creating WinXP/Win2K/98.ect... All ine Ones using EasyBoot 5.05?

Regards,

MrChris
Posted by Incroyable HULK on Nov. 24 2004,16:53
Take a look at the help file included in the software  :p
Posted by pchaxor on Jan. 08 2005,10:59
Oh yeah, because the help files are so great and anyone can understand them. HAHAHA!

Thank God there is a forum or this app would be worhless.
Honestly the documentation is something to be desired.

But for $30 .. what do you expect right?
Posted by Incroyable HULK on Jan. 08 2005,18:08
You can take a look at this guide:

< http://flyakite.msfnhosting.com/ >

This is how I got my whole thing working up. It is written with CDSHELL in mind but the concept is the same with EasyBoot (if you read the documentation).
Posted by Hannes on Jan. 12 2005,20:50
Here are my personal notes on how to do this. Please note that bits and pieces of this are pasted from docs others have written. I have not specifically credited them in these docs because this was originally just intended as notes to myself to help me remember if I came back to this after a long period of time. Some of the notes have some rough edges so feel free to ask if you have any questions or something is not clear. At the very least this may supplement other docs you have.

Hannes


Configuring Multiple Operating Systems With EasyBoot

This procedure assumes that you are working with Windows XP. The same procedure will work for Windows 2000 and Server 2003. Just modify the directory names you use to suit your needs with each OS.

1) Under “c:\EasyBoot\disk1” create a subdirectory called “WXP1”

Note: You can use any valid 4 character directory name here, however you should make certain to use all caps. Substitute whatever you use for “WXP1” in all the references below.

2) Copy the contents of your Windows XP CD to the “WXP1” directory. You can delete extra folders such as the Support directory later if you wish, but you should copy the entire CD contents over for now, especially if you want to slipstream in a Service Pack (See “Optional Steps to Slipstream in SP1” below).

Optional Steps to Slipstream in a Service Pack

If your installation files do not already have the latest Service Pack slipstreamed in then you can slipstream in the Service Pack now. This example shows how to slipstream SP1a into Windows XP. The same procedure works for Windows 2000. Of course, you simply need to modify the directory names below and the name of the Service Pack file.

A) Copy the contents of the Windows XP CD to a directory on a HD. In this example, we’ll assume C:\XP
B) Download the FULL Service Pack package (not the minimal install package).
C) Make a directory on you HD to extract the Service Pack files to, for example, C:\SP1a.
D) Open a command prompt and change to the directory where the SP is located. Issue the command “xpsp1a_en_x86.exe –x”. When asked where to extract the files to, point to the directory you just created (C:\SP1a in the example above).
E) Change to the directory where the SP files were just extracted to and go to the update directory.
F) Issue the command “update /s:c:\xp”

You have now slipstreamed the Service Pack into your installation files.

If you now want to create a bootable CD with the slipstreamed Service Pack do the following:

A) Extract the boot sector from your original Windows CD using a utility such as Ultra ISO.
B) Open a CD Burning application such as Nero or Easy CD Creator. Choose to create a bootable CD. You should set the emulation type to “No Emulation” and load 4 sectors.
C) If using Nero Burning ROM be sure to check the box that reads:

Do not add the “;1” ISO file version extension.
Note: Current  versions of Easy CD Creator don’t have this option  but seem to work properly by default.

D) Use the Joliet file system, allow paths more than 8 levels deep, and allow more than 255 characters in the path. Set the volume label to be the same as the original CD.

End of Optional Steps to Slipstream the Service Pack

3) Copy the files from the root of your Windows XP CD to the “c:\EasyBoot\Disk1” directory. For Windows 2000 this includes all files whose names start with “cdrom”. For Windows XP and Server 2003 copy all files starting with “win51”. This includes the files such as “WIN51”, “WIN51IP”, etc.

4) Use a tool such as UltaISO to save the bootsector from your CD to the “c:\Easyboot\Disk1\ezboot” directory. As an alternative you can use download a bootsector file. Rename as you see fit. For example, if you plan to have two copies of Windows XP, such as a retail version and a Volume License edition you can call one bootsector file “WXP1.bin” and one “WXP2.bin”. Use the search and replace text tool built into EasyBoot to change all occurrences of “I386” to “WXP1” in this file (remember to use all caps). The name of the bin file is not what matters here. What matters is that I386 is modified to match the name of the directory that your installation files are in.

5) The goal of this step is to simply copy the boot files needed to install Windows from the “i386 directory to the “WXP1” directory (or whatever directory you are using). There are two methods you can use here. The first method is far simpler to perform and involves using a simple batch file to copy files over from the i386 directory. The second method is good if you want to be 100% certain that you are copying the correct files over. This might be useful if a new Service Pack is released or you have a special version of Windows such as an OEM version that has additional files that the batch file does not account for. The bottom line is that Method 1 should work fine but Method 2 is a sure bet.

Method 1
=======
Copy the boot files from the “i386” directory to the “WXP1” directory. To do this, use the appropriate batch file available in the resources directory of your EasyBoot installation. There is a batch file for Windows XP Pro, one for all versions of Win2000, and one for all versions of Server 2003. Place the batch file for Windows XP in the “WXP1” directory and then run it by double-clicking it. After it has run you can delete it if you wish.

Method 2 for Windows XP or Server 2003
==============================
Thanks to the MSFN forums for this information:

Make a backup copy of the c:\boot.ini file. This procedure will cause this file to be modified so you will want to be able to change it back after that happens.

Go to Start -> Run and type or paste the following command:

<path to i386 directory for XP or Server 2003>\winnt32.exe /noreboot

Example: c:\Easyboot\disk1\WXP1\i386\winnt32.exe /noreboot

Windows XP setup should come up. Choose "New Installation" and go through the options as usual. Do NOT download updated setup files. At the "Setup Options" screen, click on "Advanced Options" and make sure "copy all installation files from the CD" is checked. If it is grayed out don't worry about it.
Setup should create 2 folders in the root of your main drive. They will be hidden so make sure "Show hidden files and folders" is enabled.
$WIN_NT$.~BT - the boot folder$WIN_NT$.~LS - installation files folder
Copy the contents of $WIN_NT$.~BT to “WXP1”.

Now in the “WXP1” folder delete the following files:
BOOTSECT.DAT
migrate.inf
winnt.sif

IMPORTANT: Now there's just one last thing we have to do. When we ran setup like we just did, it expects us to be installing a new operating system the next time we reboot, so setup adds an extra boot option in the boot.ini file and changes the default boot choice to it. Delete the boot.ini file and rename the copy you made earlier to boot.ini.

Method 2 for Windows 2000
=========================

The method described above for Windows XP and Windows Server 2003 will not work for Windows 2000 if you are running on a Windows XP based OS.


Install an ISO image of 2000 Professional in VMware. Copy the contents of the ISO into a folder on the virtual installation's desktop, and slipstream in SP4 if not already done. Run winnt32.exe from the i386 folder. Windows 2000 setup should come up. Choose "New Installation" and go through the options as usual. Do NOT download updated setup files. At the "Setup Options" screen, click on "Advanced Options" and make sure "copy all installation files from the CD" is checked. If it is grayed out don't worry about it. When it's done do NOT let it reboot.

Setup should create 2 folders in the root of your main drive. They will be hidden so make sure "Show hidden files and folders" is enabled.
$WIN_NT$.~BT - the boot folder$WIN_NT$.~LS - installation files folder
Copy the contents of $WIN_NT$.~BT to “WXP1”.

Now in the “WXP1” folder delete the following files:
BOOTSECT.DAT
migrate.inf
winnt.sif

IMPORTANT: Now there's just one last thing we have to do. When we ran setup like we just did, it expects us to be installing a new operating system the next time we reboot, so setup adds an extra boot option in the boot.ini file and changes the default boot choice to it. Delete the boot.ini file and rename the copy you made earlier to boot.ini.

___


6) Edit the file “setupldr.bin” in the “WXP1” directory. Again, use the search and replace text tool built into EasyBoot. Change all references of “i386” to “WXP1”. Use all capital letters except for the “i” in “i386”.

7) Edit the file “txtsetup.sif” in the “WXP1” directory and change the value for “SetupSourcePath” from “\” to “\WXP1”. Note: You can use notepad to do this, however, it is very important to check the file after you save it to be sure that notepad has not appended a “.txt” extension to the end of it! I would suggest using Wordpad rather than Notepad.

8) When making your boot menu in EasyBoot use “run wxp1.bin” to run this installation of Windows  XP.

Note: When you install, at the time of the first reboot you should eject the CD or DVD and reinsert it only when Windows prompts for it again. I found that even though I set EasyBoot to boot from the HD when it timed out, for some reason Windows XP could not find files on the CD then.  If I boot directly to the HD then all works fine. At least, that’s what happened in my VMWare test &#61514;.

Creating an Unattended Setup Installation

Follow the instructions as above for setting up an OS in EasyBoot

Create a $OEM$ directory at the same level as the i386 directory. The directory structure should look like this:

I386
$OEM$
     $1
           Install
           Drivers
     $$
           System32
     $Docs
     $Progs

From the Windows Deployment tools copy “setupmgr.exe “ and “ref.chm” to a directory on the HD. Run “setupmgr.exe”. Use the following options:

New or Existing Answer File: Create New
Type of Setup: Unattended Setup
Windows Product: Windows XP Home / Professional
User Interaction: Fully Automated
Distribution Share: Set up from CD (ignore the message about IE customizations, they work actually!)

Having done that, accept the Licence Agreement, then fill in all the boxes as you would during Windows XP Setup. If you come across a section that you don't understand, then ignore it. Windows XP will use whatever default option there is for that section.
When you've finished, it creates a file called unattend.txt. Since we are going to run Setup from a CD we need to rename this to winnt.sif.

But to make this work, we need to specify two values in the winnt.sif file under [Unattended]:
[Unattended]
OemPreinstall=Yes
UnattendSwitch="yes"
OemPreinstall=Yes instructs Windows XP Setup that there is an $OEM$ distribution share on the CD. This will tell setup to copy them over to the destination hard drive of where Windows is being installed.
UnattendSwitch="yes" instructs Windows XP Setup to skip the "Welcome to Windows XP" screens, where user account and Internet setting-up takes place.

If you prefer to manually choose a partition during text-mode setup with full control on choice of filesystem, then make sure you have these lines set as they are under the [Data] and [Unattended] sections in winnt.sif:
[Data]
AutoPartition=0
[Unattended]
FileSystem=*

Normally you would add the winnt.sif to the i386 directory but when using EasyBoot you will want to add it to the directory that you copied the Windows files into and where the boot files have been copied. For example, if you copied your Windows XP CD contents to Disk1\WXP1 then you will want to put the winnt.sif in the WXP1 directory.

End of Unattended Setup Configuration


How to Integrate Acronis Products into EasyBoot

Notes for integrating Acronis TrueImage:
1) Use UltraISO to extract boot file of a bootable CD
  created by Acronis TrueImage, save it as trimg.bif in the disk1\ezboot directory
2) Use 'bootinfotable;run trimg.bif' as menu command to load it
3) For TrueImage, copy the remaining files from the root of the CD directly to the disk1 directory.


Adding Norton Ghost 9 to the Multiboot Disc

Copy all the files from the root of the CD to the EasyBoot\disk1 directory.

Make a 4 letter directory (I used GST9) just like you would for any copy of Windows XP, Server 2003, etc. Copy the entire i386 directory from the Ghost 9 CD over to this directory.

Modify the setupldr.bin and the txtsetup.sif just as for other Windows installations. Do the same for the boot sector.

If you want to get rid of the message asking you to press any key to boot from the CD delete the bootfix.bin file.
Posted by DEVIL on Jan. 14 2005,19:49
mY GOD HANNES, GREAT JOB THERE DUDE, BUT FOR THE SIMPLTONS LIKE ME, wELL i KINDA GOT LOST HALF WAY THROUGH, SEEMED LIKE i MADE FOUR CDS BY THE TIME i HAD READ IT ALL,
This is a compliment not a flame, Im just kinda thick I guess :-------)
Posted by Hannes on Jan. 15 2005,20:52
Thanks for the feedback. I guess I really should spend a little time rewritting this and clarifying each step. In fact, maybe I'll have time to do that this weekend.

In the meantime, if you have any questions regarding any specific parts, please feel free to let me know.

Hannes
Posted by Cpt. Canuck on Jan. 16 2005,01:27
Hannes....

I read your bit. Good stuff... Before I try some of it, let me know if I'm wasting my time.

What I am thinking of doing is creating a multiboot cd with the following options.

Option 1: WinXP fresh install (Slipstreamed with SP2)

Option 2: Ghost Image

What I'm thinking is creating a 2.88 boot image for option 2 so that EasyBoot will run this if selected by user. (The 2.88 boot image would be the 2 diskette set that ghost creates.) I would have the ghost image on a 2nd disk (DVD).

Recap: If opton one is chosen, EasyBoot would start a fresh install. If option 2 is selected, EasyBoot would launch ghost.exe and the user would then be able to point to the DVD drive that would contain the image and re-image the HDD.

Do you think it would work 'OR' do you know of a better way to get a bootable "DVD" that can also contain the ghost image that is over 3Gb?


Any input is appreciated by anyone.

Thanks.
Posted by Incroyable HULK on Jan. 16 2005,08:57
I think you are on the right track. Once your floppy image of Ghost program is loaded, you could switch for another CD/DVD which contains the ghost image.

You could also go for the DVD option and put your ghost image in the \disk1 folder so it would be accessible as the root of the current DVD.
Posted by Cpt. Canuck on Jan. 16 2005,10:30
Incroyable Hulk,

I would have to verify the size of the I386 with sp2 and my ghost image. I'm not sure how much extra overhead Easyboot adds to the disks but between the I386 and the ghost image there may not be enough room on 1 dvd. Otherwise that would be my best solution.

Thanks,

Cpt. Canuck
Posted by sakai on Jul. 16 2005,12:26
Quote (Hannes @ Jan. 13 2005,01:50)
Here are my personal notes on how to do this. Please note that bits and pieces of this are pasted from docs others have written. I have not specifically credited them in these docs because this was originally just intended as notes to myself to help me remember if I came back to this after a long period of time. Some of the notes have some rough edges so feel free to ask if you have any questions or something is not clear. At the very least this may supplement other docs you have.

Hannes


Configuring Multiple Operating Systems With EasyBoot

This procedure assumes that you are working with Windows XP. The same procedure will work for Windows 2000 and Server 2003. Just modify the directory names you use to suit your needs with each OS.

1) Under “c:\EasyBoot\disk1” create a subdirectory called “WXP1”

Note: You can use any valid 4 character directory name here, however you should make certain to use all caps. Substitute whatever you use for “WXP1” in all the references below.

2) Copy the contents of your Windows XP CD to the “WXP1” directory. You can delete extra folders such as the Support directory later if you wish, but you should copy the entire CD contents over for now, especially if you want to slipstream in a Service Pack (See “Optional Steps to Slipstream in SP1” below).

Optional Steps to Slipstream in a Service Pack

If your installation files do not already have the latest Service Pack slipstreamed in then you can slipstream in the Service Pack now. This example shows how to slipstream SP1a into Windows XP. The same procedure works for Windows 2000. Of course, you simply need to modify the directory names below and the name of the Service Pack file.

A) Copy the contents of the Windows XP CD to a directory on a HD. In this example, we’ll assume C:\XP
B) Download the FULL Service Pack package (not the minimal install package).
C) Make a directory on you HD to extract the Service Pack files to, for example, C:\SP1a.
D) Open a command prompt and change to the directory where the SP is located. Issue the command “xpsp1a_en_x86.exe –x”. When asked where to extract the files to, point to the directory you just created (C:\SP1a in the example above).
E) Change to the directory where the SP files were just extracted to and go to the update directory.
F) Issue the command “update /s:c:\xp”

You have now slipstreamed the Service Pack into your installation files.

If you now want to create a bootable CD with the slipstreamed Service Pack do the following:

A) Extract the boot sector from your original Windows CD using a utility such as Ultra ISO.
B) Open a CD Burning application such as Nero or Easy CD Creator. Choose to create a bootable CD. You should set the emulation type to “No Emulation” and load 4 sectors.
C) If using Nero Burning ROM be sure to check the box that reads:

Do not add the “;1” ISO file version extension.
Note: Current  versions of Easy CD Creator don’t have this option  but seem to work properly by default.

D) Use the Joliet file system, allow paths more than 8 levels deep, and allow more than 255 characters in the path. Set the volume label to be the same as the original CD.

End of Optional Steps to Slipstream the Service Pack

3) Copy the files from the root of your Windows XP CD to the “c:\EasyBoot\Disk1” directory. For Windows 2000 this includes all files whose names start with “cdrom”. For Windows XP and Server 2003 copy all files starting with “win51”. This includes the files such as “WIN51”, “WIN51IP”, etc.

4) Use a tool such as UltaISO to save the bootsector from your CD to the “c:\Easyboot\Disk1\ezboot” directory. As an alternative you can use download a bootsector file. Rename as you see fit. For example, if you plan to have two copies of Windows XP, such as a retail version and a Volume License edition you can call one bootsector file “WXP1.bin” and one “WXP2.bin”. Use the search and replace text tool built into EasyBoot to change all occurrences of “I386” to “WXP1” in this file (remember to use all caps). The name of the bin file is not what matters here. What matters is that I386 is modified to match the name of the directory that your installation files are in.

5) The goal of this step is to simply copy the boot files needed to install Windows from the “i386 directory to the “WXP1” directory (or whatever directory you are using). There are two methods you can use here. The first method is far simpler to perform and involves using a simple batch file to copy files over from the i386 directory. The second method is good if you want to be 100% certain that you are copying the correct files over. This might be useful if a new Service Pack is released or you have a special version of Windows such as an OEM version that has additional files that the batch file does not account for. The bottom line is that Method 1 should work fine but Method 2 is a sure bet.

Method 1
=======
Copy the boot files from the “i386” directory to the “WXP1” directory. To do this, use the appropriate batch file available in the resources directory of your EasyBoot installation. There is a batch file for Windows XP Pro, one for all versions of Win2000, and one for all versions of Server 2003. Place the batch file for Windows XP in the “WXP1” directory and then run it by double-clicking it. After it has run you can delete it if you wish.

Method 2 for Windows XP or Server 2003
==============================
Thanks to the MSFN forums for this information:

Make a backup copy of the c:\boot.ini file. This procedure will cause this file to be modified so you will want to be able to change it back after that happens.

Go to Start -> Run and type or paste the following command:

<path to i386 directory for XP or Server 2003>\winnt32.exe /noreboot

Example: c:\Easyboot\disk1\WXP1\i386\winnt32.exe /noreboot

Windows XP setup should come up. Choose "New Installation" and go through the options as usual. Do NOT download updated setup files. At the "Setup Options" screen, click on "Advanced Options" and make sure "copy all installation files from the CD" is checked. If it is grayed out don't worry about it.
Setup should create 2 folders in the root of your main drive. They will be hidden so make sure "Show hidden files and folders" is enabled.
$WIN_NT$.~BT - the boot folder$WIN_NT$.~LS - installation files folder
Copy the contents of $WIN_NT$.~BT to “WXP1”.

Now in the “WXP1” folder delete the following files:
BOOTSECT.DAT
migrate.inf
winnt.sif

IMPORTANT: Now there's just one last thing we have to do. When we ran setup like we just did, it expects us to be installing a new operating system the next time we reboot, so setup adds an extra boot option in the boot.ini file and changes the default boot choice to it. Delete the boot.ini file and rename the copy you made earlier to boot.ini.

Method 2 for Windows 2000
=========================

The method described above for Windows XP and Windows Server 2003 will not work for Windows 2000 if you are running on a Windows XP based OS.


Install an ISO image of 2000 Professional in VMware. Copy the contents of the ISO into a folder on the virtual installation's desktop, and slipstream in SP4 if not already done. Run winnt32.exe from the i386 folder. Windows 2000 setup should come up. Choose "New Installation" and go through the options as usual. Do NOT download updated setup files. At the "Setup Options" screen, click on "Advanced Options" and make sure "copy all installation files from the CD" is checked. If it is grayed out don't worry about it. When it's done do NOT let it reboot.

Setup should create 2 folders in the root of your main drive. They will be hidden so make sure "Show hidden files and folders" is enabled.
$WIN_NT$.~BT - the boot folder$WIN_NT$.~LS - installation files folder
Copy the contents of $WIN_NT$.~BT to “WXP1”.

Now in the “WXP1” folder delete the following files:
BOOTSECT.DAT
migrate.inf
winnt.sif

IMPORTANT: Now there's just one last thing we have to do. When we ran setup like we just did, it expects us to be installing a new operating system the next time we reboot, so setup adds an extra boot option in the boot.ini file and changes the default boot choice to it. Delete the boot.ini file and rename the copy you made earlier to boot.ini.

___


6) Edit the file “setupldr.bin” in the “WXP1” directory. Again, use the search and replace text tool built into EasyBoot. Change all references of “i386” to “WXP1”. Use all capital letters except for the “i” in “i386”.

7) Edit the file “txtsetup.sif” in the “WXP1” directory and change the value for “SetupSourcePath” from “\” to “\WXP1”. Note: You can use notepad to do this, however, it is very important to check the file after you save it to be sure that notepad has not appended a “.txt” extension to the end of it! I would suggest using Wordpad rather than Notepad.

8) When making your boot menu in EasyBoot use “run wxp1.bin” to run this installation of Windows  XP.

Note: When you install, at the time of the first reboot you should eject the CD or DVD and reinsert it only when Windows prompts for it again. I found that even though I set EasyBoot to boot from the HD when it timed out, for some reason Windows XP could not find files on the CD then.  If I boot directly to the HD then all works fine. At least, that’s what happened in my VMWare test &#61514;.

Creating an Unattended Setup Installation

Follow the instructions as above for setting up an OS in EasyBoot

Create a $OEM$ directory at the same level as the i386 directory. The directory structure should look like this:

I386
$OEM$
     $1
           Install
           Drivers
     $$
           System32
     $Docs
     $Progs

From the Windows Deployment tools copy “setupmgr.exe “ and “ref.chm” to a directory on the HD. Run “setupmgr.exe”. Use the following options:

New or Existing Answer File: Create New
Type of Setup: Unattended Setup
Windows Product: Windows XP Home / Professional
User Interaction: Fully Automated
Distribution Share: Set up from CD (ignore the message about IE customizations, they work actually!)

Having done that, accept the Licence Agreement, then fill in all the boxes as you would during Windows XP Setup. If you come across a section that you don't understand, then ignore it. Windows XP will use whatever default option there is for that section.
When you've finished, it creates a file called unattend.txt. Since we are going to run Setup from a CD we need to rename this to winnt.sif.

But to make this work, we need to specify two values in the winnt.sif file under [Unattended]:
[Unattended]
OemPreinstall=Yes
UnattendSwitch="yes"
OemPreinstall=Yes instructs Windows XP Setup that there is an $OEM$ distribution share on the CD. This will tell setup to copy them over to the destination hard drive of where Windows is being installed.
UnattendSwitch="yes" instructs Windows XP Setup to skip the "Welcome to Windows XP" screens, where user account and Internet setting-up takes place.

If you prefer to manually choose a partition during text-mode setup with full control on choice of filesystem, then make sure you have these lines set as they are under the [Data] and [Unattended] sections in winnt.sif:
[Data]
AutoPartition=0
[Unattended]
FileSystem=*

Normally you would add the winnt.sif to the i386 directory but when using EasyBoot you will want to add it to the directory that you copied the Windows files into and where the boot files have been copied. For example, if you copied your Windows XP CD contents to Disk1\WXP1 then you will want to put the winnt.sif in the WXP1 directory.

End of Unattended Setup Configuration


How to Integrate Acronis Products into EasyBoot

Notes for integrating Acronis TrueImage:
1) Use UltraISO to extract boot file of a bootable CD
  created by Acronis TrueImage, save it as trimg.bif in the disk1\ezboot directory
2) Use 'bootinfotable;run trimg.bif' as menu command to load it
3) For TrueImage, copy the remaining files from the root of the CD directly to the disk1 directory.


Adding Norton Ghost 9 to the Multiboot Disc

Copy all the files from the root of the CD to the EasyBoot\disk1 directory.

Make a 4 letter directory (I used GST9) just like you would for any copy of Windows XP, Server 2003, etc. Copy the entire i386 directory from the Ghost 9 CD over to this directory.

Modify the setupldr.bin and the txtsetup.sif just as for other Windows installations. Do the same for the boot sector.

If you want to get rid of the message asking you to press any key to boot from the CD delete the bootfix.bin file.

4) Use a tool such as UltaISO to save the bootsector from your CD to the “c:\Easyboot\Disk1\ezboot” directory. As an alternative you can use download a bootsector file. Rename as you see fit. For example, if you plan to have two copies of Windows XP, such as a retail version and a Volume License edition you can call one bootsector file “WXP1.bin” and one “WXP2.bin”. Use the search and replace text tool built into EasyBoot to change all occurrences of “I386” to “WXP1” in this file (remember to use all caps). The name of the bin file is not what matters here. What matters is that I386 is modified to match the name of the directory that your installation files are in.

Sorry, may i know which a where is >bootsector files<  can u make it clear...thanks so much
Posted by vikas123 on Apr. 01 2007,12:06
I made a N in 1 DVD with easy boot. I added win98, win me, win2000 pro, win2003(all the three versions), winXP pro, winXP home, winXP media center, ERD commander 2003, UBCD 3.4 full, acronis trueimage workstation bootable cd.
Win98, win me, winXP pro, winXP home and UBCD work well (I mean computer boots from these bootables) but when I try to boot from others, following errors appear:
(1)Win2000 : Could not find NTLDR
(2)Win2003 All versions : setuptxt.sif corrupted or missing (or something like this)
(3)ERD commander : Could not find NTLDR
(4)Acronis Trueimage : Could not find NTLDR
(5)Win XP media center : setup runs properly in text mode setup but when enters into
                                         GUI mode setup during file copy, setup promt me to give exact path of setup files and when I give the path G:\WXPM\I386 (WXPM is the directory of win XP media center) setup runs properly but I have to repeat this step again and again when promt. Please Help ME……..