EZB Forum » Printable Version of Topic » Run EasyBoot from USB tutorial

Forum: EasyBoot
Topic: Run EasyBoot from USB tutorial
started by: heureka

Posted by Guest on Sep. 04 2008,03:57

Tutorial for USB boot approach.
(Okay, I know my English is far from perfect, but hope it’s readable anyway) :;):

Attention: I do not take any responsibility for any problems this tutorial may lead to!

You need some files from Windows-XP so this tutorial works primary only for systems that running Windows-XP.

Download HP format tool for USB devices from here: < http://files.extremeoverclocking.com/file.php?f=197 > >> Install this tool to [C:\]

Download Grub MBR-tool from here: < http://www.purviancecs.com/acronisdl/grubutil-1.1-bin-w32-19.zip > >> Expand zip-file

Download grub4dos here: < http://download.gna.org/grub4dos/grub4dos-0.4.4-2008-08-08.zip > >> Expand zip-file

You now have necessary tools to make EasyBoot run from USB device (stick).
--------------------------
Step 1. Stick in your USB device to computer. We need to create a batch file. Start your Notepad and insert this text:

@echo off
rem Use at your own risk
echo:
echo:
echo:
SET /P driveletter="Put in drive letter (no colon) for USB device and press Enter: "
cls
echo:
echo:
echo:
echo: *** Note: Format to NTFS take some few extra seconds ***
echo:
Hpusbf.exe %driveletter%: -FS:NTFS

Save text file to folder “drivekey” with the name: format usb.bat (Note extension bat)
Double click on batch file in folder “drivekey” and do as you are told (answer questions).
And yes there are GUI-tools for HP format tools as well (Hpusbfw.exe). It’s possible to use this to, but I found out that Hpusbf.exe works better. Don’t now why? That’s the reason I want you to use a batch file, instead of “graphic user interface” (Hpusbfw.exe).
--------------------------
Step 2. Open folder “grubutil-1.1-bin-w32-19” and double click on “grubinst_gui.exe”. A nice window shows up. Be very careful what your do here. In the top of window you find “Disk………Refresh” Push Refresh to make sure program has found your USB device. Use the little “arrow” to check out what disks that’s connected to your system. Be sure you choose USB Device. Example: If computer have two hard disks and one USB device currently in use, it could look like this:

(hd0) (105509M)
(hd1) (140681M)
(hd2) (486M) <Obviously this is my USB device in this case
(fd0)

Explanation:
(hd0) (105509M) This is my hard disk number one (partitions doesn’t matter)
(hd1) (140681M) This is my hard disk number two
(hd2) (486M) This is my USB device currently in use (512 MB USB stick)
(fd0) This is my floppy unit (if you don’t have floppy it might not show up)

Okay you of course choose “(hd2) (486M)” and then in bottom of window you press “Install” a dos window shows up telling you (hopefully) that everything went right. Press Enter to close dos window. Quit “Grub4Dos installer”. You now have a USB device bootable to Grb4 Dos.
ATTENTION: Never touch your harddisk (hd0) or (hd1) etcetera. If you insert grub MBR to harddisk (hd0) your system won’t boot and you have to run: “fixmbr\device\harddisk0” from windows repair consol. Windows cannot start with grub MBR (MBR= MasterBootRecord). You can use a grubloader on the rot of first hard disk, and then start windows from that stage, but we are not interested of those issues at this point.
Note: I take no responsibility for people that mix this up.
--------------------------
Step 3. Open “grub4dos-0.4.4-2008-08-08” folder (you can rename folder to a shorter name).
Copy this three files: “grldr”, default and “menu.lst” to USB device. You now have a USB device that starts to Grub4Dos, but we need to do some editing to file “menu.lst”. You can open this file with a simple texteditor (Notepad works fine). Open “menu.lst”. on USB device, delete all text and insert this instead:

color blue/cyan yellow/cyan
timeout 6
default /default

title Boot from Hardisk (Start Windows)
root (hd0,0)
chainloader (hd0,0)/ntldr

title Start EasyBoot
find --set-root --ignore-floppies /iso/mycd.iso
map /iso/mycd.iso (hd32)
map --hook
chainloader (hd32)
boot

