Forum: EasyBoot
Topic: Run BartPE by EasyBoot menu
started by: martinx

Posted by martinx on Dec. 23 2003,22:00
When a bootable ISO (for example 'bartpe.iso')is created by PEBuilder, you can add it to EasyBoot menu this way:

1) Open 'bartpe.iso' by UltraISO, extract all files and folders to c:\easyboot\disk1 . You can see information as following:

 c:\easyboot\disk1
                      |--ezboot
                      |--I386
                      |--PROGRAMS
                      |--AUTORUN.INF
                      |--BOOTFONT.BIN
                      |-- ...

2) Use 'Boot->Save Boot File' from UltraISO main menu,  and save it as 'c:\easyboot\disk1\ezboot\bartpe.bif'

3) Set 'run bartpe.bif' as command line to coresponding menu item

Note: Use V4.55b (Build 296) or above to avoid problem with long filenames used by Bart PE.
Posted by wn on Dec. 26 2003,12:19
I have tried the same concept with trinity-recue disk (< homepage >), but failed to get it working. The ISO is booting linux. Any suggestions would be welcomed.

Thank you for a great program and everyone who help on this forum.
Posted by Tommy WS on Jan. 01 2004,01:44
Some program under BartPE can't work properly, maybe martinx can try total commander, wordpad, under bartpe.
These program can not work properly.

Thanx
Posted by martinx on Jan. 01 2004,09:26
Please use V4.55 build 296 to resolve this kind of problem.

See more information < Here >
Posted by fvklaver44 on Jan. 02 2004,13:00
hello,
I have a question regarding the creation of the file: "c:\easyboot\disk1\ezboot\bartpe.bif".
obviously this can be done as suggested by martinx.
but if I already have a good working Bart-PE, can I also create the bif-file by extracting it from the working CD with the program called UltraISO ?
thnks
Fred
Posted by Hannes on Jan. 02 2004,20:01
Sure! That should work fine. In fact, I usually prefer to extract the bootsector myself rather than downloading one. This way I know for sure it matches my CD perfectly.

I guess it's just a matter of preference.

Hannes
Posted by fvklaver44 on Jan. 05 2004,02:23
Well,
If you run EasyBoot, and try to create a bif-file, you don't get a complete image of the existing CD.
The size of the file is much too small.
So, the only way is to go along with the method as suggested by marinx
thkns
Fred
Posted by boombastc on May 30 2004,09:08
I  followed your post to copy in the disk1 folder the files for Winxp and Bart's PE but know i don' t know which file should i use as boot image when i make the final iso.Can you help me?I tried whit loader and cdmenů but when i insert the dvdrw after reboot winxp setup starts not the easyboot menů.
Another thing:the guide for xp pro says:"for Windows XP Professional, copy  win51ip to C:\EasyBoot\disk1" but i've got xpProfessional with SP1,should i copy win51ip or win51ip.sp1?
Posted by boombastc on May 30 2004,11:24
Finally i managed to do the disc removing setup.exe,readme and autoran.inf that i copied from Xp cd to disk1 directory.Now if i boot with this dvd i get the menů but either if i choose setup XP ot Bart's PE always setup XP starts,why?What should i check?
Posted by jnilles on Jul. 22 2004,19:48
When I try BartPE with easyboot I get a bluescreen Process1_Initialization_Failed error after windows logo screen of about 15secs.  BartPE works fine on its own cd.

Recreated BartPE several times. Tried in Virtual PC 2004 and several machines. All same error.

Use EasyBoot 4.56 and 5. Same issue. Followed steps above. No luck.

Any thoughts?
Posted by Tim on Aug. 30 2004,17:59
This is the only way I have made BartPE work with EasyBoot fully.
Even using the newer version still made some programs not work like wordpad. So this is how I do it.

Step 1 - Create BartPE ISO
The first thing you need to do is create a BartPE ISO with all the applications you want. Test the ISO as is before going on. Refer to BartPE guides for details on how to use it.

