Forum: EasyBoot
Topic: Multiboot XP CD\DVD
started by: DataMind
Posted by DataMind on Aug. 13 2005,06:22
Hi
Is it possible to make a multiboot CD / DVD with several xp versions in it? like pro home pro sp1 home sp1?

tx DM
Posted by eureka on Aug. 13 2005,08:22
Hello DataMind

Please start with reading help file in EasyBoot (especially “Practical Guide”).

There are also several topics in this forum that discuss this issue.

Here’s a nice link to use: < http://gosh.msfnhosting.com >

eureka
Posted by DataMind on Aug. 13 2005,13:03
hey thanx for replying the truth is i read the practical guide first and then came here the point is i have a perfectly clean idea on how to fit multiple versions of winz in a dvd the point is when i have only xp versions i get confused eg when i have pro sp1 and pro sp2 wich files i have to add to the root as both have an IP.... file. i hope u get what im saying sorry about my english :)

DM
Posted by eureka on Aug. 13 2005,14:38
To DataMind

Depending if it’s an original XP, or XPsp1 or XPsp2 you need files like: Win51, win51IP, win51ip.SP1, win51IP2, and finally win51ip.SP2. Setup only uses what’s necessary according to different XP-setup (XP, XPsp1 or XPsp2). Win51 files according to XPhome have different names, so it’s okay to put these ones to on the root (if creating such an multiboot-CD\DVD)

It’s no harm to have every Win51 file on the root (if you suddenly change from having original XP or XPsp1 or XPsp2 setup folder or Xphome edition). Don’t forget to put this win51.files not only on the root, you need them also parallel to each i386 folder (if building a kind of multiboot-CD/DVD).

A “normal” multiboot could look like this:

EasyBoot\disk1\Win51, win51IP, win51ip.SP1, win51IP2, win51ip.SP2 (the root folder)

EasyBoot\disk1\Setup\XP\i386 (this is original XP)
EasyBoot\disk1\Setup\XP\Win51, Win51IP (as you can see, Win51 files parallel with i386 folder)

EasyBoot\disk1\Setup\XPsp1\i386 (servicepack 1).
EasyBoot\disk1\Setup\XPsp1\Win51, Win51IP, Win51ip.sp1 (same here)

EasyBoot\disk1\Setup\XPsp2\i386 (servicepack 2)
EasyBoot\disk1\Setup\XPsp2\Win51, Win51IP2 Win51ip.SP2 (and finally, same here)

No problems with your English…

eureka
Posted by DataMind on Aug. 14 2005,05:02
hey thanx man/woman (pick the one that fits you :))
as u can see you solved ma problem im going to make the DVD from scratch now and follow the guide.. AH u made someone a happy man today u should be proud of your self ;) ill come back with more problems ... and thanx for the english thing.

DM

Posted by DataMind on Aug. 15 2005,04:02
unfortunatly after all this work i ended up with "couldnt find NTLDR" :(
Posted by eureka on Aug. 15 2005,09:13
To Datamind

"couldnt find NTLDR".
You have to explain how you created this multi-CD/DVD.

Where did you put different “Boot-folders”, and to what name/names?

Did you change path in “boot loader-file” (file in ezboot)?

Did you change “Setupsource” in Txtsetup.sif file and where did you put this file?

In fact, in what way have you created each different “Boot”-folder? Did you use “Gosh´s way”? < http://gosh.msfnhosting.com/http://gosh.msfnhosting.com > to reduce size and/or in what way did you create different boot-folders?

-------------------------------------------
I repeat how a “normal” multiboot (different WinXP pro) could look like, but show you more specific.

A “normal” multiboot could look like this:
-------------------------------------------
EasyBoot\disk1\Win51, win51IP, win51ip.SP1, win51IP2, win51ip.SP2 (the root folder)

EasyBoot\disk1\XPST (Setup files according to XP original) Note*
EasyBoot\disk1\XPS1 (Setup files according to XPsp1  With Servicepack 1)
EasyBoot\disk1\XPS2 (Setup files according to XPsp2  With Servicepack 2)

EasyBoot\disk1\Setup\XP\i386 (this is original XP)
EasyBoot\disk1\Setup\XP\Win51, Win51IP (as you can see, Win51 files parallel with i386 folder)

EasyBoot\disk1\Setup\XPsp1\i386 (servicepack 1).
EasyBoot\disk1\Setup\XPsp1\Win51, Win51IP, Win51ip.sp1 (same here, only some different file)

EasyBoot\disk1\Setup\XPsp2\i386 (servicepack 2)
EasyBoot\disk1\Setup\XPsp2\Win51, Win51IP2 Win51ip.SP2 (and finally, same here, only some different file)
-------------------------------------------
Note*: I only show this Setup folder (XPST), it’s the same procedure with other stuff (only different names).
In EasyBoot\disk1\ezboot I have put a renamed copy of  w2ksect.bin (comes with EasyBoot and renamed this one to XPORIGIN.BIN), and have also changed path (hexedit) in this file from original I386 to XPST (only one textstring is changed here). In same boot folder (XPST) I have changed path in Setupldr.bin from i386 to XPST (this is done in several places in this file).
Finally: I have moved Txtsetup.sif from original i386 folder to this Boot folder (XPST) and changed “Setupsource” to : SetupSourcePath = "\SETUP\XP\". I have also put my Unattended file (winnt.sif) in this Boot folder (XPST).

Note: To hexedit files you may use EasyBoot>Tools>Replace Text…
To start my WinXPpro-original Setup, I use command:  run xporigin.bin  

A good advice: I you not using some kind of “Virtuell PC”, start doing it! In this way you wont spoil any CD/DVD!
Microsoft Virtual pc: < http://www.microsoft.com/windows/virtualpc/default.mspx >

eureka
Posted by DataMind on Aug. 16 2005,04:50
thanx 4 posting..
i use a Virtual PC and its Microsoft Virtual PC if i burned all these unsuccessful compilation i would have to buy a DVD store...:D i will do it all over and tell ya
each step

thanx again.
Posted by eureka on Aug. 16 2005,05:10
To DataMind

He, he… quoting: “i would have to buy a DVD store...:D” good point….

About creating different ”boot-folders”.

One way is to download WinXP (or win 2000 etcetera) appropriate set of boot disk. Link here: < http://www.bootdisk.com/bootdisk.htm >

You will be redirected to Microsofts download site with different downloadable exefile (set of floppy disk). Right click on downloaded exefile and expand to folder, and then use Winimage to extract every file from every image containing the complete set of setup files, and in this way create separate “boot”-folder(s).

eureka
Posted by DataMind on Aug. 16 2005,05:21
I did this 4 test:
 Here is a step by step instruction for adding Windows XP (English version):
1) Make a folder named 'xpen' under 'c:\easyboot\disk1'
2) Copy 'win51' and 'win51p' (from root directory of original CD) to 'c:\easyboot\disk1'
3) Copy I386 folder to 'c:\easyboot\disk1\xpen'
4) Copy wxp.bat from 'c:\easyboot\resource' to 'c:\easyboot\disk1\xpen', and run it there
5) Copy w2ksect.bin in 'c:\easyboot\disk1\ezboot' to a new file xpen.bin
6) Start EasyBoot, click 'Tools'->'Replace Text', browse file 'c:\easyboot\disk1\ezboot\xpen.bin', and specify 'I386' as "Text to Replace", 'XPEN' as "Replace to", then click 'Replace', 1 occurence should be replaced
7) Do step 6 to 'c:\easyboot\disk1\xpen\setupldr.bin', and replace 'i386' to 'xpen', 4 occurences should be replaced
8) Open 'c:\easyboot\disk1\xpen\txtsetup.sif' by NotePad (or UltraEdit), search for 'SetupSourcePath', and change [SetupSourcePath = "\"] to [SetupSourcePath = "\XPEN"] (not include [])
9) Set the menu item's command as 'run xpen.bin'
10) Save menu file
-------------------------
The only changes i made is use HOM1 instead of XPEN
and added to the root:Win51, Win51IC, Win51ic.sp1.
now now how i make the iso?