Close and save changes made to this file.
--------------------------
Step 4. We need a couple of more files. Make “hided files and folders” visible in windows. From root on [C:] copy “Ntdetect.com” and “ntldr” to your USB device.
Again start Notepad and insert this text:

[Boot Loader]
Timeout=10
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Start Windows from hd 0 part 1" /FASTDETECT

Save this text file to USB device with the name: boot.ini (Note extension ini)
--------------------------
Step 5. Create a folder with the name iso on USB device. Copy iso-file from EasyBoot (mycd.iso) into this “iso”- folder” on USB device (this take some time).

Congratulations you are finished!

Reboot your computer and set BIOS to boot from USB device. You get two choices: Boot to Windows or start EasyBoot. I guess you choose EasyBoot :laugh:

Enjoy

Regards from heureka

Posted by abubin on Sep. 11 2008,01:07

i tried this but doesn't work. I didn't use bootcd's iso. Instead, I tried using hiren.iso to test first.

During bootup, I get error saying "find --set-root --ignore-floppies /iso/myiso.iso" file not found.

BTW, can grub open iso files automatically? Cause I don't see any use of tools to open iso and read the boot information inside..so I am not sure if this tutorial is correct.

Any, I will try again following this with easyboot iso.

Posted by Guest on Sep. 11 2008,02:57

To abubin

Hi abubin! Are you really sure that you have put ”mycd.iso” file on USB device and placed this in a folder named iso

Like this:

Iso/mycd.iso

Note: Name on EasyBoot iso must be “mycd.iso” (no quotes). I have tested this on several USB bootable computers and have no problem. I have also already pointed out that there might be a problem with some computers BIOS’s.

Seems that name on your iso (created by EasyBoot) is ”myiso.iso” correct? If so change name on iso to mycd.iso to fit path.
I currently use: “find --set-root --ignore-floppies /iso/mycd.iso” in my path.
Or use name “myiso.iso”, but then you must change path in your “menu.lst” to this instead: “find --set-root --ignore-floppies /iso/myiso.iso” no quotes! You may call iso file whatever you want, like: abubin.iso and then change path in “menu.lst” : “find --set-root --ignore-floppies /iso/abubin.iso”.
Please note: path in next line in “menu.lst”: “map /iso/mycd.iso (hd32)” must be changed to right path as well. It’s like that old DOS (Disk-Operative-System)-times. Always be sure to have right path in text files.

Some information about my tests:

Computer 1:
BIOS= Phoenix BIOS v.661M04MX (Intel single core)
CPU= 2.8 Ghz
RAM= 767 Mb (should be 768 Mb but some problem with memory bank)
Motherboard= FOXCONN (cheap one but works)

Computer 2 (high performance):
BIOS= AMI BIOS v.0705
CPU= 3.4 Ghz (Intel double core)
RAM= 2 Gb
Motherboard= P5LD2 Deluxe (excellent Motherboard with high performance USB-speed)

Computer 2 loads an iso file with size 400 Mb into memory in less than 45 sec. Computer 1 (Foxconn) take more than 15 minutes to finish.
Talk about differences

As you can se, I have two different BIOS, s and two different computers (but Intel in both, shouldn’t make any difference).

In fact I have tested this on my harddisk. My boot.ini file (hided on C:) has now an extra boot option. Instead of normal start:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

My boot.ini now looks like this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
C:\GRLDR="Start GRUB"

As you can notice I have put in C:\GRLDR="Start GRUB"
And to make Easyboot run I have put a copy mycd.iso and a copy of grub loader grldr and a copy of my menu.lst on C: And finally edited menu.lst to have this text:

timeout 0

title Start EasyBoot
find --set-root --ignore-floppies /mycd.iso
map /mycd.iso (hd32)
map --hook
chainloader (hd32)
boot

I can now choose to start EasyBoot or start Windows :laugh:

Have to edit post (forgot to answer your question: “BTW, can grub open iso files automatically?”) Straight answer is: YES

I’m amazed that it doesn’t work out for you.
What kind of USB device did you use for this test (just by curiosity).

Regards heureka

Posted by abubin on Sep. 12 2008,00:58

yes, my iso is called myiso.iso and I already changed it in menu.lst as well. So, it shouldn't be due to that.

BTW, what does chainloader (hd32) means?

I will trying now following this guide exactly.

Now error is different :