Step 2 - Extract BartPE Boot Image
Using UltraISO open the BartPE ISO and save the boot image.

Step 3 - Create EasyBoot Files
Use EasyBoot to create you menu(s). When it comes to BartPE use the boot image you saved in step 2.
You should test EasyBoot except for BartPE to make sure all other menu items work as expected.
Once done testing you may delete the ISO that EasyBoot creates as we will not be using it.

Step 4 - Combine EasyBoot and BartPE
Now to combine the two open the BartPE ISO up in UltraISO again.
Add all the files from you EasyBoot directory to the BartPE ISO.
Load loader.bin found in your ezboot directory as the boot image.
Optionally under the file properties you may change it to DVD size and click Optimize
Save the ISO.

That is it. I also remove BartPE's AutoRun.inf and replace with my own autorun.

Hope this helps

Posted by problems copying bartpe files an on Nov. 02 2004,10:16
Hi!

I didi as the forum indicates, extracting all files from the bartpe.iso to c:\easyboot\disk1\ directory. I verifyed and the folfres and files are really there. But When I create the iso, these files are ignored. For example my iso was created having the size of 8MB. this 8 MB are just the others iten of the menu. I tryed several times, but I couldn´t. What is rong? Does anybody know?

Thanks

Posted by xoben on Nov. 03 2004,22:05
Quote
This is the only way I have made BartPE work with EasyBoot fully.
Even using the newer version still made some programs not work like wordpad. So this is how I do it.

Bart PE works. Please make sure that 'Joliet' is not checked when making an ISO image.

Posted by xoben on Nov. 03 2004,22:08
Quote
What is rong? Does anybody know?


Please check the setting of 'CD File Dir'.

Posted by teletom on Nov. 09 2004,20:16
Hello!

I think it is a good idea to make easy multiboot cds or dvds. Thats why i have created a Ezboot pebuilder plugin.

Reasons:
  • fast boot dos > delete, create or resize partitions or repair the mbr fdisk /mbr> reboot to bartpe
  • boot recovery console and repair the ntfs bootsector fixboot
  • fast boot Acronis linux iso > delete, create or resize partitions use partition images > reboot to bartpe
  • use knoppix to work on linux partitions
  • especially on cds the space is small only 700 ~ 800 MB > thats why reduce the menu entrys
  • the menu is clearly arranged
Ezboot Plugin- Download: < http://pebuild-plugins.sourceforge.net/ >
Easyboot- Download: < http://www.ezbsystems.com/easyboot/ >

1. Structure
Code Sample
Mainmenu  cdmenup.ezb

     menu entry                         run command          

[1] Windows PE [by PE-Builder]   run bootsec.bin            
[2] Dos - CD, TCP/IP, Tools...    run BootImage.img        
[3] Recovery Console                run bootcmdc.bin      
[4] Acronis TI, DDS & Knoppix    run cdsubp.ezb        

Submenu  cdsubp.ezb

     menu entry                            run command

[1] Acronis True Image                 bootinfotable;run ti.bif       bif not included to built
[2] Acronis Disk Director Suite        bootinfotable;run dds.bif
[3] Da_mn Small Linux - Knoppix   bootinfotable;run knoppix.bif
[4] Return to Mainmenu                run cdmenup.ezb

"q" to quit          "r" to reboot


2. Install
Start the ezboot.part01.exe and extract the files and folders into the pebuilder plugin folder.
Copy all bootloader bin, bootimage img and Isofiles in bif-format into the plugin\ezboot folder.