Posted by eureka on Aug. 16 2005,05:35
To DataMind

“7) Do step 6 to 'c:\easyboot\disk1\xpen\setupldr.bin', and replace 'i386' to 'xpen', 4 occurences should be replaced”

If it doesn’t run as expected, replace from xpen to uppercase in setupldr.bin (XPEN).
Please in the same time, rename folder xpen to uppercase (XPEN) and as I pointed out, use caps in setupldr.bin according to XPEN.

Note: This method (using wxp.bat) works on XP (wxp.bat only copies setup files to folder XPEN). You need separate “boot”-folder if making some heavy multiboot-CD/DVD.

eureka
Posted by DataMind on Aug. 16 2005,05:53
Ah ok im dld the files u said and i have the folder i said above now what i got confused :O
Posted by eureka on Aug. 16 2005,06:00
To DataMind

A good idea is to use CAPS to everything (no problems with ”uppercase” here and there).

eureka
Posted by DataMind on Aug. 16 2005,06:09
ok lets try one more time..(sorry for tiring you ok?) i have all the setups files u said eatch one has 6 .img files what do i ido with them and how i use them to the MBDVD?if you can describe the proccess once more.
Posted by eureka on Aug. 16 2005,06:26
To DataMind

Wait some our or so, it’s lunch time :-))

eureka
Posted by DataMind on Aug. 16 2005,06:32
oooopppps sorry man/woman have a nice lunch :) oh and when u r ready post you ^%^&$%#%$#$$&^ (lol joking)
Posted by eureka on Aug. 16 2005,10:19
To DataMind

Have bending here and there but run in to the ”wall”. I thought I could create a simple guide without using “Gosh's homepage” < http://gosh.msfnhosting.com > but you have to use this method and reduce size and in that way create a well working BOOT-folder.