(hd0,0)
map /iso/mycd.iso (hd32)

Error 60: File for drive emulation must be in one contiguous disk area

Press any key to continue ...

Any idea?

When I check the usb drive, using defrag, I can see the iso file is in fragmented into 2 part. But how do I make sure it's one part? I just copied them over. Don't know why the copy is splitting the file into 2 fragments.

I can't proceed to defrag cause windows will report an error. Probably cause it's usb drive. I tried to delete the file and copy again but this time it's fragmented into 3 parts. How to copy it to make sure the file does not get fragmented?

Posted by Guest on Sep. 12 2008,03:08

To abubin

Hello again abubin. I wrote in my first topic quote: “You must (or recommends) use NTFS as file system on USB device - otherwise it’s common to get this:
“Error60: File for drive emulation must be in one contiguous disk area”. Make sure you used NTFS. I had the same problem (my blood pressure for sure raised for a while :angry:

).

Read this:
“I have managed to start EasyBoot from USB-device. Tested this on 3 different USB-sticks. One 4 Gb, one 512 Mb in size, and finally tested on my Digital Camera-Sony memory stick-512 Mb (using separate multi-memory/sim card reader stuck in to USB connector).

And this: There is still no 100% standard using USB devices. On some motherboards it works and in some not. It’s a mess out there with different motherboards and different bios. You need a computer that support booting from USB.”. This last is not the issue in your case. It’s something with your USB device (I can se you already figured it out what causes problem, read next lines and se if it can be solved).

This error could also be a problem when using to small USB device comparing to size of EasyBoot file.
I recommend not using more than proximally 25-30 % of USB device/disk area, and absolutely not over 30 %.
In fact, I recommend test EasyBoot file with only 10 % of USB capacity, just to check that it runs.

Quote: “How to copy it to make sure the file does not get fragmented?” It could be an issue how you formatted device. Always use my designed batch file together with Hpusbf.exe. Note: Hpusbf.exe and batch file must be together in same folder. It doesn’t matter where or what name on folder you use.

Finally, make a EasyBoot file that’s really small, a basic one for test purpose. That should do it.
To make it easier, do not use any large images in ezboot folder, because later on we will not start (run) large images from that folder.
And do not insert any files into EasyBoot/disk1 folder as well, because we will not be using them from that repository anyway. I’ll explain later when you are up and running EasyBoot from USB device.

(hd32) issue. Well I’m not any expert to this but I think it’s related to a command to use iso file as a kind of harddisk/cd-rom, but as I pointed out, I am no expert, only user

regards heureka

Posted by abubin on Sep. 12 2008,03:59

yes, I am sure it is NTFS cause I formatted using -FS:NTFS command.

BTW, after a lot of formatting and recopy the file, i used a defragger to look at the USB thumbdrive's file mapping.

After formatting using hp format tools, in the middle of the drive, I can see a strip of data there. That's why the 700mb file cannot copy into there as one complete file without fragment.

Posted by Guest on Sep. 12 2008,05:47

To abubin

It happens to me

I get “File for drive emulation must be in one contiguous disk area”. When this happens, I use this trick to get USB device geometry on the right track. In Windows choose to format your USB device (right click on device in explorer) and format USB device (you can use fat or fat32, if it is a big USB device you probably only can use FAT-32, it doesn’t matter what file system you use, just do it!).

When finished, start downloaded HP GUI-tool (Hpusbfw.exe) and from this again format USB device with file system FAT. Now use my batch file to run final format (in tutorial). Finally follow guidelines in tutorial (except format that’s already done) to get EasyBoot file (mycd.iso or whatever) on to USB device together with grub (grldr) and “menu.lst” as well and rest of necessary files.

Important: Do NOT pull out your USB device without using (“Safe remove USB….) in Windows. If you pull out USB device while system still have contact (and “chatting” to USB) parts of file structure or even parts of geometry in USB device may be partly destroyed and you have to start all over again.

Please read this: "Make a EasyBoot file that’s really small, a basic one for test purpose. That should do it.
To make it easier, do not use any large images in ezboot folder, because later on we will not start (run) large images from that folder.
And do not insert any files into EasyBoot/disk1 folder as well, because we will not be using them from that repository anyway. I’ll explain later when you are up and running EasyBoot from USB device".

