Topic: To whom it might concern
started by: balder
Posted by balder on Dec. 19 2009,08:01
To whom it might concernA lot of EasyBoot-users ask for help how to launch ISO-file directly (avoiding extracting files and folders). This is of course the ultimate solution – using ISO-files as they are
Plenty of ISO-files can be launched using my grub based “kicker-images” – but not all
However – there is no such thing as a “free lunch”. Not all ISO-files can be launched directly. You have to test for your self which ISO-file that offers “free lunch”
To make things more easy for EasyBoot-users I have created a special script (easyboot-iso.script) that automatically copy your target ISO-file to EasyBoot and then automatically create “kicker-image” that at same time is automatically modified to launch target ISO-file).
Note: You have to download “Startkit” and continue to scripts and there download easyboot-iso.script. Follow instructions carefully how to manage scripts and winbuilder script-engine.
Scroll down to “Welcome to my website here” to find above-mentioned scripts
Balder
Posted by fsaaib on Dec. 19 2009,12:11
Thanks Balder, you always come in handy.I just want you to take a look at this recent post i´ve made asking for help on loading wifiway correctly so i can use it in the winbuilder script you´ve made to transfer the whole project to a UFD, i finished my build (it works OK, the iso i made with easyboot)
The problem comes when i try to test it on UFD (using your script to transfer the easyboot project to a usb flash drive) and select to bootup wifiway, it tries to load, then gets stuck on the part that its "searching for data folder", and it never loads up, ends up with an error message *sighs*
Any heads up will be really apreciated, as you´ve helped so many people in here
Thanks in advance
Best regards,
fsaaib
Posted by balder on Dec. 19 2009,13:49
@fsaaibThanks for reply fsaaib
Generally you must think different when run EasyBoot from ufd – as we are using grub to directly launch easyboot-ISO-file as it is. When this approach is used, root of easyboot (disk1) is lost and basically transferred to root of ufd. This means that you have to copy some file/folder ” that holds the “core” of the program – in this case the “core” from wifiway
I guess that it is this build you are referring to < HERE > @fsaaib (correct?).
To make wifiway run from ufd, test with copy folder wifiway to the root of ufd – we can name it the “new root” if you find it easier to understand - hmmm not the best explanation
Attention for setup of WinXP. As “root” is lost when launching EasyBoot-ISO-file from ufd using grub you cannot launch setup of WinXP the same way as launch setup from CD/DVD-unit. It’s a major difference in this matter. Read post nr; 25 and 27 < HERE >
Note: easyboot-iso.script is not used to transfer ISO-file to ufd and making ufd bootable
easyboot-iso.script is a brand new script that integrate grub bootable ISO-files into EasyBoot structure (directly launch ISO-files without need to extract anything from ISO-file).Regards balder
Posted by sudhan1991 on Mar. 07 2010,06:20
Dear Balder,Can You Please tell,On what criteria does your "kicker-images" work.
ie.) How do I differentiate between a kickable-iso and a non-kickable iso.
ie.)How do I know if the iso uses grub as boot manager or not.
It would be much easy,if you yourself list those kickable iso's out there.
And Moreover can you Please tell what is the exact command to be given in the "Make iso" dialog box,to load the iso.
And the Winbuilder script,gave out an Error-
"FileCopy - Failed to copy [%BaseDir%\Temp\newimage\SPOT.img] to: [C:\Easyboot\disk1\ezboot]"
-How do I rectify it.
Posted by balder on Mar. 07 2010,06:49
@ sudhan1991Quote: ”Can You Please tell,On what criteria does your "kicker-images" work.”
Answer: "kicker-images" is based on grub boot manager and load ISO-files using “grub” boot loader facility. You need to read about grub – please google and read. This "kicker-images" you mention is designed by me (basically created in script) and are designed to help EasyBoot to launch ISO-file directly (if possible).
Quote: “How do I differentiate between a kickable-iso and a non-kickable iso.”
Answer: Test and trial as I do
. Note: there is no such thing as a "free lunch" - grub cannot launch some ISO-files.Quote: “It would be much easy,if you yourself list those kickable iso's out there.”
Answer: There are thousands of different ISO-files out “there” for free download – It’s 100% impossible for me to 100% know about all these files and followed by test all this ISO-files (and new ones every minute – in fact new ones when you are reading this post)
Quote: “And Moreover can you Please tell what is the exact command to be given in the "Make iso" dialog box,to load the iso”
Answer: You get menu command automatically in the end of script process. Use paper and pen and write down menu command to be used in EasyBoot menu
Note: easyboot-iso.script has been updated. Please download and replace to new script. Attention! Please push “Help-button” in script to better understand how things work
Quote: "FileCopy - Failed to copy [%BaseDir%\Temp\newimage\SPOT.img] to: [C:\Easyboot\disk1\ezboot]" What system do you run script in? Read post;5 and post;6 < HERE >
Note: Make sure you do not have spaces in file names (ISO-file to be integrated as example)
EDIT: @sudhan1991 I discovered a “text bug”
I forgot to put in *.gz in the end of message (menu command message) you get when script is finished.
Note: To all users – if using (downloaded) “winbuilder_complete.zip”. Please do new download and replace the whole folder with updated “winbuilder_complete.zip”.
If you downloaded only easyboot-iso.script (easyboot-iso.zip) separately. Please do a new download and replace script “easyboot-iso.script” in folder winbuilder.
Note: This is only an “ocular” problem. You get in the end a message what menu command to use in EasyBoot menu. Let’s say it is: run erd5.img which should bee run erd5.img.gz (floppy image is as you can notice – always g-zipped for faster load and save space as well).
Regards balder
Posted by sudhan1991 on Mar. 07 2010,08:55
I'm Working on:Spotmau 2010,XP SP3,ERD 2008,UBCD 4.1,Active@bootdisk v5,Hiren 10.1 and Ghost v15
Updated the script but,I get no menu command at the end(Where to look for it
) and i get only this error.For Spotmau 2010:
FileCopy - Failed to copy [%BaseDir%\Temp\newimage\SPOT.img] to: [C:\Easyboot\disk1\ezboot]
and for ERD 2008:
FileRename - Failed to rename file: [I:\Softwares\Boot Progs\Windows\ERD Commander 2008\ERD\ERD\ERD28.ISO.gz] to:[ERD28.ISO.GZ]
My System config:
Windows XP SP3,2Gb RAM,750Gb HDD
Posted by balder on Mar. 07 2010,09:22
@ sudhan1991Quote: “Updated the script but,I get no menu command at the end(Where to look for it) and i get only this error.”
FileCopy - Failed to copy [%BaseDir%\Temp\newimage\SPOT.img] to: [C:\Easyboot\disk1\ezboot]
Note1: Check that path in script to easyboot look like this: “C:\easyboot” and not like this: C:\easyboot\ and even more important - make sure that EasyBoot is installed on C: (the root) and not in “C:\Program files” or similar! Always remember to avoid spaces in folder and file names
Note2: You don’t get any menu command because script halted in its process – basically, script didn’t finish its whole process
Note3: I have tested script in WinXP, Vista and Win7 without problems and as you currently use WinXP as OP it really shouldn’t be any problem
EDIT: If you trying to integrate a ISO from a folder with this name ERD 2008 Script fails completely – you can not use folder and file names which has spaces. Same if folder name is correct: ERD2008 but name to ISO-file inside folder looks like this: ERD 2008.iso Please take attention to that you cannot use spaces in names
Regards balder
Posted by sudhan1991 on Mar. 07 2010,09:46
That Problem Solved,Now This,
FileCopy - Failed to copy [%BaseDir%\Temp\newimage\ERD28.img] to: [C:\Easyboot\disk1\ezboot]
And
FileCopy - Failed to copy [%BaseDir%\Temp\newimage\UBCD.img] to: [C:\Easyboot\disk1\ezboot]
Should I be using,Easyboot-Live script
Posted by balder on Mar. 07 2010,10:04
@ sudhan1991Sorry, but I persist to believe that you have spaces somewhere – maybe even in name you set for you ISO in script.
I have tested following (Note: quotes only there to show real names):
1. I put in name “TEST” – and no spaces in folder where I have my ISO-file and it works.
2. I put in name “TEST A” and it doesn’t work.
3. I put in space before “ TEST” and it doesn’t work.
4. I put in space in folder where my ISO-file is and it doesn’t work.
Conclusion: watch out for spaces in folder and file names!
You can use easyboot-live.script for some of your builds (builds based on folder i386) - but again - watch out for spaces in folder and file names!
Regards balder
Posted by sudhan1991 on Mar. 07 2010,11:22
< Hurray!!! > The Mighty Balder Did it again.
The Script worked like Charm and the mistake was My drive name,cleared those spaces and got everything Fine.
But It sounded like ERD loaded somewhat slow and that Active@bootdisk asked for the key, which when punched in, works fine.
Thanx For Spending You're Precious Time Balder, You're The Man.
Posted by balder on Mar. 07 2010,11:34
@ sudhan1991Quote: ”but It sounded like ERD loaded”
If this “ERD” is vista-based (sometimes called “MsDart-60 or MsDart-65 and not using folder i386 inside itself) you should NOT check “Run from RAM” in script, as this “Vista-based” ISO-file do not need RAM-loading. In this way it is loaded directly (avoiding load whole ISO to RAM).
Note: Basically only ISO-files based on folder i386 (typically ERD5 or ERD7 or ISO-file from BartPE or Reatogo or similar) need to be run from RAM
He, he quote: “The Mighty Balder Did it again.” He, he - That was a new one
PS. Nice you solved your problems - great
Regards balder
Posted by Orochi on Mar. 14 2010,15:50
balder, thank you for your script.If Easyboot is installed in "c:\program files x86" folder, will the script still work?
Also in the beginning I thought that this was a script that launched ISO files directly using grub therefore no need for easyboot.
Posted by balder on Mar. 14 2010,16:16
@ OrochiHi Orochi
Quote: ”If Easyboot is installed in "c:\program files x86" folder, will the script still work?”
No this is not a good solution – you can test with make a copy the whole folder EasyBoot to the root (C:\) and open folder EasyBoot there followed by double-click to EasyBoot.exe inside there. I think this is possible.
Script(s) doesn't like spaces in names to files and folders – keep that in mind
Quote: ”Also in the beginning I thought that this was a script that launched ISO files directly using grub therefore no need for easyboot.”
Well yes and no. The point with this arrangement is to expand possibilities with EasyBoot.
As we already know - you can easily launch floppy images (ghost or whatever) with EasyBoot. To launch ISO-files as they are directly in EasyBoot is quite an improvement (if I may say so
) – and it is also quite easy to use EasyBoot from USB device as well – that last point is getting more and more interesting for the future as well as today. Balder
Posted by Orochi on Mar. 14 2010,16:58
Thank you balder for your hard work.All the best to you... !!!
Posted by Orochi on Mar. 19 2010,17:46
Hello balder,Just want to share my experience with the ISO script.
1. It seems that the script doesn't work very well with nested or multiboot ISOs.
For example, using the script I could not make hiren bootcd 10.2 work; neither MINI windows XP nor the DOS CD worked.
2. It seems that there is a problem when using RAM option. I tried to make a ISO using DIgiWIZ miniPE XT which has a folder mnpe at the root of the disk. Every time I ran the script with the ram option enabled, script was aborted and I kept receiving an error of that a file cannot be renamed. This happened only when the ram option was enabled. When I disabled this option the script finished successfully but then the ISO (miniPE XT) did not load properly from easyboot.
3. the defrag option in the USB script did not work for me. The script said that the file defrag.exe cannot be found.
I am guessing this is because I am on win 7 64.
I would appreciate if you could clarify few things regarding the points mentioned above.
Once again, thank you for your wonderful scripts.
Posted by balder on Mar. 20 2010,04:05
@ OrochiFirst of all – thank you for this clarifying notes (and your efforts to make these tests which I highly appreciate) – it sure helps a lot.
Now to the “reality”
Quote: ”1. It seems that the script doesn't work very well with nested or multiboot ISOs.”
Answer: This is not related to script it self – it’s related to if grub can launch such ISO in a correct way– which unfortunately it can not (you described it correctly: “nested or multiboot ISOs” – grub cannot launch such ISOs)
Quote: “2. It seems that there is a problem when using RAM option.”
Answer: Please check that you do not have spaces in name to file or folder where you keep ISO. Test with copy this ISO to the root (C:\) and also rename it to a shorter name without spaces like this; digiwiz.iso
Attention! Make sure you have EasyBoot and Winbuilder folder installed on the root (C:\) and not in folders like “Program files” as such folder has space in name – and the same to ISO-files – never use folder “Program files” there is a space in name
Please report back if it did work this way.Quote: “3. the defrag option in the USB script did not work for me.”
Answer: Tested on my barebone computer that run Win7 (recently installed. Use it in the cellar as I hate Vista/Win7
– just joking). I have no problem using this option in script. Do you run Win7 with full admin-rights Final note: My web pages are slowly dying and will in this days shout down completely
. I have to find new web host for web pages and files – unfortunately this may take several weeks or even months – in meanwhile I will try to upload to rapidshare or similar.Regards balder
Posted by Orochi on Mar. 20 2010,04:32
balder thank you for responding PS. balder I forgot to ask. How important is it to activate "allow for lower case letter" checkbox?
The First time i compiled an ISO without this feature activated and the CD worked fine. Every program was booting fine.
Posted by balder on Mar. 20 2010,06:51
@ OrochiQuote: ”PS. balder I forgot to ask. How important is it to activate "allow for lower case letter" checkbox?
The First time i compiled an ISO without this feature activated and the CD worked fine. Every program was booting fine.”
@ Oroch
You do have a BIG POINT there! It’s really not necessary to check “Allow Lower Case” when creating ISO in EasyBoot - I completely forgot this (note: I made this changes recently and forgot about memdisk). Reason that we no longer need this “Allow Lower Case” is that I use memdisk to launch grub based “kicker-images” (images is used as compressed). Thanks for pointing my attention to this fact.
Anyway about script: If integrating MsDart60/65 (NT6-system) you do not need to use “Run from RAM”. It’s basically only needed when integrating WinPE based on NT5 (WinXP-family that uses folder i386 including server 2000/2003 which also is a NT5-system). If integrating Acronis rescue ISO-files you mostly do not need “Run from RAM”.
Regards balder