Step 1: Create a folder with a four letters name in EasyBoot\disk1. Let’s call it XPS2 (Note: uppercase)
Step 2: Copy every file from boot-folder created bye “Gosh's way” to XPS2.
Step 3: Create a new folder in EasyBoot\disk1 with the name SETUP (Note: UPPERCASE)
Step 4: Create another folder in EsyBoot\disk1\SETUP an name it XPPRO2
Step 5: Copy Win51-files to EasyBoot\disk1 and also to EasyBoot\disk1\SETUP\XPPRO2
Step 6: Copy folder i386  (from CD or whatever) to  EasyBoot\disk1\SETUP\XPPRO2 or use reduced system folder (created in “Gosh's way”) but remember to rename it to i386.
Step 7: Copy Txtsetup.sif from i386 to folder EasyBoot\disk1\XPS2 (the boot-folder)
Step 8: Open 'c:\ EasyBoot\disk1\XPS2\txtsetup.sif' by NotePad (or UltraEdit), search for 'SetupSourcePath', and change [SetupSourcePath = "\"] to [SetupSourcePath = "\SETUP\XPPRO2\"] (not include [])
Step 9 : Copy w2ksect.bin in 'c:\easyboot\disk1\ezboot' to a new file xps2.bin
Step 10: Start EasyBoot, click 'Tools'->'Replace Text', browse file 'c:\easyboot\disk1\ezboot\xps2.bin', and specify 'I386' as "Text to Replace", 'XPS2' (Note: Uppercase)
Step 11: Do step 10 to 'c:\easyboot\disk1\XPS2\setupldr.bin', and replace 'i386' to 'XPS2', 4 occurrences should be replaced (Note: Uppercase with XPS2)
Step 12: Set the menu item's command as: run xps2.bin

Tested and works (Attention: You have to use “Gosh's homepage” and create functional boot-folder).

I used some of your text.

eureka
Posted by DataMind on Aug. 16 2005,11:04
ok ill go right away and try but i didnt see where i use the setup files u mentioned earlier.also when i add XPS1 for example i ll just add XPS1 folder in .../disk1 and do the proccess for this?

thanx a million.

DM
Posted by eureka on Aug. 16 2005,11:32
To DataMind

Skip my suggestions with using floppy images – it doesn’t work because we getting problems with “EULA” using this method.

You need a well running standalone boot-folder to make it work. And then copy files from this “Gosh” boot folder to XPS2 (Note I named it to XPS2= XP with servicepack 2  Different systems= different names to keep things apart).

Attention: Be carefull about boot.ini file (resides on C:\). Make a copy of boot.ini to a safe place (floppy?).

eureka
Posted by DataMind on Aug. 16 2005,13:26
ok i extracted $WIN_NT$.~BT from my cd now what else i need to follow from Gosh?
Posted by eureka on Aug. 16 2005,15:19
To DataMind

Step 1: Create a folder with a four letters name in EasyBoot\disk1. Let’s call it XPS2 (Note: uppercase)
Step 2: Copy every file from boot-folder created bye “Gosh's way” to XPS2.
Step 3: In XPS2 delete following files: bootfont.bin and migrate.inf
Step 4: Create a new folder in EasyBoot\disk1 with the name SETUP (Note: UPPERCASE)
Step 5: Create another folder in EsyBoot\disk1\SETUP an name it XPPRO2
Step 6: Copy Win51-files to EasyBoot\disk1 and also to EasyBoot\disk1\SETUP\XPPRO2
Step 7: You have two options here: Copy folder i386  (from CD or whatever) to  EasyBoot\disk1\SETUP\XPPRO2 or use reduced system folder i386 that resides in ”$win_nt$.~bt” (created in “Gosh's” way). I suggest “Gosh's” way of folder.
Step 8: Open 'c:\ EasyBoot\disk1\XPS2\txtsetup.sif' by NotePad (or UltraEdit), search for 'SetupSourcePath', and change SetupSourcePath = "\"   to    SetupSourcePath = "\SETUP\XPPRO2\"
Step 9 : Copy w2ksect.bin in 'c:\easyboot\disk1\ezboot' to a new file xps2.bin
Step 10: Start EasyBoot, click 'Tools'->'Replace Text', browse file 'c:\easyboot\disk1\ezboot\xps2.bin', and specify 'I386' as "Text to Replace", 'XPS2' (Note: Uppercase)
Step 11: Do step 10 to 'c:\easyboot\disk1\XPS2\setupldr.bin', and replace 'i386' to 'XPS2', 4 occurrences should be replaced (Note: Uppercase with XPS2)
Step 12: Set the menu item's command as: run xps2.bin

Option (in fact necessary). You have to make changes or completely remake winnt.sif in XPS2. Make following changes in winnt.sif in folder XPS2: Change line “msdosinitiated="1"  to “msdosinitiated="0"  and delete line “Win32Ver="a280105"”

But I suggest a completely new unattended file. This is my unattended (you may put a “;” (no quotes) in beginning of stuff you don’t want to use. Use this text instead of text in winnt.sif that resides in XPS2.

;SetupMgrTag
[Data]
   AutoPartition=0
   MsDosInitiated="0"
   UnattendedInstall="Yes"

[Unattended]
   Repartition=No
   UnattendMode=FullUnattended
   OemSkipEula=Yes
   OemPreinstall=No
   UnattendSwitch="yes"
   TargetPath=\WINDOWS
   WaitForReboot = No
   Hibernation=No

[PCHealth]
   ER_Display_UI = 0

[Components]
   ;Does not install AutoUpdate
   autoupdate = Off

[GuiUnattended]
   AdminPassword=*
   AutoLogonCount="999999"
   AutoLogon="yes"
   EncryptedAdminPassword=NO
   OEMSkipRegional=1
   TimeZone=110 ;you may need to change timezone
   OemSkipWelcome=1

[WindowsFirewall]
   Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
   Mode = 0

[PCHealth]
   ER_Display_UI = 0

[Components]
   ;Does not install AutoUpdate
   autoupdate = Off

[UserData]
   ProductID=11111-22222-33333-44444-55555 ;replace numbers with your CD-key
   FullName="anonymous" ;another name perhaps?
   OrgName="home"
   ComputerName=computer

[Branding]
   BrandIEUsingUnattended=Yes

[URL]
   Home_Page=http://www.google.se/ ;change startpage?

[Proxy]
   Proxy_Enable=0
   Use_Same_Proxy=1

[Identification]
   JoinWorkgroup=MSHOME

[Networking]
   InstallDefaultComponents=Yes

[Display]
   BitsPerPel = 16
   Vrefresh = 85
   Xresolution = 1024
   Yresolution = 768

;End of text

Tested and works

Delete files and folders o C:\ with names like $win_nt$.~ls and $ldr$, we don’t need these any more.

(I used some of your text).


eureka
Posted by DataMind on Aug. 17 2005,04:55
Hey i added only HOMESP1 just for test... it really booted!!!!!.  To add the rest OSes i just have to change the BOOT and the other folder names right?

thanx a trillion eurika :):D

I think u must put this for your sig (LOL):
"DataMind... eurika's joy".

Posted by eureka on Aug. 17 2005,05:52
To DataMind

Good to notice progress from you.
Nice feedback…. Thanks from a (male) Swede to you…

Success! It is possible to use “Setup Disks for Floppy Boot Install”.

But you have to do following, delete this files in boot folder (XPS2): “Bootfont.bin”, “1394VDBG.sy_”, “Txtsetup.si_” and then continue with copy Txtsetup.sif from i386 to this separate boot-folder (XPS2) and finally create a winnt.sif file (unattended file) in boot-folder (XPS2).

This means that it is not necessary to run “Gosh” way and reduce system folder. It’s possible to use original i386 folder from CD. However, I personally find it more interesting using “Gosh” way.

eureka
Posted by eureka on Aug. 17 2005,06:11
To DataMind

I forgot … Quote: “To add the rest OSes i just have to change the BOOT and the other folder names right?”
Yes that’s correct! And it’s up to you to give every separate boot folder different names (Note: always uppercase= CAPS).

eureka
Posted by DataMind on Aug. 17 2005,10:40
hey im back :) listen to this when i added HOMESP2 and tested when the setup started it said:"insert the disk windows xp home sp2  in A:and press enter".why? what did i do wrong?

oh and if i wanna use “Setup Disks for Floppy Boot Install” do i have to del migrate.inf?

PS: i may have to create a new topic but see this:
lets suppose that we got a XPPROSP2 (EN) CD can we make it and other language? like FR or GE? as you see i became more inquiring with xp now that i know more things about installation... i like learning.

DM

Posted by eureka on Aug. 17 2005,13:17
To DataMind

Quote: “when i added HOMESP2 and tested when the setup started it said:"insert the disk windows xp home sp2  in A:and press enter".why? what did i do wrong?

You don’t have the complete set of necessary Win51 files on the root (EasyBoot\disk1). Someone is missing!

Quote: “can we make it and other language? like FR or GE?”
Yes you can! But you need to use different system folders (different i386 folders). But in the same time, it’s possible to use the same BOOT folder (in my example named XPS2) and use this boot folder to different languages (but same servicepack). However this is a little bit more complicated. You have here two options:

1. Create different BOOT, folders that have different txtsetup.sif (different path in txtsetup.sif to setupsource) and different setupldr.bin file.
2. Use same BOOT folder to same system, but different names on different Setupldr.bin in this boot folder. In this case you have to hexedit (using EasyBoot>text modifier) files a lot of more than you have done before. It’s a little bit tricky.

I suggest you use different BOOT folders. Use “Optimize” when creating ISO file in EasyBoot, in that way the final ISO will be “compressed” (same file only used one time= no doublets) witch highly reduce size on finished CD/DVD. In the same time I suggest you use “Gosh way” < http://gosh.msfnhosting.com/ >  to reduce size and in the same time get a nice boot folder. Note: If you have created a BOOT folder in “Gosh way” with sevicepack2, then it’s possible to use this to different language (make copies of this BOOT folder and rename it to “French version” and “English version” etcetera. If you have created BOOT folder with servicepack 1, use copies of this one to different languages.

Example showing only XPpro servicepack 2:

EasyBoot\disk1\Win51, win51IP2, win51ip.SP2 (and more files with Xphome/XPpro-sp1)

EasyBoot\disk1\XP2E (Boot folder servicepack 2 English) Create boot folder in you language
EasyBoot\disk1\XP2F (Boot folder servicepack 2 French) Same boot folder as above, only a renamed copy
EasyBoot\disk1\XP2S (Boot folder servicepack 2 Spain) Same boot folder as above only a renamed copy

EasyBoot\disk1\Setup\XPsp2ENG\i386 (servicepack 2 English)
EasyBoot\disk1\Setup\XPsp2ENG\Win51, Win51IP2 Win51ip.SP2

EasyBoot\disk1\Setup\XPsp2FR\i386 (servicepack 2 French)
EasyBoot\disk1\Setup\XPsp2FR\Win51, Win51IP2 Win51ip.SP2

EasyBoot\disk1\Setup\XPsp2SPA\i386 (servicepack 2 Spain)
EasyBoot\disk1\Setup\XPsp2SPA\Win51, Win51IP2 Win51ip.SP2

I personally use paper and pen, in this computer age :-)) Otherwise I always mix things up (it’s sometimes a big mess).

eureka
Posted by DataMind on Aug. 17 2005,13:28
Hey man (now i know)
so you mean that if i get the i386 and other folders but use the win51... files from other lang will work? i didnt get wheres the diff.

thanx man. oh by the way im greek :)
Posted by eureka on Aug. 17 2005,14:07
To DataMind