Regards heureka

Posted by abubin on Sep. 12 2008,06:35

arh...doesn't work. I tried formatting fat, fat32 then ntfs but still same. The tried low level format it but still same. Ahh..this is annoying, spend the whole day trying to do this.

Posted by Guest on Sep. 12 2008,07:08

To abubin

It’s something wrong with your USB device. It’s not related to my tutorial.

Final test is to create a very small EasyBoot file. You should easily get down to less than 3 Mb in size. In this way you may have luck to inject file on to one “contiguous disk area”, due to the fact, that parts of your device seems not to have a “contiguous disk area”

.

Or bye a little cheap one. I can easily get 2Gb from a store for about less than 10 Euro.

regards heureka

Posted by abubin on Sep. 12 2008,11:16

yeah..nothing much can be done. I even tried another USB thumbdrive and same problem. So, I am not even sure which thumbdrive to buy now.

Posted by Guest on Sep. 12 2008,12:33

To abubin

What can I say

As I pointed out earlier, it has nothing to do with EasyBoot.iso, file it’s something with your USB thumb drives. Sorry, can’t do much to help you

You can read that I have tested this with 3 different USB thumbs, even using a digital camera memory stick “Sony-512 Mb” stuck into separate multi-memory/sim card reader (it’s a bit slow but works). And these 3 usb devices tested on two different computers (one “cheap” and one “power computer” with success)

Is there anybody else out here on this forum that has tested this with success? Or not?
Any comments welcome :;):

Regards heureka

Posted by Pepino on Sep. 26 2008,14:40

Hello friends!
in

find --set-root --ignore-floppies /iso/mycd.iso
map /iso/mycd.iso (hd32)

Can i replace the *.iso for *.img boot file with DOS 6.22 version?
Or how it is possible?
thanks guys.

Posted by Guest on Oct. 02 2008,13:50

To Pepino

Sorry for delay been travelling...

Quote: ” Can i replace the *.iso for *.img boot file with DOS 6.22 version?”

Yes but you need to make some changes. Grub load image to memory and then boot image from there.
Grub command for images (*.ima or *.img) looks like this:

title Start DOS 6.22
map --mem /IMAGES/dos.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

Note: image ‘dos.ima’ is put in a folder ‘IMAGES’ to have a clean structure on usb device. And its possible to use compressed images (gz compress) like this:

