|
|
| Post Number: 1
|
allgames71 
Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted on: Jul. 24 2012,04:47 |
|
   |
hello balder ,
I am wondering is there a way for Easyboot to boot up a .VHD file ? If possible , live XP , Win7 and Win8 OS is possible on a usb harddisk.
Thanks
|
 |
|
|
| Post Number: 2
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 24 2012,07:12 |
|
 |
@allgames71
Quote: "I am wondering is there a way for Easyboot to boot up a .VHD file"
Important! You need the file 'bootmgr' and BOOT-folder on the root of USB drive to launch VHD-file (but that is obvious) 
I would solve it this way:
1. Create your VHD-system with its VHD-file and folder BOOT on the root of USB drive (test that it works)
2. Copy floppy image 'setupnt6.img' from my folder 'balder/ USB_Resources' to folder EZBOOT and use menu command in EasyBoot menu: Â run setupnt6.img
3. Open 'setupnt6.img' in folder EZBOOT (I used UltraIso) and extract file 'menu.lst' to some temporary place.
4. Modify 'menu.lst' (use notepad) and replace ' bootmgr' to both text-lines with 'bootvhd'
5. Save changes to file and replace 'menu.lst' inside 'setupnt6.img' with this modified 'menu.lst'
6. Save changes to 'setupnt6.img'.
7. Change name to 'bootmgr' on USB drive to 'bootvhd'
8. Only tick 'Joliet' when creating ISO in EasyBoot
9. Use my script 'easyboot-usb_v2.script' and in script tick 'Force script to NOT format USB drive'.
You are also advised to in 'Chose visual boot option' chose 'Launch ISO\image-file directly'
10. When script finally asks for ISO-file you chose ISO created by EasyBoot.
Note: Remove files and folders that you have in folder disk in EasyBoot, only keeping folder EZBOOT before you create ISO in EasyBoot.
It's pointless to have these files and folders there as we cannot reach these from inside of ISO-file (EasyBoot-ISO-file)
However you can still launch WinPE from inside of EasyBoot ISO-file if these WinPE are based on NT6-system (typically Msdart60 etcetera)
I know that above works as I have used process (tutorial) above - already discussed  HERE 
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: 3
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 24 2012,07:51 |
|
|
hello balder ,
quote : "I know that above works as I have used process (tutorial) above - already discussed"
Yes balder , we've discuss this before. But I'm always forgot things. So I'll look back the previous discussion and solve my work.
Thanks a lot.
|
|
|
|
| Post Number: 4
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 29 2012,12:50 |
|
|
hello balder ,
I've a image file ... xp-1.img , which is a .vhd file. It's a bootable Live XP file.
I boot it this way :
title Boot XP from Image - XP-1.img - WinVBlock driver - 3067 MB
find --set-root --ignore-floppies /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
It boots and works perfect. But I don't know how to add it to Easyboot menu command like :
run xp-1.img
Of course it failed and stop at boot.
The thing is I don't want to boot it by menu.lst , I want to add it to Easyboot menu as I've a .ezb file including :
Live Windows XP (menu command :  ??)
Live Windows 7 (menu command : run win7usb.img)
Live Windows 8 (menu command : run setupnt6.img)
Thanks in advance.
|
|
|
|
| Post Number: 5
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 29 2012,13:45 |
|
|
@allgames71
Quote: "I don't know how to add it to Easyboot menu command"
You have to options to solve this:
A. Create a new 'grub-kicker-image'
In my opinion this is an interesting script I created, as it also can create different sizes to Floppy Images including use different boot-sectors (grub or DOS or NT-boot sector)
B. Or modify an existing 'grub-kicker-image'
I would test this (create a new floppy image with grub boot sector):
1. Use my script 'easyboot kicker-image.script'
2. In upper left corner you have 'Create new Grub-Floppy Image'. Set parameters in that section (write a name in text-box like xp-vhd and chose size to 0,32Mb and set path to where to create new 'kicker-image' which would be folder EZBOOT. Don't tick g-zip to create Image.
3. In the right pan of window you write in the lines that you need to 'menu.lst', which is these lines:
find --set-root --ignore-floppies /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Attention! You must also to copy 'xp-1.img' to folder disk1 in EasyBoot
Note: you don't need the line 'title' as grub command lines is executed at once from inside of the 'grub-kicker-image'
3. In EasyBoot menu you use menu command: Â run xp-vhd.img
Another way is to open an existing grub-kicker-image (use the 'setupnt6.img')
Use the same method to modify 'menu.lst' as described in post nr;2 Â but put in text-lines deleting existing text-lines:
find --set-root --ignore-floppies /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Save modified floppy image in folder EZBOOT with name 'xp-vhd.img' and use menu command: Â run xp-vhd.img
Test and see if it works better this way
--------------------
He, he you sure are working hard with those vhd-files
Keep it up
regards balder
Edited by balder on Jul. 29 2012,14:05
--------------
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: 6
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 29 2012,15:07 |
|
|
hello balder ,
1. I copy the "C:\Easyboot\disk1\ezboot\setupnt6.img" to "C:\Easyboot\disk1\ezboot\xp-vhd.img"
2. Modify the menu.lst from :
find --set-root --ignore-floppies /bootmgr
chainloader /bootmgr
To :
find --set-root --ignore-floppies /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
3. Copy XP-1.img to "C:\Easyboot\disk1" and use menu command "run xp-vhd.img"
4. Create Easyboot :
C:\Easyboot\iso\mydisk.iso
5. User WinBuilder > EasyBoot-USB-v2 to make iso to USB harddisk
An error message pop-up with message at boot :
----------------------------------------------------------------------
GRUB4DOS 0.4.5b 2011-06-16, Mem 621k/2814M/1024M, End : 356204
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub>
----------------------------------------------------------------------
|
|
|
|
| Post Number: 7
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 29 2012,16:10 |
|
|
hello balder ,
A picture of the existance files in my 8GB usb-stick.
Before I just mentioned the xp-1.img file. But how about the other files , how to handle with them ?
Thanks
|
|
|
|
| Post Number: 8
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 29 2012,16:11 |
|
|
hello blader
Attached Image
|
|
|
|
| Post Number: 9
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 30 2012,03:03 |
|
|
@allgames71
Quote: "An error message pop-up"
We are now in a 'test-and-trial-position' - which is not that funny but unfortunately sometimes a necessary part of the process 
First step is to check this:
When you boot USB-stick there might be some vital information that shows up (I'm desperately interested of that information - if it shows up of course).
Grub may show a list of 'boot sectors' - typically:
Try (hd0,0)
Try (hd0,1)
Try (hd0,2)
Try (hd0,3)
Etcetera.....
I'm interested if such list of boot sectors is searched by grub during USB stick boot sequence
---------------------
Quote: "But how about the other files"
Eeee - what files
Didn't we solved this is post nr;2 Â (launch Win7.vhd using modified 'setupnt6.img')
However I also noticed you seems to have a Win8.vhd-file
If this is the case, you need to rename 'bcd-file' in folder 'boot' that launch (points to) win8.vhd and also hex-edit file 'bootmgr' related to that bcd-file
Rename bcd-file that points to Win8.vhd (use a name like bc1 or whatever) and then hex-edit 'bootmgr' to point to bc1-file instead of the standard-name bcd, in folder boot (also change name to this hex-edited 'bootmgr' to bootwi8 - or whatever name you prefer).
It's obviously you must have separate 'boot-files' to win7.vhd and win8.vhd as you cannot use the same 'bootmgr-file' and the same bcd-file to both vhd-files 
Make a copy of setupnt6.img and rename it to win8vhd.img
Finally modify menu.lst in win8vhd.img to point to 'bootwin8' (name I sugested above), which means you modify 'menu.lst' (use notepad) and replace ' bootmgr' to both text-lines with 'bootwi8'
When win8vhd.img is launched in EasyBoot menu, grub launch bootwin8 that points to bc1 in folder boot which then launch win8.vhd
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: 10
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Jul. 30 2012,11:18 |
|
|
hello balder ,
The below picture is my USB harddisk partition.
Partition 1 : Windows 7 USB Edition x86 (F:)
Partition 2 : Win8USB (G:)
Either Win7USB or Win8USB boots normal to majority of the other computers. I've got no problem in them as I rename "bootmgr" to "boot7" , which matching the win7usb.img (chainloader /boot7). So it would not be confused with Win8USB boot file.
My problem is WinXPUSB , as I made individually WinXPUSB in a usb-stick , it contains the follwoing files and boot normally :
boot
bootfont
grldr
menu.lst
NTDETECT
ntldr
RUN
xp-1.img (the entire Windows XP)
the menu.lst is :
title XP-1.img - WinVBlock FILEDISK - 3067 MB
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
So I copy files from usb-stick to usb harddisk "F:" , which contains :
1. Win7USB files
2. Easyboot - contains Win7/8PEs , Partition Tools, Backup & Recovery Tools ......
Files copied are like those in the picture :
boot
grldr
NTDETECT
ntldr
RUN
XP-1.img
So the menu.lst becomes :
--------------------------------------------------------------
default 0
timeout 10
gfxmenu = /wallpaper/boot.gfx.gz
title Launch EasyBoot
find --set-root --ignore-floppies /iso/iso.iso
map /iso/iso.iso (hd32)
map --hook
chainloader (hd32)
title XP-1.img - WinVBlock FILEDISK - 3067 MB
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
--------------------------------------------------------------
As I said before , I don't want the WinXPUSB be seperated , I want to to be like this :
--------------------------------------------------------------
default 0
timeout 10
gfxmenu = /wallpaper/boot.gfx.gz
title Launch EasyBoot
find --set-root --ignore-floppies /iso/iso.iso
map /iso/iso.iso (hd32)
map --hook
chainloader (hd32)
--------------------------------------------------------------
It means , like Win7USB & Win8USB , the WinXPUSB should be included in the Easyboot menu named LiveWin.ezb :
WinXPUSB (run xp-vhd.img)
Win7USB (run win7usb.img)
Win8USB (run setupnt6.img)
I try to make the WinXPUSB in Easyboot like this :
1. copy xp-1.img , boot , NTDETECT , ntldr , RUN to "C:\Easyboot\disk1\ezboot"
2. copy setupnt6.img to xp-vhd.img and modified :
find --set-root --ignore-floppies /bootmgr
chainloader /bootmgr
To :
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
But it failed to boot as above mentioned , I've changed line 4 "root (hd0,0) to root (hd0,1) or root (hd0,2) . But also fail to boot
Please help
Attached Image
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