Yes the same win 51 files to different languages.

I have been living in Spain for a couple of years ago, and hope to make Greece my next “Stop” on “the line”.

eureka
Posted by DataMind on Aug. 18 2005,06:43
heh i suppose i got u confused lol. just dump the MB. lets say i have only one CD PROSP2 (EN)
can i make it PROSP2 (GR) by changing some files?( remember we got only 1 cd nothing else).

thanx again.
Posted by eureka on Aug. 18 2005,08:45
To DataMind

Quote: ”by changing some files?”

Absolutely not! Nearly every file in system setup folder (i386) is unique according to language. If this wouldn’t be so, Microsoft only would need one single CD to distribute every country’s specific differences (language).

I think you need a DVD. But It’s possible to have BartPe and WinXP on same CD (Note: If you use “Gosh way” of reducing size on folder i386).

eureka
Posted by DataMind on Aug. 18 2005,10:10
ah i have some questions
1 whats BartPE?whats its use?
2 what does file w2ksect.bin do?
3 what do bootfont.bin and migrate.inf files do?
4 when i boot from HDD option from the EZboot boot menu itsays couldnt find ntldr i wrote boot 80 why doesnt it boot?

Posted by eureka on Aug. 18 2005,12:00
To DataMind

W2ksect.bin is the BOOT file, designed to point (in this case) to SETUPLDR.BIN witch then executes and start the whole installation procedure. To make it brief: The BOOT file is stored on a disk partition, diskette (or on “boot sector” on CD/DVD) and is loaded into memory.

BOOTFONT.BIN is dealing with the font and used during the initial boot when starting the system (Windows or similar). The BOOTFONT.BIN is not actually needed, it is for international char set. The loader (boot loader) does look for it, but its absence is not necessary. You don’t need to care about it.

Migrate.inf? To my knowledge this file is used when you updating from Win9*/Me to Win NT systems (XP included). Note: when reducing size (“Gosh way”), you won’t be able to “migrate” from lower level (Win9X/Me) to “higher” level (WinXP). But who runs updates from win9X or WinMe this days? This means that we don’t need this file any more on a reduced system.

BOOT 80 points to boot sector on hard disk, and in fact, I don’t understand your question?
If you write “boot 80” in the menu (Note: not “run boot 80” only “boot 80”) the system should look for bootable medium (normally looking for boot sector on first bootable hard disk). I don’t now what you have done here?

Finally: BartPe is a “Preinstallation environment” witch is capable to run WinXP from CD/DVD. With BartPe running from CD/DVD (booting from CD/DVD) you even don’t need a hard disk in the cabinet!

Link here: < http://www.nu2.nu/pebuilder/#screen >

Or maybe this is a better choice: < http://www.reatogo.de/ >

eureka
Posted by DataMind on Aug. 18 2005,13:39
man thanx what a great knowledge i aquired through this task of mine and your patience and veeeery good explanation of things! i only say keep it up.Now i have one more question for you:

quote:W2ksect.bin is the BOOT file, designed to point (in this case) to SETUPLDR.BIN witch then executes and start the whole installation procedure. To make it brief: The BOOT file is stored on a disk partition, diskette (or on “boot sector” on CD/DVD) and is loaded into memory.

can i make one ma self?

about boot 80: i wrote this cmd in the ezboot menu but when i chose this option on the VM it says couldnt find NTLDL
Posted by eureka on Aug. 18 2005,14:13
To DataMind

Quote: ”Now i have one more question for you….” Is this a new version of “never ending story?” He, he just joking :-))

“can i make one ma self?” I don’t think so. I don’t say it’s impossible, but it needs a lot of knowledge in stuff like programming.

“when i chose this option on the VM it says couldnt find NTLDR” Have you done some kind of XP-installation in VM? Because boot 80 starts to look for a boot sector on first bootable hard disk! You must have a installation to boot to on this virtual hard disk (in VM). It could bee something you have done earlier in this VM, when testing multibootCD (ISO made by EasyBoot). Or some bug. You can test Virtual Computer from Microsoft and see if it works as supposed. < http://www.microsoft.com/windows/virtualpc/default.mspx >

eureka
Posted by DataMind on Aug. 19 2005,06:06
SOS EUREKA SOS!!!!!!!!
i tryed to use the mb cd. all seemed to go normal but when i was at the state to format to an ntfs the setup said that the system doesnt have enough memory or somefiles are missing or corrupt HELP!!!!!!
Posted by eureka on Aug. 19 2005,07:56
To DataMind

I’m not sure what you mean…
Quote: ”tryed to use the mb cd” In what way using mb cd? You mean copy original i386 folder to EasyBoot\disk1? If this is the case, did you copy original txtsetup.sif file from this original i386 to separate BOOT folder? And of course changed SETUPSOURCE to right path?