title Start DOS 6.22
map --mem /IMAGES/dos.ima.gz (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

But what’s the point? You can use such an image in EasyBoot as usual ‘run dos.ima’ (same procedure as CD/DVD-loading). Note: you can’t locate NTFS-partitions (not without special arrangements) from dos and if your usb device is formatted NTFS you can’t even locate usb device. It’s not much you can do from here?!

Regards heureka

Posted by Pepino on Oct. 06 2008,13:11

thank heureka!!
thank for Your Information.. my proyect is run an MSDOS command like fdisk and format before run Easy boot CD image...
but when i run easy boot, its get an error like:
(hd0,0)
map /iso/mycd.iso (hd32)

Error 60: File for drive emulation must be in one contiguous disk area..
any idea for fix this error.??
Sorry for my english.. I'm from Argetina.
Saludos

Posted by Medox on Oct. 17 2008,15:39

(Pepino @ Oct. 06 2008,20:11)

QUOTE

Error 60: File for drive emulation must be in one contiguous disk area..
any idea for fix this error.??
Sorry for my english.. I'm from Argetina.
Saludos

Here is the solution: < http://diddy.boot-land.net/grub4dos/files/map.htm#hd32 >

QUOTE

There are two distinct types of mapping, direct and memory. Direct mapping is generally used for larger images/devices. If using direct mapping to create a virtual device from a disk image, then the image file must be contiguous (not fragmented). Either of the following programs can be used to defragment a file that is contiguous - < contig > or < wincontig >. Attempting to directly map a non-contiguous file will result in Error 60: File for drive emulation must be in one contiguous disk area , in which case memory mapping or defragmenting the file, and then retrying, should be attempted.

I tried wincontig, selected the iso involved and after the defragment it worked perfectly

If you're iso is small you can map it in memory so you don't need to defrag it, using "--mem" after map... like here: (the same for iso's)

QUOTE

E.g. instead of -

* map (hd0,0)/win98.ima (fd0) [enter]
* map --hook [enter]
* root (fd0) [enter]
* chainloader (fd0)+1 [enter]
* boot [enter]

use,

* map --mem (hd0,0)/win98.ima (fd0) [enter]
* map --hook [enter]
* root (fd0) [enter]
* chainloader (fd0)+1 [enter]
* boot [enter]

good luck.

Posted by Pepino on Oct. 20 2008,19:57

Thanks Medox!
I'll try that.
Salutes.

Posted by kush_h20 on Jan. 17 2009,10:12

I am able to Boot EasyBoot Menu from USB Drive.. Thanks .!!

I am able to Boot PQ Partition Manager... from the USB

I am not able to boot WinXP Pro Installation, ERD Commander 2005 from the USB

but WinXP and ERD Boot from CD

Posted by balder on Jan. 17 2009,11:49

@ kush_h20

Note: Running Easyboot from USB device and start setup of winxp or start reatogo/bartpe isn’t done in the same way as when using CD/DVD. Read here: < http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=1;t=2480 >

balder

Posted by allencltnc on Jun. 02 2009,13:56

I just have to say that I followed the initial instructions here and it worked beautifully!!

Thanks!!

Posted by iphoneu on Jul. 12 2009,13:44

It Didn't work for me
There is sure bug inthe guide
I don't think grub opens iso directly

Posted by iphoneu on Jul. 12 2009,14:19

I am Sorry for my above comments.
after defragmenting the iso file it worked fine for me.

Only thing is I am getting blue screen with windows-live. And same windows-live boots perfectly from cd.

Any guide lines?

Posted by logajith on Oct. 08 2009,03:35

Dear ,

Is it possible to put 2 iso images in that usb boot.booting time total 3 lines like ,
boot from hdd ,
eazyboot iso1,
eazyboot iso 2
Awaiting your reply.
Thank you

Posted by balder on Oct. 08 2009,04:28

@logajith

Yes it is.

But you have to manually edit text file menu.lst on USB device followed by manually copy your second or third etcetera ISO-file to USB device.

Note: you can use any text editor to edit text file menu.lst - notepad works fine.

---------------------------------------------------------
Let’s say you have a folder ISO on USB device and in this folder ISO you have one ISO-file (ISO created by EasyBoot) with name iso.iso. Then text file menu.lst might looks like this:

timeout 0

find --set-root --ignore-floppies /iso/iso.iso
map /iso/iso.iso (hd32)
map --hook
chainloader (hd32)
boot

You can create a different ISO in Easyboot and rename this created ISO to whatever you like. Let’s name it easy.iso you then copy this “easy.iso”-file to folder ISO on USB device and insert this text lines in menu.lst:

timeout 10

title run iso file
find --set-root --ignore-floppies /iso/iso.iso
map /iso/iso.iso (hd32)
map --hook
chainloader (hd32)
boot

title run easy file
find --set-root --ignore-floppies /iso/easy.iso
map /iso/easy.iso (hd32)
map --hook
chainloader (hd32)
boot

As you can see I put in timeout 10 seconds and a title for each easyboot ISO-file and that it's

@logajith

I was thinking

Why loading a second different iso? You can create submenu (plenty of different submenus) this is nearly the same as start a different iso file created by easyboot.

EasyBoot is so versatile and powerful

You can jump between submenus and jump back to “main menu”. In my opinion this is a far more efficient and reliable solution than loading different iso files :;):

balder

Posted by logajith on Oct. 11 2009,08:19

Dear balder,

Thanks your reply.Also one more thing i want to know that,
i have a Win7 iso that is created by eazyboot.I make same way usb boot that's inside the win7 iso. Once the installation starting, its asking the "cd/dvd driver file reqiured" error. it cannot be installed.In the same iso i write to a dvd and installed that's working fine.

Can you solve the issue.
Thank you

Posted by balder on Oct. 11 2009,13:11

@logajith

Quote: ” I make same way usb boot that's inside the win7 iso”

It’s a huge difference installing any Windows system XP or vista or Win7 from USB comparing installing from CD/DVD

To use EasyBoot (and it’s nice interface with backgrounds and “buttons”\text) you need to create “kicker-images”. Easy way to create this “kicker-images” is to use my “easyboot-kicker-image.script” (downloadable from my website)

You need an out of the box program to create environment on USB device that can handle setup from USB device. Download from < here >
This program does what you are asking for :;):

