Topic: windows 7 sp1 32 bit and eset rescue 1 dvd
started by: muhammad15
Posted by muhammad15 on Oct. 31 2013,15:35hello i m newbie and new to easyboot... i want to make a multiboot dvd in which windows 7 sp1 and eset rescue i want....
but windows 7 and eset rescue have same files..... and they replace... it.... and its working only 1 i mean only windows 7.....
can any 1 help me?
i want the easiest method to make it...
Posted by balder on Oct. 31 2013,16:41@muhammad15
Wellcome to EasyBoot @muhammad15
Quote: "i want to make a multiboot dvd in which windows 7 sp1 and eset rescue"
It seems you already are clear how to fix the Win7 case, so I chose to show how to solve the Eset rescue ISO case
You are right that Eset use same folder-names as Win7 do (these two systems are both based on NT6-systems)
This makes it impossible to have both systems in the root-folder of EasyBoot (folder 'disk1' is the root in EasyBoot if you wonder)
Instead you can use the Eset rescue ISO-file as it is
(Note: you cannot use the same solution to Win7 - in that case you must have all files and folders from Win7 in folder 'disk1')
Test this to Eset rescue ISO-file:
1. Copy Eset rescue ISO-file to folder EZBOOT
2. Create menu command in EasyBoot menu and use menu command: run eset.iso (or whatever name you use to Eset ISO-file)
Note: Eset rescue ISO-file is basically a 'WinPE-system' and is loaded and run from RAM (which makes it possible for EasyBoot to launch ISO-file as it is)
Posted by muhammad15 on Oct. 31 2013,17:27well... i tried and it works ;) thankyou!!!
and how can i have a multiboot DVD of windows xp 32 bit and 64 bit
Posted by balder on Nov. 01 2013,01:59@muhammad15
Quote: "and how can i have a multiboot DVD of windows xp 32 bit and 64 bit "
Yes this is possible
Note: there are an tutorial in EasyBoot help-file how this can be done, but that tutorial works for WinXP without service-packs and only for English WinXP
Better up is to use my script 'easyboot-aio.script'
You have download below in every post I write in this forum
Download scripts (it's a zip-file) and extract zip-file to C:\
Read carefully READ_ME.html inside folder 'balder'
Use easyboot-aio.script to integrate different WinXP-sources
Posted by muhammad15 on Nov. 01 2013,03:02i downloaded ur script ... and i m new at easyboot forum and software also.....
and which other iso i can use directly like eset.iso??
Posted by balder on Nov. 01 2013,03:28@muhammad15
Quote: "and which other iso i can use directly like eset.iso"
But your request was: "and how can i have a multiboot DVD of windows xp 32 bit and 64 bit"
You are asking two different things here
Note: to be clear, you CANNOT use ISO-file of WinXP to launch setup - you must have files and folders from respectively system on the root of EasyBoot (but use my script 'easyboot-aio.script' to modify source to run from an extra folder on the root of EasyBoot if your intension is to have several winxp in build).
There is also a 'help-button' in script that give some basic help how to use script
About this: " and which other iso i can use directly like eset.iso"
You can run a lot of ISO-files as they are
Here you have a basic list:
All WinPE-ISO-files based on NT6-systems (NT6-systems are Vista, Win7, Win8 and server-2008) typically examples is Eset, ActiveBoot Disk (from version 5) and all versions of MsDart (MsDart60, MsDart65, MsDart70 etcetera)
It's easy to see if ISO can be run directly (run ***.iso) by open ISO-file (use UltraIso) - if you have folders like: SOURCES and BOOT and a file BOOTMGR then it is a WinPE based on NT6 which means you can launch ISO as it is
ATTENTION! You CANNOT launch setup of Win7 or Win8 from there respectively ISO-files (you need to have files on the 'root' in EasyBoot which is folder 'disk1')
You can launch all different Acronis-rescue-ISO-files and in most cases also paragon-ISO-files (note: paragon can be a slow process to launch)
You can also launch ERD (ERD is a WinPE based on NT5-system and NT5 is Win2000, WinXP server-2003)
However to launch such WinPE built from a NT5-source you need to use my script: 'easyboot-ISO.scrip' which creates special environment to run ISO from RAM with special driver ('firadisk) that script automatically implement in your build (you also receive correct menu command to use in EasyBoot menu by script)
Posted by muhammad15 on Nov. 01 2013,04:41thanks u cleared my xp doubt....
ATTENTION! You CANNOT launch setup of Win7 or Win8 as examples from there respectively ISO-files (you need to have files on the 'root' in EasyBoot which is folder 'disk1')
is that means i cant make windows 7 and windows 8 multiboot dvd?
Posted by balder on Nov. 01 2013,05:24@muhammad15
Quote: "is that means i cant make windows 7 and windows 8 multiboot dvd?"
Yes this is a problem as Win7 and Win8 uses same folder name on the 'root'
Further more, even we could solve this, you create new problems with the final size to such build
It seems EasyBoot have problem if final build exceeds 4.2 GB in size
Note: There are some limits related to the UDF-format - < READ HERE >
Further more if build is larger than 4.7 GB it even doesn't fit into a 'standard' DVD - you must use double-sided-DVD
Take it 'as a man' - large build (with sizes over 4 GB) creates problems - accept this
Better is to use USB stick in such cases
In fact - I predict that in less then 5 years DVD is used in less than 5 percent of this cases - CD\DVD is a dinosaur - USB stick\harddrive is the future
Posted by muhammad15 on Nov. 01 2013,06:32yup but i m going to make a multiboot dvd like this...
1 windows7 sp1 32 bit (2.34GB)
2 windows xp sp3 with sata (700MB)
3 hiren boot (600MB)
4 ESET RESCUE (226MB)
5 boot from hdd...
it will exceed 4.2GB i think... what problems will it create??? any idea?
Posted by balder on Nov. 01 2013,07:04@muhammad15
Quote: "it will exceed 4.2GB i think... what problems will it create"
My guess is that it creates problem the UDF-format problem most likely pops up
If I where your, I would skip HIREN
Hiren is much overrated - instead use ActiveBoot Disk-5 (it has Ghost_v11 integrated as example)
Or have ERD-commander (ERD5) in build
Or a small Linux-distro to access files so you can save files if your system refuse to start
Try to keep build less than 4.2 GB in size - which may end in that you must skip some of above and only have Win7, WinXP ans ESET (if possible) in the final build
Posted by muhammad15 on Nov. 01 2013,07:18thanks and i really appreciate ur thinking but hiren has windows password reset... live xp and many softwares... and many more features..... and i didnt used Active boot or erd or linux (ubuntu) ever... and what is udf format problem? i know the iso format
Posted by balder on Nov. 01 2013,08:41@muhammad15
Quote: "it will exceed 4.2GB i think... what problems will it create"
You need UDF to large builds and if you need to tick 'Joliet' (needed if having knoppix in build) 'Joliet' doesn't work
Accept that large builds create problems as long as EasyBoot doesn't have full support to the UDF-format
As you can notice; The need of UDF 'kills' the 'Joliet-switch' - it's a kind of moment-22
Some interesting notes:
< HERE > and < HERE >
Posted by muhammad15 on Nov. 01 2013,11:25what does joliet means??? how it works?
as i said i m new at easyboot... is there any video or anything... i m looking for instructions for every option how to use
i know i m asking for really very hard work......
Posted by balder on Nov. 01 2013,12:38@muhammad15
Well you really don't need to know everything in detail about 'Joliet' but basically you must tick 'Joliet' if having Knoppix in build
But some basic knowledge about 'Joliet' is its primary focus with the relaxation of the filename restrictions inherent with full ISO 9660 compliance.
Or with an simple language: Joliet makes it possible (or easier) to use longer filenames
Compare with DOS that accept only 8 letters to a file or folder name
If you use longer name in DOS name is truncated (tail-docked)
Example: If you want a long file name to a folder in DOS - let's say 'muhammad15' it is showed in DOS like this: 'muhamma~' (as you can see 7 letters plus '~' that makes it 8 letters in total length)
The role is; use 'Joliet' if having knoppix (or similar linux-build) in your build
And remember that 'Joliet' most likely fail to function if using UDF (which must be used when having size over let's say 4.2 GB or something)
Posted by muhammad15 on Nov. 01 2013,12:50ok thank you very much... look like my all problems are completely solved.....
incase in future i got any problems... i'll contact u... or come to this topic... thnx...
Posted by muhammad15 on Dec. 07 2013,05:06i made a multiboot
1. windows xp sp3 ( 650MB)
2. Windows 8.1 pro (2.7GB)
3.Ubuntu 12.4 (704MB)
total = 4.03GB
all is working fine... but when i boot windows 8.1 by pressing 2 and enter....
CD BOOT memory overflow Error...
xp and ubuntu is booting... only 8.1 error....? whats that ?
i extracted all files of ubuntu and 8.1 and xp only i386 folder and winip files...
Posted by balder on Dec. 07 2013,07:32@muhammad15
Quote: "CD BOOT memory overflow Error..."
This can be caused by a lot of different parameters - hard to tell from where I'm sitting
However some basic questions:
1. Have you run setup of Win8.1 from the 'original' DVD (did it worked then?)
2. Test with only having Win 8.1 in build (to reduce size of build)
3. And test suggestion-2 with and without ticking 'Joliet'
Note: you can use DVD-RW to not spoil anything
4. Use a USB stick (you need 4GB or larger stick) and reboot
Note: you can interrupt setup of Win8.1 to not destroy your OP-system on harddisk
This is only to see if problem is solved when run from USB stick
What happens with above suggestions?
Posted by muhammad15 on Dec. 07 2013,09:40yes i have run setup of Win8.1 from the 'original' DVD it worked nice... and i make multiboot dvd also with using magic iso... but when i make multiboot with easyboot
error comes.... CD BOOT memory overflow Error..."
2. Test with only having Win 8.1 in build (to reduce size of build)
yes i test with only having Win 8.1... still same problem.... its not making a bootable also...
and i didnt ticked that joliet because u told me not to use...
and i m not formating my own pc.... i m using that image file on VMware-workstation-full-10.0.0-1295980.exe
is anything that i forgot to mention???
Posted by balder on Dec. 07 2013,10:09@muhammad15
Quote: "is anything that i forgot to mention?"
No that's enough information for the moment
Test this (I know it sounds odd ):
1. Create your build as you did in post nr;16 (push only 'Save' in EasyBoot but don't create ISO)
2. Launch UltraISO and create ISO (using all files from inside of folder 'disk1' in EasyBoot)
Note: use 'loader.bin' from folder EZBOOT as boot-file in UltraISO
How did that works out
Posted by muhammad15 on Dec. 07 2013,12:01i did as u told me.... but same error occured
cdboot: memoryflow error
i think easyboot cant make windows 8.1 bootable...
but i tried magic iso ( made in 2009) its working with multibootable too....
Posted by balder on Dec. 07 2013,12:20@muhammad15
Quote: "but i tried magic iso ( made in 2009) its working"
I'm drawing the conclusion you made it work alright -correct?
Could you please look in 'properties' what settings that was used when 'magic iso' created that working ISO-file
It could be that magic iso used different settings comparing to UltraISO 'standard settings' when ISO was created
Posted by muhammad15 on Dec. 08 2013,05:28first u check it how i make a multibootable image with magic iso...
watch the video... and u will get... i think ultra iso is not the problem... easyboot cant make a windows 8.1 bootable, i think...
< https://www.youtube.com/watch?v=UMa8yPyuxuE >
i think easyboot need to get update.....
Posted by balder on Dec. 08 2013,06:01@muhammad15
Quote: "easyboot cant make a windows 8.1 bootable"
I don't agree - I'm positive EasyBoot (or UltraISO) in the end can create a working ISO
However I prefer using UltraISO as described in post nr;19
Please use UltraISO and open ISO that was created by magic iso and in 'UltraISO>>File>>Properties' check what parameters that is used to this ISO
Use same parameters in UltraISO following guide-lines in post nr;19
Attention! Make sure you extract 'boot-file' from the original Windows-8.1 ISO-file
Save boot-file to folder disk1 in EasyBoot and use menu command: run *** (note: you can use any name or the usual bootmgr or efimgr or whatever you prefer)
It's vital you use correct boot-file to Win8.1 and best result is to extract that boot-file from a working windows8.1 ISO-file
Posted by muhammad15 on Dec. 08 2013,06:43yes i extract boot file from windows 8.1 original iso.... and paste it to disk1 ezboot folder and run command as bootinfotable; run win8.bif
i done it all correctly.... plz watch that magic iso video once... i think u will get my solution... u dont have windows 8.1 image? thanks
Posted by balder on Dec. 08 2013,07:52@muhammad15
Quote: "plz watch that magic iso video once"
I have no use of watching a movie about magic iso
I watched movie and nothing new that I already know was found in movie
Magic iso uses basically the same procedure to create a multiboot ISO-file as UltraISO/EasyBoot does
The difference might be what 'settings' that is used in magic iso - this is the vital difference
Again I urge you to do a simple 'forensic examination' of ISO created by magic iso to see what settings that was used im magic iso
I ask you again, please use UltraISO to open ISO that was created by magic iso and select; 'File>>Properties' in UltraISO and tell what parameters that is used in this ISO you created with magic iso
What properties (File System) is used in ISO; Joliet, RockRidge, Apple HFS, UDF, Windows/Unix(31) or Max(221) and IF Joliet is ticked, what Joliet File Format is used then? Standard(64) or Extended(110)...???
Use these setting that is used in ISO created by magic iso in UltraISO
Again read post nr;19
Quote: "u dont have windows 8.1 image?"
No I do not have this ISO in my position
Posted by muhammad15 on Dec. 08 2013,08:15
u have teamviewer
i used the same settings which is in magic iso... still no success...
Posted by balder on Dec. 08 2013,09:45@muhammad15
Quote: "used the same settings which is in magic iso... still no success..."
Thank you for clarifying settings in ISO
By the way, is the build larger than 4.2 GB in size (its looking so in picture you show)
I know that UltraISO\EasyBoot have issues when build exceeds 4.2 GB
On the other hand - you probably already have tested with only having Win8.1 in build to reduce size - and it still fails
However I'm pretty sure it works from USB stick (only Win8.1 as WinXP needs 'workaround' from USB drive)
Hmm... It seems we are stuck here
Thanks anyway for clarifying problems related to your build
Posted by muhammad15 on Dec. 08 2013,09:55yes.... i m sure easyboot need to be update... v cant make windows 8.1 bootable with easyboot windows 8.1 (2.7GB) i m not making multiboot... its not even making a bootable only 8.1
can u report the easyboot of this problem???
Posted by balder on Dec. 08 2013,10:44@muhammad15
Quote: " can u report the easyboot of this problem"
Well I'm sure 'xoben' is watching from time to time at this forum
EasyBoot\UltraISO is still developed as 'things' out 'there' continuously is changing
Posted by muhammad15 on Jan. 30 2014,19:03yesterday i again tried to make a multi boot of Windows 8.1 Pro but now this time i got this error..
CDBOOT: Cannot boot from CD -Code: 5
What is Wrong with it???
@Balder u got anything for me???
Posted by balder on Jan. 31 2014,02:06@muhammad15
Quote: "CDBOOT: Cannot boot from CD -Code: 5"
Is it setup of Win8.1 from DVD unit or from USB stick\thumb-drive
You need to clarify this before we procedure
Posted by muhammad15 on Jan. 31 2014,21:28i made that iso, and run in virtual machine......
Posted by balder on Feb. 01 2014,03:18@muhammad15
Quote: "run in virtual machine"
He, he you sure are some limited in your response
Have you tested with run setup of Win8.1 original ISO in virtual machine
I ask, because there could be some file missing from the ISO you created in EasyBoot.
Also take in consideration that the 'virtual machine' is far from bullet proof in its behaviour, mismatch with hardware issues involved is quite common
Another issue is that testing in 'virtual environment' could sometimes be a bit hazardous
No guaranties it could be run as in a 'reality test'
It might work with original ISO and not with the ISO created in EasyBoot
But ISO created by EasyBoot might work alright if run from a 'real BOOT'
If you do have a USB stick you could do a better test (skipping continue setup to not destroy any of you DATA)
Posted by muhammad15 on Feb. 01 2014,04:39yup i have tested the windows 8.1 original iso in virutal machine....
And i checked that easyboot (multiboot iso) with pendrive... no error comes but full blackscreen no booted
till now u dont have 8.1 iso??? i just want to check only i m facing problem or every 1..
Posted by balder on Feb. 01 2014,05:58@muhammad15
Quote: "no error comes but full blackscreen no booted"
Eeee... What do you mean...
Did it boot up when run from USB stick correctly and you could continue the setup sequence?
Unfortunately I do not have any Win8.1 ISO, but I currently run Win8.1 which on the other hand (in my opinion) is the most stupid OP-system created by Microsoft so far
I hate it and are very anxious to get next version installed and in future NEVER use Win8.1 again
Note: there might be some 'peculiarities' with your Win8.1-ISO that creates these problems
It happens to often that ISO-files have some 'scratches' that creates problem when files and folders are extracted from ISO-file, instead of burned directly to a CD\DVD
I guess we are locked up here, not solving this problem
Posted by muhammad15 on Feb. 01 2014,07:18ok thnx for help.... now i quit to make a win8.1 multiboot its very complicated OS for me.......
by the way i m using xp as my default OS. its very nice for me.... simple to use and compatible with every software....
will use XP 1-2 years more