Or did you only make some test using installation from CD in VM or Virtuall Computer? How much memory did you configured to virtual computer to handle? At least 200 Mb to avoid problems is a good idea to use.

eureka
Posted by DataMind on Aug. 19 2005,08:05
yes i  made some tests first on VM which has 256mb and when i was in the format to ntfs state this message appreared "the system doesnt have enough memory or somefiles are missing or corrupt" then i thought that it was VM's problem and burned it on a cd and the same problem occured. am i ruined?:(
Posted by eureka on Aug. 19 2005,08:39
To DataMind

If it is the original CD that hangs, well if that is the case, you might be “ruined”. But to be sure there isn’t something else, you need to test original CD in “real mode”. Use some other computer and test if CD works.

eureka
Posted by DataMind on Aug. 19 2005,10:51
well it doesnt work to the other pc now what whats the problem is it the redused size method?
Posted by eureka on Aug. 19 2005,11:01
To DataMind

Sorry I still don’t understand what you mean? How can you be ruined when you made a “false setup” using “Gosh method” (and in same time created BOOT folder). From what source did you made this “false setup”? Wasn’t this “false setup” made using original CD as source?

eureka
Posted by DataMind on Aug. 20 2005,03:23
Well i ll say it from the start. i burned the multiboot cd on a real[B] cd and booted from it.then i selected an OS to install from the multiboot cd and after awhile the setup printed this error:
"the system doesnt have enough memory or somefiles are missing or corrupt"
thats our problem
Posted by eureka on Aug. 20 2005,03:58
To DataMind

Well that means you still must have some original CD with WindowsXP-pro (or XPHome) still working – just in case…

However this message: “the system doesn’t have enough memory or some files are missing or corrupt" happens when some file really is corrupt. I often (in fact plenty of times) move (copy) files (i386 folder and BOOT folders) from earlier made ISO files. It’s not unusual with messages like the one you received during this process. Sometimes NTLDR gets corrupt during this copy process. You have to rework your stuff. Start from scratch.

So what! You still must have the original i386 folders.

In what way did you create ISO? Test with only using Optimize. Do not use DOS(8.3) and Joliet when making ISO in EasyBoot.  

Please use Virtual PC (or VM) before you test ISO with CD (or use CD-RW).

eureka
Posted by DataMind on Aug. 21 2005,09:08
hey i reworked all this now it works perfectly (at least on VM) i found where the prob was,the step "Step 7: You have two options here: Copy folder i386  (from CD or whatever) to  EasyBoot\disk1\SETUP\XPPRO2 or use reduced system folder i386 that resides in ”$win_nt$.~bt” (created in “Gosh's” way). I suggest “Gosh's” way of folder."
gosh's i386 didntwork 4 me thats why files were missing. i made the iso with optimize. now i just have to burn it on a dvd i suppose?
Posted by eureka on Aug. 21 2005,11:37
To DataMind

Great news from you! Well as I pointed out. Sometimes when you moving files from “here to there”, you run in to troubles. Nice to se that you solved it!

Keep up the good work.

eureka
Posted by DataMind on Aug. 23 2005,06:10
hey :)
may be its off topic but...
can we unslipstream a CD like from XP SP1 make it XP simple?
Posted by eureka on Aug. 23 2005,06:24
To DataMind

Quote: ”unslipstream a CD like from XP SP1”. I don’t think that’s possible. XPsp1 is really a well working system. You avoid virus like sasser and many more problems. Service pack2 is a little bit “heavy”. But I use sp2 without problems.

Man…what have you done? Why “unslipstream a CD like from XP SP1”? You should always have backup of everything and I mean backup on a “safe” medium (CD/DVD and make this double and on different places).

eureka
Posted by DataMind on Aug. 23 2005,10:46
oh it was just an example i wondered if we can generally unslipstream as we can sleapstream something... just curious...
Posted by bad_data on Oct. 30 2009,08:56
Hello Eureka ,

I have made several multi boos os like xp home , xp pro

now my problem is that i exceded more than 700 Mb which is the max size of my cd is there a way i can burn my 1 GB iso to a 700mb cd


thanks and  regards

bad
Posted by balder on Oct. 30 2009,09:24
@bad_data

Welcome to this forum @bad_data :)

Quote: “burn my 1 GB iso to a 700mb cd ”. Looks like “Mission impossible” :;):  

It means that the data size in bytes of the file or files you are trying to burn is larger than the capacity of the disk to burn that data to. So if you have a 700 MB CD and you want to burn 1000MB to it, it won't work...the 1000 MB of total data exceeds the size of the media (700 MB).
It’s the same thing as if you tried to fill a one-cup container with two cups of water.

A single layer DVD holds about 3.8 Gigabytes (3800 Megabytes). A dual layer DVD holds double that amount or about 8 Gigs.

A CD has a different kind of formatting and layering from a DVD. The DVD has more layers of material on it, which allows more data to be stored on it.

You did check to “Optimize” ???  when creating ISO file and created ISO file is still larger than 700 MB - then you have to use a DVD instead of CD.

balder
Posted by morokat on Nov. 01 2009,04:12

(DataMind @ Aug. 16 2005,10:21)
QUOTE
I did this 4 test:
 Here is a step by step instruction for adding Windows XP (English version):
1) Make a folder named 'xpen' under 'c:\easyboot\disk1'
2) Copy 'win51' and 'win51p' (from root directory of original CD) to 'c:\easyboot\disk1'
3) Copy I386 folder to 'c:\easyboot\disk1\xpen'
4) Copy wxp.bat from 'c:\easyboot\resource' to 'c:\easyboot\disk1\xpen', and run it there
5) Copy w2ksect.bin in 'c:\easyboot\disk1\ezboot' to a new file xpen.bin
6) Start EasyBoot, click 'Tools'->'Replace Text', browse file 'c:\easyboot\disk1\ezboot\xpen.bin', and specify 'I386' as "Text to Replace", 'XPEN' as "Replace to", then click 'Replace', 1 occurence should be replaced
7) Do step 6 to 'c:\easyboot\disk1\xpen\setupldr.bin', and replace 'i386' to 'xpen', 4 occurences should be replaced
8) Open 'c:\easyboot\disk1\xpen\txtsetup.sif' by NotePad (or UltraEdit), search for 'SetupSourcePath', and change [SetupSourcePath = "\"] to [SetupSourcePath = "\XPEN"] (not include [])
9) Set the menu item's command as 'run xpen.bin'
10) Save menu file
-------------------------
The only changes i made is use HOM1 instead of XPEN
and added to the root:Win51, Win51IC, Win51ic.sp1.
now now how i make the iso?