I recommend using my script “easyboot-usb.script” as first step (format etcetera).

Then run WinSetupFromUSB_0-2-3.exe
Note: you have to install/run WinSetupFromUSB_0-2-3.exe (in reality extracting to a folder WinSetupFromUSB_0-2-3.exe).
You can add WinXP (several different ones), add vista, add win7, add bartpe etcetera and when you nearly have filled up you usb device creating “kicker-images” for each setup and use this “kicker-images” as “start-images” in EasyBoot and finally create your EasyBoot-iso and copy iso (overwriting if already exist) to folder iso on usb device.
Note: you may need to run defrag to usb device in case easyboot-iso file is copied to fragmented areas on usb device (as this is the last thing in this process to be done).

When you later on better understand how and what you want on usb device you can create your final easyboot iso file with necessary kicker-images in place and run my “easyboot-usb.script” and as second step putting your decided win-systems to usb device (using WinSetupFromUSB_0-2-3.exe).
You have to read\learn how this different grub menu.lst is working and use this different text according to what system to start setup to and copy this text to your created different kicker-images used in easyboot.

Take your time and watch/learning/experiment=have fun
He, he that last one “have fun” is in my opinion the best part

Regards balder

Posted by logajith on Oct. 13 2009,09:24

Dear Balder ,
Thanks for your answer but thats not clarity can u give me step by step instructions.
Thank you

Posted by balder on Oct. 13 2009,12:21

@logajith

Quote: ” can u give me step by step instructions”
Well I do not consider me an expert on writing tutorials but I will try to do my very best

How to create setup environment from USB device with WinXP (sp2 or sp3) as target. Step by step procedure down here

1. Download and install WinSetupFromUSB_0-2-3.exe from < here >
2. (you can as option jump to “Optional” down below and then go back and continue from here) Go to my website and download “Startkit”. Run EasyBoot-USB-script (format etcetera and put for fun in some created iso from easyboot)
3. Run WinSetupFromUSB_0-2-3.exe from inside folder WinSetupFromUSB. Only scroll to setup folder WinXP (folder i386) and choose this as target. Do not set or change anything else in this window. Don’t change to ntfs don’t format just press GO button.

When WinSetupFromUSB_0-2-3.exe is finished (you have to in the end of this procedure accept license agreements). Then take a look to text file winsetup.lst on USB device. You find this text: title First part of Windows XP Professional setup
root (hd0,0)
chainloader (hd0,0)/$WIN_NT$.~BT/SETUPLDR.BIN
savedefault 1

This text lines has been added by WinSetupFromUSB_0-2-3.exe and for each system you put on USB device new text lines is inserted. It’s this text lines that is used in my “kicker-images”

Optional:
Download from my website easyboot-kicker-image.zip (extract and put it in folder easyboot in winbuilder.
Start easyboot-kicker-image-script and inject this line by line (delete existing lines)

root (hd0,0)
chainloader (hd0,0)/$WIN_NT$.~BT/SETUPLDR.BIN
savedefault 1

Create grub image (check g-zip as well) and save compressed image in easyboo\disk1\ezboot with the name setupxp do not set extension because this is done automatically by script.

In easyboot create menu “Setup WinXP from USB” and use command: memdisk setupxp.img.gz

This is our first “kicker-image” to start setup winxp from usb.
Create ISO in easyboot and use this ISO in step 2 above.
Note1: If you find this difficult you can download already created image from < here > extract file and copy g-zip compressed image to easyboot\disk1\ezboot and use command: memdisk setupxp.img.gz ). You can later change text file meny.lst inside this kicker-image to start other setup.
Note2: you can also extract image and use it as a “normal” floppy image (size 1,44 Mb with run ***.img in easyboot) to easily extract menu.lst and do changes and then inject edited menu.lst and finally save image with a new name equivalent to what image is starting/launching etcetera.

That’s all. You have to notice changes in text file winsetup.lst and in menu.lst on usb device for each system you put on usb device (using WinSetupFromUSB_0-2-3.exe). Basically what we do is to copy behaviour of this text files (winsetup.lst and menu.lst) but instead force this text commandos from different kicker-images launched by easyboot.

