|
|
| Post Number: 1
|
balder 
Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Sep. 27 2010,09:56 |
|
   |
@ CDMaker
Quote: ” now I want to make it bootable for do the following jobs”
He, he you sure are asking for a lot  – however some solutions can be found if you use search-button and use “older topics” 
Anyway some quick answer below here…
“1- Installing different versions of Win XP direct from Hard disk” = Read post nr; 25 HERE
”2- Installing different versions of Win 7 direct from Hard disk” = To have several different NT6-systems (Vista/Win7 or server-2008) is possible but not an easy task. I recommend you to read HERE
“3- Run Live CDs. (BartPE, WinPEs etc)“ = My script easyboot-iso.script can launch ISO-file from any BartPE or WinPE (including MsDart-versions).
“4- Boot PC from HDD and do all recovery work.” = Unsure what you mean by this
“5- Create/Restore PC ghost or Image.” = Can be solved in several ways. Read a basic solution in post nr; 8 HERE
“6- Merge/Use all utilities which are avaliable on net.” = Unsure what you mean by this
balder
Edited by balder on Dec. 26 2010,22:56
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
 |
|
|
| Post Number: 2
|
|
|
| Post Number: 3
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Dec. 27 2010,01:11 |
|
 |
@CDMaker
Quote: ”I am really a dump man”
He, he maybe you should change name to “USB_maker” (unfortunately not possible to change name  ).
Anyway – it is an extremely impressive bunch of utility tools you have on your USB harddisk – very impressing 
Sure I know who “Jamal” is
His tutorial style is “straight forward” – and easy to follow.
Though He doesn’t in detail explain from where grub-menu.lst parameters are fetched in most of tutorials.
However I have no problem with this – as His tutorials are so easy to follow.
EasyBoot have some advantages comparing to grub.
It’s much easier to integrate floppy images – and Easyboot can also create “pre-made” floppy images in different sizes!
And of course it’s extremely easy (as the name EasyBoot) to create submenus and to jump to any submenu from a submenu and back to main menu etcetera.
And also use different nice backgrounds.
Note: you are advised to only use 9 menu commands in each EasyBoot-menu.
Create submenus to avoid using more than 9 menu commands in each menu.
As a consequence how easy it is to integrate floppy images – I got the idea to use “grub-kicker-images” – and that’s basically the thing you are going to use.
Note: you can use one “grub-kicker-image” and basically make copies of this one and change menu.lst inside with the menu.lst “Jamal” provides.
Then launch this different kicker-images from EasyBoot using “memdisk ***.img.gz” (read about why images are g-zipped below)
Make sure path is correct in menu.lst to ISO-file(s) - as I use a folder “ISO” on the “root” (folder disk1) which “Jamal” may not use in "menu.lst".
Copy ISO-file to folder disk1 - or a folder ISO in folder disk1 (do as you whish) - check path and take attention to that grub is case sensitiv when used on CD/DVD-units!
You can use easyboot-kicker-images.script to create your “grub-kicker-images”.
However some of your ISO-files can much easier be integrated using my script easyboot-iso.script!
Example on this is:
Mini Windows XP
OPHCRACK Live
Hiren's Boot CD 10.6
Ultimate Boot CD (UBCD) v5.0.2 – however you must copy “pmagic-4.10.sqfs” to folder disk1 (you can then delete pmagic-4.10.sqfs in ISO-file as it now is on the “root”=folder disk1 in Easyboot).
Note: “easyboot-iso.script” can launch all kinds of WinPE-ISO-files. Both NT5-systems (folder i386 inside ISO) as NT6-systems (Vista\Win-7\ghost-14, ghost15 MsDart-ISO’s etcetera) – all these ISO-files can easily be integrated using this script.
Next step is to use easyboot-grub-iso.script to get all transferred to USB.
But you do have one problem here. Script refuse to work on USB disk unit that have more than on partition due to safety reasons.
However this can be solved by using one partition and then “ghost” this partition and ghost back to one of your chosen partitions.
Let’s take one example what I mean.
We are going to create a grub-kicker-image to launch “BOOT to harddisk”.
This can for sure be done in several ways – but I use this method:
Use easyboot-grub-iso.script. Download latest script-collection and push on "Make USB bootable and transfer ISO-build to USB" to make USB bootable with grub MBR.
You by now have several files on USB – including “BOOT_HARDDISK.LST”. This is our target.
Use easyboot-kicker-image.script and put in these lines in menu.lst:
root (hd0,0)
configfile /BOOT_HARDDISK.LST
Create image (check “g-zip”) and use menu command in EasyBoot: memdisk ***.img.gz (*** = your name to floppy image)
There are two reasons why I prefer g-zip:
1. Floppy images is shrink to 1/10 of size which later make it easier (faster) to transfer the EasyBoot-ISO-file to USB
2. I’m not dependent of “Allow lower case”.
Use easyboot-grub-iso.script. Download latest script-collection and create new ISO in script – continue then by pushing on "Make USB bootable and transfer ISO-build to USB" to make USB bootable with grub MBR.
What happens using this method?
1. You BOOT computer from USB and launch EasyBoot.
2. When launching ““***.img.gz” (your menu for BOOT to harddisk) grub-kicker-image is started
3. Grub then launch BOOT_HARDDISK.LST on USB which is executed
4. BOOT_HARDDISK.LST on USB have several fallbacks to find a bootable Windows-system on any harddisk partition with higher disk unit number than zero (0,0) - which is the USB disk unit.
At this point I think you understand that I really cannot give you specific guidelines for every utility you want to integrate to your USB device 
I can only give you the basic principles how it can be done.
It’s of great interest that you used this tutorial HERE with success – thanks for clarifying that it seems to work
This also demonstrate that you are not “a dump man” 
Final note...
To keep a clean environment in folder ezboot you can use subfolders in folder ezboot
Example:
1. create a subfolder “USB” in folder ezboot
2. Copy any floppy image to folder “USB” (let’s say ghost.img)
3. In normal case you use “run ghost.img” as menu command in Easyboot. But as you want to launch ghost.img from a subfolder you change menu command to: run /ezboot/usb/ghost.img
Note: letters are not case sensitive in EasyBoot (another advantage in EasyBoot)
Regards balder
Edited by balder on Jan. 04 2011,04:25
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 4
|
|
|
| Post Number: 5
|
CDMaker
Group: Members
Posts: 16
Joined: Dec. 2006
|
|
Posted on: Jan. 18 2011,11:27 |
|
|
Dear Guru (balder) 
I found these three methods in this forum and in your script Please Explain me what the deference or advantage between them.
QUOTE title Launch ERD 2k/WinXP/2k3
find --set-root --ignore-floppies /FIRADISK.GZ
map --mem /FIRADISK.GZ (fd0)
map --hook
find --set-root --ignore-floppies /ERD50.iso
map --mem /ERD50.iso (0xff)
map --hook
chainloader (0xff)
QUOTE title Launch ERD x86 for Vista
find --set-root --ignore-floppies /ERD60x86Vista.iso
map /ERD60x86Vista.iso (0xff) || map --mem /ERD60x86Vista.iso (0xff)
map --hook
chainloader (hd32)
boot
QUOTE title Launch ERD x86 for Windows 7 / 2k8
find --set-root --ignore-floppies /ERD65x86W7.iso
map /ERD65x86W7.iso (hd32)
map --hook
chainloader (hd32)
boot
Second method is not working for me...
|
|
|
|
| Post Number: 6
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jan. 18 2011,13:23 |
|
|
@CDMaker
Quote: ”Dear Guru (balder)”
He, he thanks for the title
Quote: “I found these three methods in this forum and in your script Please Explain me what the deference or advantage between them”
Answer: Method one use a separate driver image “FIRADISK”
Firadisk makes ISO-file run in RAM.
You cannot use method two to a NT5-system (WinXP-PE or similar NT5-system - even it does load ISO to ram before launching) as drivers isn’t reachable from inside of ISO.
Method one works for NT5-system (WinXP-PE as example) as drivers is extracted and loaded from FIRADISK image.
ISO-file is also loaded to RAM - otherwise ISO-system cannot use drivers
Note: firadisk is created by the brilliant ”karyonix” – and is a “freeware driver”
title Launch ERD 2k/WinXP/2k3
find --set-root --ignore-floppies /FIRADISK.GZ
map --mem /FIRADISK.GZ (fd0)
map --hook
find --set-root --ignore-floppies /ERD50.iso
map --mem /ERD50.iso (0xff)
map --hook
chainloader (0xff)
Method two is used to ISO-files based on NT6-system (Vista/Win-7 or server-2008) and to plenty more ISO-files (Linux/isolinux and EasyBoot-ISO-file as well)
Method two run ISO from ram (map –mem)
However, as you having problem with this “ERD60x86Vista.iso” using this method – I can guarantee you that this is not a genuine NT6-system.
It’s probably a NT5-system.
Look inside ISO-file for a folder i386 (can be renamed but should then have a setupldr.bin inside renamed folder i386).
And if folder “Boot” and “sources” and file BOOTMGR isn’t present then it is not a genuine NT6-system.
It happens from time to time that you find ISO-file on Internet that is presented as a NT6-system but in reality it is a kind of NT5-system.
And launching such system using method below is doomed to fail.
title Launch ERD x86 for Vista
find --set-root --ignore-floppies /ERD60x86Vista.iso
map /ERD60x86Vista.iso (0xff) || map --mem /ERD60x86Vista.iso (0xff)
map --hook
chainloader (hd32)
boot
Last method is what I use in my script to launch NT6-systems (Vista/Win-7 or server-2008) and some rare Linux/isolinux-ISO-files and EasyBoot-ISO-file 
Anyway look inside ERD65x86W7.iso and you find folders typically: “Boot”, “sources” and file BOOTMGR (more folders and files can be present depending how “PE-system” is designed to be used).
title Launch ERD x86 for Windows 7 / 2k8
find --set-root --ignore-floppies /ERD65x86W7.iso
map /ERD65x86W7.iso (hd32)
map --hook
chainloader (hd32)
boot
The main difference between method 2 and 3 is that method 3 skip loading ISO to ram.
Because NT6-PE-systems automatically reads in files into RAM and execute anyway.
If using method-2 ISO is first loaded to RAM and the NT6-system then load system-files one more time into RAM and execute.
What is the point using method two you may ask?
Well this is discussed frequently on Internet among gurus but I have never noticed that method two is a safer way to launch ISO-file based on NT6-system.
And remember that using method two also consume at least twice the amount of RAM to run.
Okay not a big problem these days – but it also takes a couple of extra seconds more to launch using method two.
However, in some cases it can be a good idea to launch ISO to RAM (Linux/isolinux or similar).
Note: Things are changing continuously – tomorrow new ISO-files is constructed – there are new things out there every day – I’ll be in touch
I like fast launching of PE-systems so I stick to method 3 which also is what you get when using my scripts.
Regards balder
Edited by balder on Jan. 19 2011,02:43
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 7
|
CDMaker
Group: Members
Posts: 16
Joined: Dec. 2006
|
|
Posted on: Mar. 02 2011,05:47 |
|
|
sorry for out of forum.
Due to sickness I was completely on bed .... now I am on my way
Guru (balder)I am facing very different experience, my office system does not boot from 1TB HDD (WD My Passport Essential SE)
I have format it with your latest script (feb 01-2011) in both FAT32 and NTFS but no success.
I have try RMPrepUSB ... No success
I have try Flashboot ...No success
I have try WinSetupFromUSB ... No success
This System can boot from other 1GB, 2GB, 8GB flash drives, 40GB laptop HDD, 40GB USB HDD.
I have checked on other systems they are booted from 1TB HDD.
now I am confused & need your help. Kindly guide me, which utility/format I have to choose and format my drive to make it bootable. I need these partition:
1- Bootable. (FAT32)
2- Portable/working. (NTFS)
3- Backup/Data (NTFS)
Previously I distributed 100GB:200GB:700GB
|
|
|
|
| Post Number: 8
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Mar. 02 2011,07:57 |
|
|
@CDMaker
Quote: ”Guru balder”
He, he don’t say to much – he, he I might get “screwed up”
Quote: ”which utility/format I have to choose and format my drive to make it bootable”
Well by several reasons it can be difficult to pin point the “perfect tool” to use in this case.
However, if I where in your position I probably would test using the in Windows built-in harddisk configuration tools.
Don’t forget to set partition 1 as “Active”.
You can then from this point, modify boot-sector (if wanted) to what ever you like (grub or whatever).
Important note: Watch out for “hided” partition – it’s possible you have a “hided” first partition that you haven’t discovered
I once had such problem with a harddisk with a “hided” partition.
I didn’t noticed this and continue to make “first” visible partition active – of course without any success 
As a second choice I probably would use this tool HERE
If you haven’t tested – please do
-------------------------
Quote: “Due to sickness I was completely on bed”
Glad to see that you are recovering
He, he each time my grandchild (2 years old) visits me – I always 3 days later get the flu
Can there be a connection 
Regards balder
--------------
Download complete set of scripts including help file HERE
Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
| Post Number: 9
|
CDMaker
Group: Members
Posts: 16
Joined: Dec. 2006
|
|
Posted on: Mar. 03 2011,00:32 |
|
|
thanks for your reply ....GURU hehehehehehehe
Quote: "Important note: Watch out for “hided” partition – it’s possible you have a “hided” first partition that you haven’t discovered
I once had such problem with a harddisk with a “hided” partition."
I have My passport Essential SE which has a UDF virtual CD(700MB) in its firmware we cannot remove it but disable it. I had already talked to WD but they did not give any positive response to remove it. I have check in both condition but my office system does not boot from this HDD. It means there is the problem or something new in HDD firmware which does not support this type of computer BIOS
Quote: "Don’t forget to set partition 1 as “Active”."
Yes, I did it,
Quite: "As a second choice I probably would use this tool HERE"
This utility does not support my HDD
I will find some other way to solve this problem, may I can first boot from CD (Plop Boot Manager) than choose boot from USB. let me check may be it is work!
Edited by CDMaker on Mar. 03 2011,00:34
|
|
|
|
| Post Number: 10
|
CDMaker
Group: Members
Posts: 16
Joined: Dec. 2006
|
|
Posted on: Apr. 19 2011,03:17 |
|
|
GURU can you add one more line (at least) in you signature that whats New! in your Script ... Please
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