hello

brothor i has follow u all step but its error like the picture

plese hel me all body

thanks
< error >

Posted by balder on Nov. 01 2009,04:29
@morokat

What language do you use to folder i386 (genuine English or what) ???

I couldn’t load error image (403 Forbidden) :angry:

Note: Batch file “wxp.bat” is designed to only support English language. So if you are using WinXP with a different language than English you get errors :(  

You can use a script I have designed. Scroll down to “Welcome to my website”. Scripts here are free to use for private use :)  This scripts support most language used on earth :;):

balder
Posted by morokat on Nov. 01 2009,04:45

(balder @ Nov. 01 2009,09:29)
QUOTE
@morokat

What language do you use to folder i386 (genuine English or what) ???

I couldn’t load error image (403 Forbidden) :angry:

Note: Batch file “wxp.bat” is designed to only support English language. So if you are using WinXP with a different language than English you get errors :(  

You can use a script I have designed. Scroll down to “Welcome to my website”. Scripts here are free to use for private use :)  This scripts support most language used on earth :;):

balder

this is error

please insert the compact disc labeled windows xp professional service pack 2 cd
Posted by balder on Nov. 01 2009,04:48
@morokat

Read < here > :;):

balder
Posted by morokat on Nov. 01 2009,11:36

(balder @ Nov. 01 2009,09:48)
QUOTE
@morokat

Read < here > :;):

balder

thanks u man now i'm success all 5

but i want on  7, can u tell me step to step about its?

thanks  u again my brother
Posted by balder on Nov. 01 2009,12:08
@morokat

Quyote: “but i want on  7”
If issue is to have vista itself on board your DVD (you must use DVD because vista is a big one to have on board your project) – then it’s a simple solution. Do it this way:

1. Copy everything from vista-DVD (or from inside vista-ISO)  to easyboot\disk1
2. Create menu in easyboot and use command: run Vistaldr.bin  (make sure you have Vistaldr.bin in folder ezboot)

Regards balder
Posted by morokat on Nov. 01 2009,12:48

(balder @ Nov. 01 2009,17:08)
QUOTE
@morokat

Quyote: “but i want on  7”
If issue is to have vista itself on board your DVD (you must use DVD because vista is a big one to have on board your project) – then it’s a simple solution. Do it this way:

1. Copy everything from vista-DVD (or from inside vista-ISO)  to easyboot\disk1
2. Create menu in easyboot and use command: run Vistaldr.bin  (make sure you have Vistaldr.bin in folder ezboot)

Regards balder

thanks u

but on vista i can completed yet

that i want is windows 7(I use DVD)

windows 7 support   or not?

thanks
Posted by balder on Nov. 01 2009,13:08
@morokat

If I have got this right you want vista and win-7 together on same DVD? Correct? (I guess you need a dual layer DVD because that one holds about 8 GB) :O  I have not done this but I do know it’s possible (in theory). This is a hard nut to crack :angry:  Read post nr 9 < here >


If issue is to only have win-7 on board your DVD I guess you can use same approach as when in cooperate vista ???
1. Copy everything from win-7-DVD (or from inside win-7-ISO)  to easyboot\disk1
2. Create menu in easyboot and use command: run Vistaldr.bin  (make sure you have Vistaldr.bin in folder ezboot) (Not sure it launch win-7 setup but most likely).


Here is a topic that might help to mix vista and win-7 together on same DVD - read < here >  
Please note that I do not have any win-7 DVD (or ISO) so I cannot be to any big help here :(

Regards balder
Posted by morokat on Nov. 01 2009,13:24

(balder @ Nov. 01 2009,18:08)
QUOTE
@morokat

If I have got this right you want vista and win-7 together on same DVD? Correct? (I guess you need a dual layer DVD because that one holds about 8 GB) :O  I have not done this but I do know it’s possible (in theory). This is a hard nut to crack :angry:  Read post nr 9 < here >


If issue is to only have win-7 on board your DVD I guess you can use same approach as when in cooperate vista ???
1. Copy everything from win-7-DVD (or from inside win-7-ISO)  to easyboot\disk1
2. Create menu in easyboot and use command: run Vistaldr.bin  (make sure you have Vistaldr.bin in folder ezboot) (Not sure it launch win-7 setup but most likely).


Here is a topic that might help to mix vista and win-7 together on same DVD - read < here >  
Please note that I do not have any win-7 DVD (or ISO) so I cannot be to any big help here :(

Regards balder

yes thanks on DVD vista and windows 7 its has some folder and file the same so i can't mix its
thanks
Posted by nitin_friendsall on Nov. 15 2009,09:26
hi balder,
                i have windows xp,vista and 7 ultimate  iso files ,i  also have dual layer dvd . plz tell me detail how i can burn it. i dont know how to use easy boot . vista and w7 have some same folders so what to do with same folders
i want to install some software with windows so plz tell where to put these setup files .
                      thanks a lot . plz help me
Posted by nitin_friendsall on Nov. 15 2009,10:58
Thank you worked perfect
now have the following on a dvd9
w2k
xp pro,home,media,tablet pc,x64
vista x86-x64 all editions
Windows7 rc1 7137 x64
ubuntu 9.04
Winpe2.0
plus various diagnostics tools

plz help how i can do this
in detail plz plz help
Posted by madar on Nov. 15 2009,11:04
nitin_friendsall

1.For windowses xp and vista look at link below:

< http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=1;t=2774 >

2.For adding win 7,we all should work and find out how to do that.
till this time i have not seen any information about using win 7
and vista together in web.

why don't you try to find away? we all should work and help!!!
Posted by Killer74 on Nov. 25 2009,06:24
I have a problem with my DVD
Windows Xp and Windows 7 is OK
but I Can't inculde Microsoft.Diagnostics.and.Recovery.Toolset

rename I386 folder VNXP
Cahnge txtsetup.sif and setupldr.bin I386 -> VNXP
and the Ezboot dir boot file  VNXP.bin I386 .> VNXP

when I try boot the virtula machine the following message wrote:
NTLDR is corrupted

What is the problem ?? please help.

Sorry My english is wery poor :)
Posted by balder on Nov. 25 2009,08:10
@Killer74

Welcome to this forum Killer74 :)

You didn’t wrote what "Microsoft.Diagnostics.and.Recovery.Toolset” you mean ???

Is it “Winternal ERD-7 or ERD-5” or similar – or is it the brand new ERD-8 (vista based) recovery toolset (Ms-DaRT) you try are trying to launch ???