If you decide to also create setup of vista (the same if you use vistape) from usb then put this text in menu.lst in kicker-image and save image as vista (or something):

root (hd0,0)
chainloader /bootmgr

When running setup of winxp (or whatever) from USB device you first run text mode setup as usual in windows setup program. When files been copied (witch goes a lot of faster than from CD/DVD) computer reboots and installation continues. Computer boots to hard disk with setup files and now runs graphic setup part as usual. This is already fixed when you run my script easyboot-usb script.

Regards balder

Posted by logajith on Oct. 14 2009,02:18

Dear Balder,
I know you are very good teacher and very good knowledge.
Thanks for your reply.Thank you very much .i hope u know what iam facing issue now-usb booting with eazyboot iso(win7)--showing dvr/cd drivers required error .i want to solve this issue.You are tutorial here is for win xp. I need to solve the win7 usb installation dvd/cd driver required error only.Not too much from you.

Thanks & Regards

Posted by balder on Oct. 14 2009,04:34

@logajith

Quote: “now-usb booting with eazyboot iso(win7)--showing dvr/cd”

I need some clarifications here

1. Are you setting up win7 from internal connected CD/DVD (IDE-interface)?
2. Are you setting up win7 from external usb connected CD/DVD?
3. Are you trying to use ISO (created by EasyBoot) and trying to run this from USB device (USB stick/thumbdrive) in the same way as ISO normally is used on CD/DVD?

Please clarify for better understanding

Regards balder

Posted by logajith on Oct. 15 2009,07:24

Dear Balder

i am trying to use an ISO (created by EasyBoot) to run from a USB device (USB stick/thumb drive).That time usb booting is perfectly working.Easy boot menus(DOS,RESTART,BOOT HDD, WINXP Installation,WINDOWS7 INSTALLATION-these are the menus in easyboot iso) also i can see but the problem is i try to install the particuler windows7 that time showing the "cd/dvd driver file reqiured".error happening.
In the same iso i write to one dvd its working perfectly.Why this happen -in usb booting and installing a iso need some additional driver files.
Please help me.
Thanks

Posted by balder on Oct. 15 2009,07:46

@logajith

Please read Post Number: 25 and especially Post Number: 27 in this topic. You cannot use ISO created by easyboot and launched from USB device in the same way as launched from CD/DVD.

I repeat, it’s a huge difference using ISO from USB device comparing to use ISO from CD/DVD.

Note: you can – as example - launch floppy images as usual (ghost/acronis images and hiren can be launched from ISO on USB device as usual). In fact most parts in ISO (created by easyboot) can be used in a “normal” way

The big difference is when launching setup to windows system (winXP/win-server2003 or vista or win7 as example). You must use references in Post Number: 25 and Post Number: 27 in this topic to achieve this.

Regards balder

Posted by logajith on Oct. 18 2009,04:37

dear balder,
Thank you verymuch, now i understand .ok any way is it possible to create a usb boot flashdrive including 1,active password changer, 2,live xp, 3,epm partition editor 4,install windows xp sp3, 5,install windows 7.If you know this please let me know.
Note:is the password changer support win7 and vista in dos boot ?.
is the epm partition editor support directly resize the partitions in win7,vista,xp in dos boot

Thanks & regards.

Posted by balder on Oct. 18 2009,05:47

@logajith

Quote: ” create a usb boot flash drive including 1,active password changer, 2,live xp, 3,epm partition editor 4,install windows xp sp3, 5,install windows 7”

I do not have active password changer or epm partition editor 4 to test

- but if you can create any kind of bootable floppy image in these programs - you can surely use these floppy images as usual in EasyBoot. I know that epm partition editor has option to create bootable floppy image. You can use this as I pointed out as usual in EasyBoot. Create floppy image and give it a nice name (epm-4 or whatever) put floppy image in folder ezboot and use command in EasyBoot as usual: run epm-4.img or if it is a ima-file run epm-4.ima
I guess that you most likely can use the same approach to active password changer. Create image and use it as above described in EasyBoot.
Note: To get created EasyBoot-ISO on USB device and make this bootable you already know

(use my script/startkit from my webb site)