ezboot.inf
Quote
[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="[Teletom] Easyboot multiboot cd/dvd v1.3"
Enable=1

[WinntDirectories]
a="ezboot",2
;tools folder
b="BootCD",2
c="BootCD\Vdefs",2
d="BootCD\Wintools",2
e="boot",2
f="lost+found",2
g="KNOPPIX",2
r="\",2

[SourceDisksFiles]
loader.bin=a
cdmenup.ezb=a ; Mainmenu
cdsubp.ezb=a ; Submenu
setup98.img=a,,4
useemu.com=a,,4
useflp.com=a,,4
rawrite.exe=a,,4
reboot.com=a,,4
logo.bmp=a,,4
back.bmp=a,,4

;bootfiles bins, imgs or isos (--> *.bif or *.wbt)
CMDC\bootsect.bin=a
bootimage.img=a,,4
knoppix.bif=a,,4
ti.bif=a,,4
dds.bif=a,,4
index.html=a,,4
fli4l.img=a,,4
tomsrtbt.img=a,,4
index.html=r,,4

[SourceDisksFolders]
;files for Dos BootCD folder
BootCD=b

;files for isolinux Knoppix
boot=e
lost+found=f
KNOPPIX=g

;files for the ezboot folder bins bifs wbts imgs isos
filesezb=a
;files for the root folder \
files=r

[SetValue]
;"..\..\pebuilder.inf", "BuildISO", "exec", """"mkisofs.exe -iso-level 4 -volid """"""BartPE"""""" -A PEBUILDER/MKISOFS -sysid """"""Win32"""""" -b ezboot/loader.bin -no-emul-boot -boot-load-size 4 -hide loader.bin -hide boot.catalog -o """"""@IsoFile@"""""" """"""@OutDir@"""""""&
;
;"..\..\pebuilder.inf", "BuildISO", "exec", """"plugin\ezboot\mkiso.cmd """"""@IsoFile@"""""" """"""@OutDir@"""""""&
;



CMDC\setcmdc.cmd
Quote
REM Copy SETUPLDR.BIN from [setupcd]\i386 folder
REM Copy BOOTSECT.BIN from [setupcd]\ folder
REM use binsub 1.8
if not Exist setupldr.bin goto _err
if not Exist bootsect.bin goto _err
if not Exist setupldr.org copy setupldr.bin setupldr.org
REM === replace i386 and I386 with cmdc ===
binsub setupldr.bin i386 cmdc
binsub setupldr.bin I386 CMDC
if not Exist bootsect.org copy bootsect.bin bootsect.org
copy bootsect.bin bootcmdc.bin /y
REM === replace i386 and I386 with cmdc ===
binsub bootcmdc.bin i386 cmdc
binsub bootcmdc.bin I386 CMDC
goto _end
:_err
echo ERROR Can't find SETUPLDR.BIN or BOOTSECT.BIN !!!
:_end


mkiso.cmd
Quote
@echo off
set xv=bootsect.bin
set xw=bootsect.bin
if not exist %2\ezboot\loader.bin goto _mi
if not exist %2\bootsect.bin goto _mi
copy %2\bootsect.bin %2\ezboot\bootsect.bin /y > nul
set xv=ezboot/loader.bin
set xw=loader.bin
:_mi
echo on
mkisofs.exe -iso-level 4 -r -hide-rr-moved -volid "BartPE" -A PEBUILDER/MKISOFS -sysid "Win32" -b %xv% -no-emul-boot -boot-load-size 4 -hide %xw% -hide boot.catalog -o %1 %2
@echo off
set xv=
set xw=


3. Windows PE
Because the ezboot menu starts in this case the bootsec.bin, you have to do the steps under point 5 - Recovery Console - to create the bootsec.bin file, else ready to use.

4. Dos - CD, TCP/IP, Tools...
Included is an experimental version. It is better to use your own dos-cd:
Put the boot-cd into the cd-drive.
Use and start isobuster, click the Bootable CD folder and extract the bootimage.img file (1440 KB) with overwriting into the plugin\ezboot folder.
Click the BootCD folder and extract BootCD with overwriting into the plugin\ezboot folder.
< http://www.smart-projects.net/isobuster/ >
If jo.sys (boot windows or boot cd?) is included into the bootimage.img use and start winimage, open bootimage.img and delete jo.sys.
< http://www.winimage.com/ >
Excellence usage for this is the Hiren's boot-cd.

5. Recovery Console
Copy SETUPLDR.BIN from [setupcd]\i386 folder and
BOOTSECT.BIN from [setupcd]\ folder into the plugin\ezboot\cmdc folder and run setcmdc.cmd.
Setcmdc.cmd replace i386 with cmdc and create BOOTCMDC.BIN.

6. Acronis True Image and Acronis Disk Director Suite
Put the Acronis True Image-cd into the cd-drive.
Use and start ultraiso < http://www.ezbsystems.com/ultraiso/ >.
Tools > Make CD/DVD Image > Output file name: ti.iso> Make > OK Return >
Click local filename - list and press F5.
Doubleclick to open ti.iso > Bootable > Save Boot File >
Enter name: ti.bif > Save
Move ti.bif into the plugin\ezboot folder.
Put the Acronis Disk Director Suite-cd into the cd-drive and make the same steps but use dds.bif.

7. Da_mn Small Linux - Knoppix
Download the dsl-knoppix-iso (for instance dsl-0.8.3.iso ~50 MB) < http://www.damnsmalllinux.org/ >.
Open the iso with ultraiso.
Bootable > Save Boot File >
Enter name: knoppix.bif > Save it into the plugin\ezboot folder.
Click the boot folder, rightclick and extract to the plugin\ezboot folder with content.
Click the KNOPPIX folder, rightclick and extract to the plugin\ezboot folder with content.

8. Build it
Start pebuilder, make the pebuilder iso and burn the cd or dvd.

:)  Regards Teletom
PS: See also < http://www.911cd.net/forums/index.php?&act=ST&f=21&t=9209 >

cmdc.inf
Quote
; Windows Recovery Console plugin
;

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Recovery Console"
Enable=1

[WinntDirectories]
a="CMDC",2
b="CMDC\SYSTEM32",2
e="ezboot",2

[SourceDisksFiles]
@SourcePath@I386\SETUPREG.HIV=a,,4
@SourcePath@I386\SYSTEM32\SMSS.EXE=b,,4
@SourcePath@I386\TXTSETUP.SIF=a,,4
CMDC\SETUPLDR.BIN=a,,1
CMDC\bootcmdc.bin=e
ntdetect.com=a
kdcom.dl_=a,,2
hal.dl_=a,,2
halaacpi.dl_=a,,2
halacpi.dl_=a,,2
kd1394.dl_=a,,2
halapic.dl_=a,,2
bootvid.dl_=a,,2
KBDTUF.DLL=a
KBDSW.DLL=a
KBDSP.DLL=a
KBDTUQ.DLL=a
KBDSL1.DLL=a
KBDSL.DLL=a
KBDSG.DLL=a
KBDSF.DLL=a
KBDUK.DLL=a
KBDRU.DLL=a
KBDRO.DLL=a
KBDPO.DLL=a
KBDPL1.DLL=a
KBDPL.DLL=a
KBDNO.DLL=a
KBDNE.DLL=a
KBDUR.DLL=a
kbdus.dll=a
KBDUSL.DLL=a
KBDUSR.DLL=a
KBDLV1.DLL=a
KBDLV.DLL=a
KBDLT.DLL=a
KBDLA.DLL=a
KBDIT142.DLL=a
KBDIT.DLL=a
KBDIR.DLL=a
KBDIC.DLL=a
KBDHU1.DLL=a
KBDUSX.DLL=a
KBDYCC.DLL=a
KBDYCL.DLL=a
KBDRU1.DLL=a
KBDHU.DLL=a
KBDHELA3.DLL=a
KBDHELA2.DLL=a
KBDHE319.DLL=a
KBDHE220.DLL=a
KBDHE.DLL=a
KBDGR1.DLL=a
KBDGR.DLL=a
KBDGKL.DLL=a
KBDFR.DLL=a
KBDAL.DLL=a
KBDBE.DLL=a
KBDBLR.DLL=a
KBDBR.DLL=a
KBDBU.DLL=a
KBDCA.DLL=a
KBDFI.DLL=a
KBDCR.DLL=a
KBDCZ.DLL=a
KBDCZ1.DLL=a
KBDDA.DLL=a
KBDDV.DLL=a
KBDES.DLL=a
KBDEST.DLL=a
KBDFC.DLL=a
ntkrnlmp.ex_=a,,2
autofmt.exe=a
autochk.exe=a
vgaoem.fo_=a,,2
biosinfo.inf=a
l_intl.nl_=a,,2
c_1252.nl_=a,,2
c_437.nl_=a,,2
drvmain.sdb=a
hidclass.sy_=a,,2
ftdisk.sy_=a,,2
flpydisk.sy_=a,,2
fdc.sy_=a,,2
fastfat.sy_=a,,2
kbdhid.sy_=a,,2
dpti2o.sy_=a,,2
dmload.sy_=a,,2
dmio.sy_=a,,2
dmboot.sy_=a,,2
disk.sy_=a,,2
dac960nt.sy_=a,,2
dac2w2k.sy_=a,,2
hidparse.sy_=a,,2
hidusb.sy_=a,,2
cpqarray.sy_=a,,2
cmdide.sy_=a,,2
classpnp.sy_=a,,2
cdrom.sy_=a,,2
cdfs.sy_=a,,2
cd20xrnt.sy_=a,,2
cbidf2k.sy_=a,,2
hpn.sy_=a,,2
i2omgmt.sy_=a,,2
i2omp.sy_=a,,2
atapi.sy_=a,,2
asc3550.sy_=a,,2
asc3350p.sy_=a,,2
asc.sy_=a,,2
i8042prt.sy_=a,,2
aliide.sy_=a,,2
aic78xx.sy_=a,,2
aic78u2.sy_=a,,2
aha154x.sy_=a,,2
adpu160m.sy_=a,,2
acpiec.sy_=a,,2
videoprt.sy_=a,,2
lbrtfdc.sy_=a,,2
ini910u.sy_=a,,2
mountmgr.sy_=a,,2
mraid35x.sy_=a,,2
acpi.sy_=a,,2
viaide.sy_=a,,2
intelide.sy_=a,,2
ohci1394.sy_=a,,2
oprghdlr.sy_=a,,2
partmgr.sy_=a,,2
pci.sy_=a,,2
pciide.sy_=a,,2
pciidex.sy_=a,,2
pcmcia.sy_=a,,2
perc2.sy_=a,,2
perc2hib.sy_=a,,2
ql1080.sy_=a,,2
ql10wnt.sy_=a,,2
ql12160.sy_=a,,2
ql1240.sy_=a,,2
ql1280.sy_=a,,2
ramdisk.sy_=a,,2
sbp2port.sy_=a,,2
scsiport.sy_=a,,2
serenum.sy_=a,,2
serial.sy_=a,,2
setupdd.sy_=a,,2
abp480n5.sy_=a,,2
isapnp.sy_=a,,2
sfloppy.sy_=a,,2
sparrow.sy_=a,,2
amsint.sy_=a,,2
spddlang.sy_=a,,2
symc810.sy_=a,,2
symc8xx.sy_=a,,2
sym_hi.sy_=a,,2
sym_u3.sy_=a,,2
1394bus.sy_=a,,2
tffsport.sy_=a,,2
toside.sy_=a,,2
kbdclass.sy_=a,,2
ultra.sy_=a,,2
usbccgp.sy_=a,,2
usbd.sy_=a,,2
usbehci.sy_=a,,2
usbhub.sy_=a,,2
usbohci.sy_=a,,2
usbport.sy_=a,,2
usbstor.sy_=a,,2
usbuhci.sy_=a,,2
vga.sy_=a,,2
wmilib.sy_=a,,2
ksecdd.sys=a
ntfs.sys=a
spcmdcon.sys=a
ntdll.dll=b
; maybe to change here 850
vga850.fo_=a,,4
c_850.nl_=a,,4



Posted by xoben on Nov. 09 2004,20:39
Thanks teletom for your great idea.
Posted by Haja68 on Mar. 15 2005,15:32
I have no GO menu in Bart PE.
AIO-DVD with Bart PE it runs till the desktop from Bart PE.
Then i see no Go Menu.
Can someone help me.
Posted by uphoff on May 19 2005,14:47
Quote (xoben @ Nov. 04 2004,03:05)
Please make sure that 'Joliet' is not checked when making an ISO image.

Xoben,

You are right, only if Joliet isn't checked all the apps in BartPe will run just fine. But if it isn't checked I get errors in the other bootmenu's for WinXP (pro, home) setup:  "Error in line 1 of TXTSETUP.SIF".
Only if I choose "Joliet" Both XP installations run fine, but... programs in BartPe won't run..

Catch22,

Any clue's??

Michel
Posted by Bruce Lee on May 19 2005,15:52
I have also a question ? If I have 2 "BartPE", for sample :

1/ "Personal BartPE"
2/ "UBCD4WIN 2.5 BartPE"

What I have to do ?

For solving the problem of long name, I have another solution with "UltraIso 7.5.0.956". I load the ".Iso" and with File --> Property, you have the possibility to put "Joliet" with Standard (64) or Extend (110). Then you save the new ".Iso". I soved this problem by fixing  "Kaella-Knoppix Linux" which don't launch and now it work fine.
Posted by Bruce Lee on May 19 2005,16:07
Hi Teletom,

I use your Plugin and you remember that I have a problem for insert "Dam Small Linux", when I was in contact with you one month ago. With my description by using "UltraIso 7.5.0.956", I have solved the problem for "Kaella-Knoppix" and I think that it also work with "DSL" or "Flonix" or others. If you could change this line for insert "Joliet" in your Plugin :

*************************************************
[SetValue]
;"..\..\pebuilder.inf", "BuildISO", "exec", """"mkisofs.exe -J -iso-level 4 -volid """"""BartPE"""""" -A PEBUILDER/MKISOFS -sysid """"""Win32"""""" -b ezboot/loader.bin -no-emul-boot -boot-load-size 4 -hide loader.bin -hide boot.catalog -o """"""@IsoFile@"""""" """"""@OutDir@"""""""&quo
t;
;"..\..\pebuilder.inf", "BuildISO", "exec", """"plugin\ezboot\mkiso.cmd """"""@IsoFile@"""""" """"""@OutDir@"""""""&quo
t;

************************************************

I am very happy !!! Because this Plugin work very fine !!!
Posted by teletom on Aug. 19 2005,07:32
Hello!

I have updated the ezboot plugin to version 1.3.
Download the ezboot plugin:
< http://pebuild-plugins.sourceforge.net/ >
You may download
ezbootv13.exe 8,35 MB and
ezboot13_.exe 1,06 MB without "BootCD" folder archives.

ezboot plugin on 911cd.net:
< http://www.911cd.net/forums/index.php?showtopic=9209 >

recommended is also the using of the !profkit plugin.
!profkit makes EZBOOT uppercase and -r -hide-rr-moved parameters
< http://www.911cd.net/forums/index.php?showtopic=9424 >

Please use also the nu2shel1 tool to set the primary shell and sort plugin folders
< http://www.911cd.net/forums/index.php?showtopic=10642 >
IMPORTANT: please do not use the nu2shell.exe by pebuilder v3.1.4(Beta)
nu2shell.exe by pebuilder v3.1.3 also works fine under v3.1.4!!!

Think it is good to appear the bootevent:

1. PowerOn Self test P.O.S.T.
2. Bootorder within the BIOS
3. Boot the CD or DVD
4. Process the Bootsector loader within the \bootsect.bin file (is hidden!!!).
5. Check if the %SytemRoot%\Bootfix.bin file exists.
- The original Bootfix.bin file brings the message "Press any key to boot from CD".
IMPORTANT: Ezboot and other multiboot system plugins replace the original Bootfix.bin with a own version to START THE MULTIBOOT MENU.
6. You take the PE System entry from the multiboot menu.
7. The PE System processes:
\BOOTFONT.BIN (if exist)
%SystemRoot%\SETUPLDR.BIN
%SystemRoot%\BIOSINFO.INF
%SystemRoot%\TXTSETUP.SIF
%SystemRoot%\NTDETECT.COM
%SystemRoot%\SYSTEM32\NTOSKRNL.EXE
8. the system loads the registry
%SystemRoot%\SYSTEM32\SETUPREG.HIV
%SystemRoot%\CONFIG\SOFTWARE
%SystemRoot%\CONFIG\DEFAULT
%SystemRoot%\CONFIG\SAM
%SystemRoot%\CONFIG\SECURITY
...

Regards,
Teletom


Posted by sm on Apr. 03 2006,20:46

(boombastc @ May 30 2004,15:24)
QUOTE
i get the menů but either if i choose setup XP ot Bart's PE always setup XP starts,why?What should i check?

both boot files must be pointing to the xp install folder

thats what i think,

weather its correct is a different matter lol

Posted by Guest on May 03 2006,00:56
How to create bootable ISO image file using programatically
Posted by Hema on May 03 2006,00:58
How to create bootable ISO image file using programatically
Posted by Guest on May 19 2006,03:44
[B][I][U][CODE]
Posted by Kex on Jun. 14 2006,15:02
Hi all Can i run xosl from easyboot
Posted by Sezgin on Jul. 05 2006,13:58
How to add  SLAX Linux EasyBoot menu

< SLAX HOME PAGE >




Posted by Guest on Jul. 13 2006,12:02
null< My Webpage >
Posted by master278 on Mar. 13 2008,10:35

(martinx @ Dec. 24 2003,03:00)
QUOTE
When a bootable ISO (for example 'bartpe.iso')is created by PEBuilder, you can add it to EasyBoot menu this way:

1) Open 'bartpe.iso' by UltraISO, extract all files and folders to c:\easyboot\disk1 . You can see information as following:

 c:\easyboot\disk1
                      |--ezboot
                      |--I386
                      |--PROGRAMS
                      |--AUTORUN.INF
                      |--BOOTFONT.BIN
                      |-- ...

2) Use 'Boot->Save Boot File' from UltraISO main menu,  and save it as 'c:\easyboot\disk1\ezboot\bartpe.bif'

3) Set 'run bartpe.bif' as command line to coresponding menu item

Note: Use V4.55b (Build 296) or above to avoid problem with long filenames used by Bart PE.

Now already in fills only after Windows fill a mistake indicates and restart. I made it in that manner than into the ones written down but nothing changed. I did it again the pe bulider with a program the Windows but this helps in. into himself it .iso runs correct. something idea?

< error <-- clique here >



Posted by iali on Jul. 23 2008,16:12
Hi Everyone,

i am tring to create one DVD, which'll have, Easy boot menu, 1 should go to Live Win2k3SP2, which 'll have ghost and all the array drivers, and on the same DVD, i'll have our standard image, which can be restored via Ghost,  , 2 should go to HP smartsTART Cd and Third - HP Firmware update Cd, trying to create one DVD for all 3 purpose.

i just also tried with BartPE, it's keeping throwing, Ntsorknl.exe not found.

My Easy menu wors fine, as I'd edited all the Bion files, but, how would I get the East Boot menu to load Cd as liove and get me going.

Thanks,

Ali.

Posted by samcsli on Nov. 02 2008,03:04
this is pretty easy...trust me...

i had made the bart pe file into an img image...

so it safes alots of time when loading...just like how the microsoft's pe works

...wim image+loading...

Posted by balder on Nov. 02 2008,03:31
Hello samcsli

If I understand you right, you suggest “loading to RAM approach”

Well… yes and no in same time :)  I do agree with you if you have a “high performance” motherboard that uses “true high speed” in “DOS”-USB-mode. But how many users have this kind of motherboards ???

It’s for sure nice, as you point out, to load any “LiveXP” system to RAM and run it from there. But before you can run it from RAM you need to load it to RAM, witch may take 10 minutes depending of size of built and type of motherboard.

My son uses an ASUS motherboard that loads my 210 MB Reatogo build to ram in less than 20 sec and then starts up pretty quick :p
On my own computer with a 2-year-old FoxConn motherboard, it takes more than 10 minutes to start up “LiveXP” (Reatogo) if using “load to ram approach” :(
If I instead choose to use “minint_approach” it takes less than 3 minutes to have “LiveXP” (Reatogo) up and running.

But in the future (when most people) do have “high speed USB motherboards (in DOS-mode)”, everyone should use “RAM-loading approach as first choice :cool:

The future is already here...

Edited by balder

Posted by samcsli on Mar. 27 2009,20:37
Hello balder

weird....i'd not remember that i did reply this post... infect this is a very old post.....Dec. 24 2003

well...when i sad that putting image files into a img...or compress into any form i did not mean that everything must be packed... from my 64m p2... i'd know better on how to reduce the # ram used and time used...

you just have to img the very basic(i mean very) that is enough to start bpe to the cmd screen... then use bartpe commend to load the second package while the first one is useless and being deleted...

so: xx.img+xx.im2= xxx.img

....when did i reply this post??



Posted by balder on Mar. 28 2009,03:37
@samcsli

Quote” “weird....i'd not remember that i did reply this post” well it just was there, so I replayed :)

Quote: “so: xx.img+xx.im2= xxx.img” Hmmm  ???  I don’t get the full picture :(

Well, I’m still unsure how this method are implemented and what benefits it have.
Could you please create some type of tutorial to describe your method?

I (and most likely) many users in this board would appreciate if you gave us hints how to use this method – please :O

Regards balder

Posted by seatfriend on May 08 2012,07:25
Hello
I want to make 2 different BartPE versions on one DVD. Version 1 has already been inserted in EasyBoot. (Folder structure in "disk1" with boot informations as *.bif). How can I add the second version? The iso variant does not work, then I get a blue screen.

Please excuse my bad English.

Thank you very much.

regards Sebastian



Posted by balder on May 08 2012,09:49
@seatfriend

Wellcome to Easyboot @seatfriend :)

Quote: "I want to make 2 different BartPE versions on one DVD"

The easiest way to solve this is to run ISO-file as it is from RAM :;):

Download my set of scripts (below in every post I write)
Read carefully 'READ_ME.html' inside folder 'balder' :O

Please copy folder 'balder' to C:\
The 'root' is always the best place to work from!
Also have ISO-file on the root (or into a folder on the 'root')
Please make sure to avoiding spaces in name to ISO-file or folder-name!
Don't use name like: bart pe.iso
Instead use name like this: bart_pe.iso or bartpe.iso (no spaces in names please)

Note: if you run Vista\Win7\Win8 or server-2008 you must lower UAC (User-Account-Control) to lowest setting while run scripts.
Script use command-line tools inside scripts which is stopped if you have UAC set to 'Normal' or higher setting :(

If run scripts is WinXP everything works smooth - no problem with that stupid UAC

Then use 'easyboot-iso.script' to integrate one of your BartPE-builds (use the smallest ISO-file)
Note: check 'Run ISO from RAM' in script, when you integrate WinPE based on NT5-systems (Windows-2000\WinXP\Server-2003 is typical NT5-systems that all uses folder I386)

You automatically receive the right menu command to use in Easyboot menu (copy and paste into EasyBoot menu and that's it!) :cool:

Attention! Above solution only works from CD\DVD-unit and not from USB device
However, I have a working solution how to run ISO-file from USB device as well, just in case you are interested to run EasyBoot from USB as well!


balder



Posted by celavey on May 15 2012,20:57
Is it really possible to convert BartPE file to an image file?
Posted by balder on May 16 2012,01:29
@celavey

Welcome to EasyBoot @celavey :)

Quote: "Is it really possible to convert BartPE file to an image file?"

I cannot fully follow what you mean or the purpose with the question of yours ???

You can rename a ISO-file to let's say *.ima or *.img and you can still launch such ISO in EasyBoot or with using grub :cool:

balder