However it seems to be "ERD" something - as folder i386 is used - but please confirm what live-build\Recovery-toolset you mean.

Nothing wrong with you English – you are welcome :;):

balder

Posted by Killer74 on Nov. 25 2009,18:35
Hello balder! Thank You.

I have three version: ERD60_x64_WinVista_SP2, ERD60_x86_WinVista_SP2, and ERD50_x86_WinXP_SP3.
I want first put, the Xp version in the Easyboot but doesn't work.

Please see the pictures:
< EasyBoot folder >
< Image files >
< Iso file structure >

If I no rename I386 folder, and not edit setupldr.bin txtsetup.sif
then working fine
what I do badly ??

Thank you for your help.

Posted by balder on Nov. 26 2009,08:53
@Killer74

First of all, good description you gave with pictures etcetera :p  – thanks! It makes it easier to understand – excellent :)
------------------------------------------------------------------------------------------





I assume that this ISO-structure you show < HERE > must be the ERD-5? Correct?

And that ISO-files; ERD60_x64_WinVista_SP2 and finally ERD60_x86_WinVista_SP2 doesn’t use folder I386 – instead using Vista structure (folder “boot”, folder “EFI” and folder “sources” and finally file “bootmgr” is what you have inside these ISO-files. Correct?)
------------------------------------------------------------------------
Let’s start with ERD-5.
Note: ERD50_x86_WinXP_SP3 is probably built using server-2003_sp2 (or sp1) as source and not on WinXP.
You can’t hex edit files used in ERD-5 because files (setupldr.bin) gets corrupted if you don’t (as first step) patch file (setupldr.bin).
I’m going to give you 3 different ways to solve issue concerning ERD-5.

1. The fully manually way: You will need a hex editor program to this
A- open the SETUPLDR.BIN file with your hex editor
B- Go to the hex address 0x2060
C- replace value 74 03 with EB 1A
D- Save the file

Now you can edit the SETUPLDR.BIN file with EasyBoot (using the Replace Text... feature under the Tools button) and replace
5 occurrence of i386 and 2 occurrence of I386 Read < HERE >

2. The “half” automatically way: Read post Nr: 9 < HERE > When you have patched setupldr.bin you are free to change name as you like. Again read < HERE >

3. The fully automatic way – I do recommend this - including possibilities to use the “half” automatically way as script has built in patch-button if you persist to do it in manually way. Scroll down to: “Welcome to my website”. Download ”startkit” followed by downloading “EasyBoot-live.script” – follow instructions how to and where to extract downloaded zip-file(s) containing script(s).
-----------------------------------------------------------
How to solve vista based ERD60_x64_WinVista_SP2 and finally ERD60_x86_WinVista_SP2 is explained below here:

Again I’m going to give you several different ways to solve this issue.

1. Create folder with name iso in EasyBoot\disk1 like this: EasyBoot\disk1\iso

2. Copy ERD60_x64_WinVista_SP2.iso and finally ERD60_x86_WinVista_SP2.iso to EasyBoot\disk1\iso

3. Rename ERD60_x64_WinVista_SP2.iso to erd60x64.iso and rename ERD60_x86_WinVista_SP2.iso to erd60x86.iso

4. Download pre-made floppy images from < HERE > – extract floppy images from zip-file to folder ezboot - in EasyBoot menu, use command: run erd60x86.ima and run erd60x64.ima

5. When creating ISO check “Allow lower case” <--very important

This still doesn't work fully out and we now have a new problem. When we created ISO checking option “Allow lower case” setup of WinXP and setup of Win-7 won’t work (you get ntldr corrupt or something or files not found for Win-7 – or whatever) - the same to loading ERD60-ISO files.

To solve this problem we need to run “uppercase” to every file and folder inside EasyBoot\disk1 (that’s a lot of files). It’s a hell lot of work to do this manually :angry:  

Again you get several ways to solve this:

1. Create a folder with name   filecase   on C:\
2. Download zip-file ctb10w32.zip from < HERE >
3. Open zip-file and extract “filecase.exe” to folder filecase
4. Start texteditor (notepad works fine) and put in following text:
 
filecase.exe /u /s /h /q /d C:\easyboot\disk1  

save text file to folder filecase with the name  filecase.cmd  (note extension .cmd not .txt) If folder easyboot is somewhere else, please change path to the accurate one – in normal case easyboot is installed to this: C:\easyboot

5. Now double click to file filecase.cmd  - filecase.exe start run and doing “it’s things” and when finished dos window automatically closes. Note: spaces in filenames are not allowed. Example: setup ldr.bin not allowed or folder name like this: win xp  doesn’t work. But this works: win_xp is okay as there are no spaces in folder name. Make sure you don’t have names to folder and files that has spaces incorporated to name.

6. Another way is to use script. You can download script “easyboot-uppercase.script “from my web page and use this to do the work for you.

Please inform me with you progress to this project – and you are of course free to ask question (if having problem or whatever) - especially if you have some questions about my scripts (how to use them etcetera) :;):

regards balder

Posted by AhrimanSefid on Nov. 26 2009,16:40
Dear balder You Very Pro.
But Me  amateur Plz Make Video And Learn All Step be Step.
Very Thank You.
Plz Add.
Posted by Killer74 on Nov. 26 2009,19:05
balder

First, Thank You Very match this long and clear description.
Second, I try to find a solution to this problem few weeks ago  :(
and now I solved it under 20 minutes, everything works !!!!  :laugh:

You Are The King !!!

Thank You again.

regards,
Killer74
Posted by AhrimanSefid on Nov. 27 2009,03:47
Hi.
Me Read All Post , But No Problam To Change I386 To ().
Me Rename I386 To Xpen Run VW No't Start For Install Windows.
Plz Help For Rename I386 Step Be Step.
Thanks A Lot

:wacko: :wacko: :wacko: :wacko:

CODE
http://flyakite.msfn.org/xpprosp1.htm
http://www.magiciso.com/tutorials/miso-create-multi-os-cd-2.htm
Posted by balder on Nov. 27 2009,04:44
@Killer74

Thanks for nice feedback :D

@AhrimanSefid

Please check following according to txtsetup.sif-file:
1. Open txtsetup.sif and search for “setupsourcepath” Make sure you changed text line from "\" to the one you use in your project (unsure how you structure looks like).
2. Make sure you deleted these files: BOOTSECT.DAT
migrate.inf
winnt.sif

If you run WinXP to your computer you can instead use my script: “easyboot-aio.script” :;):
Script does everything automatically for you. Note: you cannot run this script in Vista or Windows-7 :O

balder

Posted by Killer74 on Nov. 27 2009,22:08
balder