Including setup for windows xp sp3 and windows 7 from USB is fully possible (as described in post 25 and post 27).
Note: I do not have win-7 in my arsenal but it has already been reported to be working from USB. I have personally tested winxp-sp3 and this works 100%

Regards balder

Posted by alian on Nov. 01 2009,17:53

(abubin @ Sep. 11 2008,06:07)

QUOTE

Hard disk to start reporting missing mycd.iso as follows:

Error 60: File for drive emulation must be in on contiguous disk area
Press any key to continue..

How can I please resolve the Error?

Posted by balder on Nov. 02 2009,01:59

@alian

Click with right mouse button on harddisk (USB connected harddisk I assume?) and choose properties\tools\ and run defrag to this harddisk.

@alian Did you use my script (”startkit”) to get this harddisk to run easyboot when booting computer? If you did this error shouldn’t show up (just curios why it shows up)

balder

Posted by alian on Nov. 02 2009,16:13

@balder

My boot main menu of hard disk looks like:

QUOTE

color green/cyan yellow/cyan
timeout 4

title 1. Start Repair and Recovery CD1 from easy boot
find --set-root --ignore-floppies /boot/mycd.iso
map /boot/mycd.iso (hd32)
map --hook
chainloader (hd32)

title 2. Start Repair and Recovery CD2 from easy boot
find --set-root --ignore-floppies /boot/mycd2.iso
map /boot/mycd2.iso (hd32)
map --hook
chainloader (hd32)

title 3. Start Hiren CD
find --set-root --ignore-floppies /boot/hieren.iso
map /boot/hieren.iso (hd32)
map --hook
chainloader (hd32)
boot

-Menu 2 and 3 no problem!
-Error on boot menu 1 is as below:

QUOTE

(hd0,0)
map /boot/mycd.iso (hd32)

Error 60: File for drive emulation must be in on contiguous disk area
Press any key to continue..

Who do I make a button press, then returns to the main menu.

Posted by balder on Nov. 03 2009,01:26

@alian

Quote: ” returns to the main menu” To return to main menu is possible from sub menu and from launched floppy image (DOS image). To return to main menu is easy.
Let’s say your main menu has name “Default.ezb” and your sub menu is “format.ezb” you then set “run Default.ezb” this redirect you back to main menu “Default.ezb”.
Note: you can jump around as you wish. It’s possible to jump from one sub menu to another sub menu and back to main menu as you like.

Another example: How to return back to Easyboot menu from floppy image you are running.
Attention! This works primarily only for DOS floppy images:

1. Open floppy image (I use UltraISO) and inject ezboot.com (you have ezboot.com in EasyBoot\resource).
2. Start EasyBoot, click on 'Options' button and choose 'Configuration' from the popup menu. Then check 'Enable coming back from DOS' and click 'OK'.
3. As this is a DOS floppy image you have a batch file with name autoexec.bat you can put in text ezboot.com to automatically return to EasyBoot menu.
Example from my ghost floppy image below here:
mouse.com
mouseusb.exe
ghost.exe –auto
ezboot.com

When I finish ghost.exe ezboot.com force DOS to jump back to EasyBoot menu.
-------------------------------------

About “Error 60: File for drive emulation must be in on contiguous disk area”
This still means that ISO-file is in pieces (fragmented) and grub cannot load such a file. I noticed that you have this part of grub command in charge:

(hd0,0)
map /boot/mycd.iso (hd32)

Conclusion is that you are loading ISO file from USB drive and that this ISO-file has been copied to USB drive but is in a fragmented shape on USB drive/device. You have two options here to solve this issue:
1. Run defrag to USB drive (this is a fast and painless procedure and doesn’t harm your USB drive). Read post 35 how to run defrag to USB drive.
2. Download my USB.script (download “startkit”) Use my script to make ISO run from USB drive/device. Scroll down to “Welcome to my website” – you find it there. Note: when using my script everything on USB drive is wiped out (format must be run to ensure you don’t get “Error 60: File for drive emulation must be in on contiguous disk area”.

balder

Posted by alian on Nov. 04 2009,11:46

With your Starter Kit Error 60 is no more.
Thanks for best support.

Posted by balder on Nov. 04 2009,11:57

@alian

Quote: ” Thanks for best support.”

Well I must say “you made my day” – thanks for nice feedback

Regards balder