I ask you again,unbelievable but I have a new problem :)
I have these multiboot project:

AVAST BART CD to leave i386 folder name
True Image Home 2010 from Iso file
Windows XP prof Sp3  i386 folder renamed WNXP
Acronis Rescue Media from Iso file
MS Diagnostics and Recovery Toolset Windows XP i386 folder renamed ERD8
MS Diagnostics and Recovery Toolset Windows Vista X86 from Iso file
MS Diagnostics and Recovery Toolset Windows Vista X64 from Iso file
as You said it.


When I make it the boot dvd,and test the virtual machine everything good.


But, if I include up the windows 7
BART cd does't boot
Windows Xp freez the boot

What's wrong, please help me.
I tried to read then but I found nothing

regards,
Killer74

Posted by balder on Nov. 28 2009,03:47
@Killer74

Quote:” But, if I include up the windows 7…”

I’m not sure ???  (never done such huge project as you are creating = very impressing) but I think this might be related to how ISO is created. This must be a pretty large ISO-file and it’s probably getting “sensitive”. I guess that EasyBoot use mkisofs.exe or related software to create ISO-file. Question is which version?

Test creating ISO using UltraIso. Use “loader.bin” in folder ezboot as boot loader and of course experiment with settings (properties in UltraIso setting “Allow lower case” etcetera) and see if result is better when using this more powerful software according to create large ISO-files.

Sorry, no straight answer as this is a big project :(  – as said – impressing is the word :p

Regards balder
Posted by fardeep on Mar. 17 2010,16:50
Xp, Vista, Seven...
"impressing is the word"...  :cool:

Y need the line comand to run this win 7...
sure not "vistaldr.bin" its for Vista...

i'think... "sevenldr.bin" no?  :p  :D
Posted by balder on Mar. 17 2010,16:55
@fardeep

Welcome to this forum @fardeep :)

To make Win7 to launch setup do as following:

1. Copy everything from inside of Win7-ISO to EasyBoot\disk1
2. In EasyBoot menu use command:  run Vistaldr.bin
3. Check that you have file Vistaldr.bin in folder ezboot

When creating ISO in EasyBoot, don’t check DOS(8:3), and don’t check “Allow Lower Case” :O

Note: For the record - DOS is not used when launching Vista or Win7 :;):

balder
Posted by davesher221 on Nov. 05 2010,11:32
Hey all

I am Sumit a new member here. i have no idea how to make multiboot dvd.
Below listed are soft wares that i want as multiboot

1. Ultimate Boot CD 4.1..0
2. Acronis media 2009
3. Hiren's bootcd 11.1
4. Windows 7 ultimate
5. Windows XP SP3 with i3 processor drivers (where i can find these )
6. Kespersky rescue cd

Please tell me step by step what i have to do? I have no idea how to do it.
First time i am going to make multiboot dvd.
I have windows seven os
with easyboot 5 installed n magicISo is also installed
please tell me step by step

Thanks a lot.

Posted by balder on Nov. 05 2010,16:26
@davesher221

Welcome to this forum @davesher221

I'm away from my "home-computer" and can't participate fully out to solve your request :(
But start reading < HERE >
And < HERE >

The funny part is that if you look in post nr: 73 in this topic you have the right answer how to integrate Win7 :;):  

However please use the "search" button in the upper right corner in this forum, while I'm away from "home computer" :O  (takes at least 5 more days).

balder
Posted by Asenk on Nov. 06 2010,00:23
@ Balder

Quote “burn my 1 GB iso to a 700mb cd ”. Looks like “Mission impossible”

i think its possible but i dont know how to make it. i have XP Dark V6 CD. i got it from a friend. i tried to extract it and...wow..i got more than 7 gb. 1 of the folder named "cdshell". i think the creator use CDSHELL to built it but it seem too complicated for me coz it use commands like in DOS mode not GUI one.

7gb comes in 1 CD (700mb). its fantastic!!
Posted by davesher221 on Nov. 07 2010,10:11
[B] @ Balder
hey i am trying to get the idea how to make all files in folder disk 1. but i m not getting that exactly so plz tell me how  process from starting n step by step
for above listed soft wares.
i have all images in .iso in my computer n i have deamon tools installed for running these images n magic iso too installed
i m waiting for your arrival to ur home so that i can get a detailed guided reply by you &  all advance users
Thank you all

Posted by balder on Nov. 10 2010,12:26
@davesher221

Quote: ”how to make all files in folder disk 1”

What files and from which ISO-file(s) do you have problem with ???

Some brief explanation how EasyBoot works:

Folder “disk1” is the “root” for EasyBoot (compare with harddisk C:\)
It’s in folder disk1 you put files and folders that need to be in the “root”.

Folder “ezboot” is – as name whisper – a folder for “boot-files”. Boot-file(s) can be different.
Any bootable floppy disk image is a “boot-file” even if it in reality is a “floppy image” – but as this floppy images can be directly launched, EasyBoot treat such files as a bootable file.

To launch a bootable file that you have put in folder ezboot you simply use “run XXX.img” if it is a floppy image.
To launch setup of WinXP you can use built-in “boot-file” (W2ksect.bin). You do not need to extract boot-file from WinXP-CD or from WinXP-ISO-file (if you don’t like to do it for fun).
The “run”-command is a “basic” command – but you have more power than that in EasyBoot.
You can also launch setup of a Vista or Win-7 using this command:  run Vistaldr.bin

Note: check that you have Vistaldr.bin and W2ksect.bin in folder ezboot – they should be there.

However, these days we can launch some ISO-files directly (no need to extract files from such ISO-file). To make this possible we use “grub-“kicker-images”.
I have created a set with scripts to make it easier to implement these “kicker-images” into EasyBoot.
There are also other scripts to make “life easily to live”.
As example, we can launch EasyBoot from USB device using my script: easyboot-usb.script :laugh:

Note: scripts are totally free from costs for non-commercial use :;):  

< HERE > you have some command that “@ develi” have collected from different topics (thanks @ develi):  

In post nr: 73 in this topic you are reading, you have a pretty clear description how to get Windows-7 “onboard” your EasyBoot-project.
Is there something that you have problems with in post nr: 73 ???
------------------------------------------------------
Please – do not start with creating a “super-complexe-worldwide” build :O  
Start with one issue (like integrating Vista to EasyBoot).
When that one works – integrate another “system” (WinXP or whatever).
Continue expanding your build to the point where you are stuck – then ask for help

balder
Posted by davesher221 on Nov. 10 2010,20:32
@Balder
thanks

i ll try to make after that i ll tell you results