Topic: How to run .VHD file in Easyboot
started by: allgames71
Posted by allgames71 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
Posted by balder on Jul. 24 2012,07:12
@allgames71Quote: "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
Posted by allgames71 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.
Posted by allgames71 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.
Posted by balder on Jul. 29 2012,13:45
@allgames71Quote: "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
Posted by allgames71 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>
----------------------------------------------------------------------
Posted by allgames71 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
Posted by allgames71 on Jul. 29 2012,16:11
hello blader
Posted by balder on Jul. 30 2012,03:03
@allgames71Quote: "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
Posted by allgames71 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
Posted by balder on Jul. 30 2012,12:42
@allgames71Quote: "As I said before , I don't want the WinXPUSB be seperated"
I totally agree that EasyBoot do have a nice 'look' including option to jump between sub-menu(s) etcetera...
Anyway test this solution:
Quote: "as I made individually WinXPUSB in a usb-stick , it contains the following files and boot normally"
1. Create the same structure to first partition (drive letter F:) and test it works with menu.lst, using text-lines as described by you:
title XP-1.img - WinVBlock FILEDISK - 3067 MB
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Make sure XP.vhd do launch correctly
2. Open notepad and insert these text-lines:
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Save changes in notepad to drive letter F: but use name WinXP.lst to text-file
Note: in this case you create a 'menu.lst' with the name WinXP.lst (you can of course as option also modify a existing 'menu.lst' and then simply rename text-file 'menu.lst' to WinXP.lst)
3. 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 /WinXP.lst
configfile /WinXP.lst
Save modified floppy image in folder EZBOOT with name 'xp-vhd.img' and use menu command: run xp-vhd.img
And how do this work then you may ask
It works like this:
A. You launch grub-kicker-image ' xp-vhd.img' from EasyBoot menu
B. ' xp-vhd.img' starts looking for configfile WinXP.lst and is launched by grub
C. Configfile WinXP.lst launch WinXP exactly in the same way as the structure you are convinced to work correctly
I quote: "as I made individually WinXPUSB in a usb-stick , it contains the following files and boot normally"
---------------------------
Quote: "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."
Okay - he, he again I underestimate you
- I have to accept you are smart (or smarter than me) - excellent solution to this issue from you regards balder
Posted by allgames71 on Jul. 30 2012,15:12
hello balder ,This first time I read your instruction , I can understand what to do then.
But when I test it , it boot fail and stop with the following error message :
-----------------------------------------------------------------------
Starting cmain() ... (ho0,0)
probed C/H/S =391/255/63, probed total sectors = 6281415
Filesystem type is ntfs, partition type 0x07
Will boot NTLDR from drive=0x80, partition=0x0(hidden sectors=0x3f)
-----------------------------------------------------------------------
Please help
Posted by balder on Jul. 30 2012,15:41
@allgames71But did WinXP.vhd boot when using your method in step 1 in post nr;11:
"1. Create the same structure to first partition (drive letter F:) and test it works with menu.lst, using text-lines as described by you:
title XP-1.img - WinVBlock FILEDISK - 3067 MB
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Make sure WinXP.vhd do launch correctly
Did above work correctly from USB harddisk unit - if not - it's pointless to go to step 2 in post nr;11
You must first make sure WinXP.vhd really boot and run correctly before we try to launch from EasyBoot menu
Note: it is not the same to launch WinXP from USB harddisk as from USB stick\thumbdrive - you cannot be sure WinXP.vhd behave correctly from USB harddisk unit
I tell you this as there are some indications to that direction in message:
"probed C/H/S =391/255/63, probed total sectors = 6281415
Filesystem type is ntfs, partition type 0x07
Will boot NTLDR from drive=0x80, partition=0x0(hidden sectors=0x3f)"
regards balder
Posted by allgames71 on Jul. 31 2012,05:13
hello balder ,1. As I copy all the files from the 8GB usb stick to drive K: , I test XP boots normal with this menu.lst :
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
2. From "C:\Easyboot\disk1\ezboot" , I copy the "setupnt6.img" to "xp-vhd.img"
3. In the xp-vhd.img's menu.lst , I change to :
find --set-root --ignore-floppies /WinXP.lst
configfile /WinXP.lst
4. In drive K: , I make a WinXP.lst
# Sector-mapped disk
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
When I boot up with the "xp-vhd.img" option , the error message still comes up at the very beginning. It freeze at the error message and will not boot XP :
------------------------------------------------------------------------------
Starting cmain() ... (hd0,0)
probed C/H/S =391/255/63, probed total sectors = 6281415
Filesystem type is ntfs, partition type 0x07
Will boot NTLDR from drive=0x80, partition=0x0(hidden sectors=0x3f)
------------------------------------------------------------------------------
Any help ?
Posted by balder on Jul. 31 2012,07:29
@allgames71I'm pulling out the rest of my hair in a desperate attempt to solve this strange problem
This is out of any range of strange behaviour - what is going on
Let's dig into to 'investigate and troubleshoot' scenario
1. Modify 'WinXP.lst' to
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader --raw /ntldr
If not wNot working - go to step 2
2. Replace grldr in 'xp-vhd.img' with the one you use on the root of USB drive
Note: also modify 'menu.lst' in 'xp-vhd.img' to:
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
3. Test if using the same 'grldr' in 'xp-vhd.img' improves result - if not - go to step 4
4. Modify menu.lst in 'xp-vhd.img' to;
find --set-root --ignore-floppies /menu.lst
configfile /menu.lst
Yes this means you from EasyBoot goes back to menu.lst on USB drive, getting this menu;
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
Test if WinXP.vhd can be launched correctly
--------------------------
Another solution could be to launch EasyBoot in the 'normal mode' (launch EasyBoot from a FAT32-partition, avoiding run ISO of EasyBoot as this involves a different 'memory match' that might create problems.
However this means you need a FAT32-partition and also includes copying folder EZBOOT to this FAT32-partition
You can launch EasyBoot with grub menu from the first partition ('boot partition' that have needed NTFS as filesystem to support VHD-files):
title Launch EasyBoot
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
Note: You can of course skip the line 'title' and directly launch Easyboot - like this:
find --set-root /ezboot/ezldr
chainloader --raw /ezboot/ezldr
This launch EasyBoot without the need to use ISO-file of EasyBoot, but must be run from FAT32-partition (a tiny small partition)
Test above to notice of any improvements
He, he you have some work before you gone through all 'investigate and troubleshoot' scheme above
regards balder
Posted by allgames71 on Jul. 31 2012,11:57
hello blader ,I've tried your way 1,2,4 :
Method 1..... Modify 'WinXP.lst' to ...........
result to non-boot with the following error message like before :
--------------------------------------------------------------------------------
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>
-------------------------------------------------------------------------------
Method 2 & 4 ..... Replace grldr in 'xp-vhd.img' & Modify menu.lst in 'xp-vhd.img' to;
same result to computer reboot when choosing the xp-vhd boot
又
Method Final ...... Another solution could be to launch EasyBoot in the 'normal mode'
I don't want to have another partition in this usb-harddisk , as there's already 3 partitions in it.
I'm now uploading the xp-1.img to a web file hosting , it takes hours. Tomorrow I'll send you a link of this file to download.
It's better to get it and practice it , rather than to guess it.
Thanks for help
Posted by balder on Jul. 31 2012,12:59
@allgames71Quote: "Tomorrow I'll send you a link of this file to download."
Okay, I will do my very best to figure out if there is a solution to this mystery
You can use messenger in EasyBoot to give me link to download
I have a 500 GB Buffalo USB harddisk that I can 'play' with
regards balder
Posted by allgames71 on Aug. 01 2012,06:12
hello balder , Here are the XP-1.iso download link
< http://www.mediafire.com/?tztmyvcjqj3oos3 >
< http://www.mediafire.com/?fkhw67dooojaho1 >
< http://www.mediafire.com/?pac6kqzo9yq7slp >
Total 562MB
Thanks
Posted by balder on Aug. 01 2012,06:33
@allgames71I am a little bit occupied this afternoon
Starting 'investigating things' during tomorrow regards balder
Posted by balder on Aug. 02 2012,06:18
@allgames71I have run a lot of different test to find a reliable solution, and hopefully this works to you to as well
This is my conclusions so far:
A. It is possible to launch XP-1.img (the XP-1.img - WinVBlock RAMDISK - 3067 MB) from EasyBoot menu.
To make it work, you launch (as usual) the ISO-file of EasyBoot (must use ISO as you use NTFS to file-system).
In EasyBoot menu you use menu command: bcdw to 'grub-kicker-image' (the modified 'setupxp.img')
The menu.lst inside 'setupxp.img' can be:
find --set-root --ignore-floppies --ignore-cd /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
OR
find --set-root --ignore-floppies --ignore-cd /XP-1.img
map --mem /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Note1: I was forced to use --mem as I mostly got 'Blue-Screen-Of-Death' (BSD) when trying to launch XP-1.img
However as I was forced to use '--mem' I decided to also run g-zip to XP-1.img
Note2: I used my script 'easyboot cab.script' and pushed on button 'g-zip' in script and followed instructions.
This is what I finally did:
1. Formatted USB hard-disk partition one to NTFS
2. Created EasyBoot menu: bcdw setupxp.img
Used this text in menu.lst in setupxp.img (note extension 'gz'):
find --set-root --ignore-floppies --ignore-cd /XP-1.img.gz
map --mem /XP-1.img.gz (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
Note: It took 3 minutes to make XP up and run as it takes some time to load file to RAM before launch XP
3. Created ISO in EasyBoot only ticking 'Joliet'
4. Used my script 'easyboot-usb_v2.script' ticking 'Force script to not format USB drive'
And pointed to EasyBoot ISO-file when asked
5. Copied 'XP-1.img.gz' (I used the g-zipped file to avoid BSD) and also avoid the problem with ' error 60 contiguous shape' to image-file
Attention! You don't need any other files on the root of USB drive
However, if it is possible for you to use menu.lst without --mem like this:
find --set-root --ignore-floppies --ignore-cd /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
If it works, use above in your case - but I don't understand I got BSD
Or maybe I do understand that BSD-behaviour as launching NT5-system (WinXP is an typically NT5-system) in normal case includes getting BSD when directly launched from ISO\IMG-file
Take a look into this thread < HERE >
Could this be to any help regarding using a vhd-file
------------------
Test and see if solution above works correctly (using bcdw-command in EasyBoot menu)
Note: bcdw doesn't 'lock' any memory area and also doesn't 'lock' you to any file-system as far as I can understand
regards balder
Posted by allgames71 on Aug. 02 2012,13:39
hello balder ,I tried your per instruction and both FAIL TO BOOT , BUT REBOOT RIGHT THE WAY1. a) 'grub-kicker-image' = "setupxp.img" with menu.lst :
find --set-root --ignore-floppies --ignore-cd /XP-1.img
map /XP-1.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
b) with menu command "bcdw setupxp.img"
c) xp-1.img with other xp files in usb-harddisk root folder
2. a) 'grub-kicker-image' = "setupxp.img" with menu.lst :
find --set-root --ignore-floppies --ignore-cd /XP-1.img.gz
map --mem /XP-1.img.gz (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
b) with menu command "bcdw setupxp.img"
c) user 'easyboot cab.script' and pushed on button 'g-zip' in script and followed instructions , then I've got a "xp-1.img.gz"
xp-1.img.gz in usb-harddisk root folder
Please tell me what I was wrong , as you can get a BSD or to avoid the BSD with "--mem".
I have no chance to boot it up , even I can't see the XP loading hardware screen !!!
Thanks
Posted by balder on Aug. 02 2012,15:23
@allgames71Quote: "I have no chance to boot it up , even I can't see the XP loading hardware screen !!!"
Please read in your message, to see if it helps
regards balder
Posted by allgames71 on Aug. 03 2012,09:32
hello balder ,quote : "Please read in your message, to see if it helps
"
I don't understand what this mean , do you mean I've to wait for your test. OR I've to read your message once again ?
Thanks
Posted by balder on Aug. 03 2012,14:24
@allgames71Well I have sent you a message using EayBoot messenger
Haven’t you received such message with download links
There are files and a brief instruction to test my version of EasyBoot menu
I also have done some more test – and all succesfull if I used --mem in menu.lst
I always get BSD-screen if not using –mem in grub-kicker-image
I also noticed the importance of a ‘clean structure’ to USB drive (especially if using USB stick)
Anyway – did you or did your not receive message with download links in Easyboot message
Note, I’m not at my home residence for two days – will be back on Sunday or something
Regards balder
Posted by allgames71 on Aug. 04 2012,01:30
hello balder ,quote : "Well I have sent you a message using EayBoot messenger"
Sorry balder , I haven't heard about what is Easyboot messenger. I never know that there is a messenger in Easyboot. If you sent it to me , so where can I get it ?
Thanks for your instruction or can email me to allgames71@gmail.com
Thanks a lot
Posted by balder on Aug. 04 2012,16:06
@allgames71Quote: "Sorry balder , I haven't heard about what is Easyboot messenger"
In the upper right corner you have in EasyBoot 'Your Messenger'
I use this 'messenger' when sending some 'secret' messengers that should only be read by that particular person
Note: I also have used your e-mail
Hopefully you got the message this time
Regards balder
Posted by allgames71 on Aug. 06 2012,14:20
hello balder ,A great thanks to you for your help , successfully I made the xp bootable from within Easyboot menu and not from add booting to the menu.lst
1. from the allgames71.gho , I extract only the xp.img and xp_mem.img and test only the xp.img
2. I put the xp.img in "C:\Easyboot\disk1\ezboot" and use menu command "bcdw xp.img"
3. Then make "mydisk.iso" and check "Joliet" only , use Easyboot-usb_v2 and place xp-1.img in the root of my usb-hd
4. It boots up right the way to xp desktop successfully at the first trial. Really nice.
My CURIOSITY
1. It seems to be no difference of the menu.lst in your xp.img , with the one you taught me before (post number 11) . I'm wondering what's the different between them ? It seems to be exactly the same. Was I doing anything wrong before to waste your time ? Or am I now making it successfuly by luck ?
2. I test with xp.img and not xp_mem.img as I know it takes a lot of time to boot . Fortunately I have not encounter the BSD like you .
a) My motherboard is Asus M4N68T-M V2 , 4GB Ram , AMD Athlon™ IIx2 255 Processor (I haven't try the Intel motherboard yet)
b) There's an easy way to make XP universally boot in any computer except those with AHCI / Raid , is to throughly erase all the drivers with a batch file everytime before shutdown .
c) For those motherboard , specially notebooks with AHCI /Raid , you can also add all the AHCI /Raid drivers in xp by offline .
------------------------------------------------------------------------------------------
------------------------------------
I'm now playing with Win8 vhd , may be I'll need your help soon.
Anyway , thanks again and again to you , balder . You did a great help , thanks.
Posted by allgames71 on Aug. 06 2012,15:03
hello balder ,From the file you sent me , you use the background picture "BACK7.BMP" , which is 1024 x 768 size .
But when I use the 1024 x 768 size as BACK.BMP and save , it has an error message .
If it's inconvient to talk about this in here , please email me. Thanks
Posted by allgames71 on Aug. 06 2012,15:20
hello balder ,Sorry to border you , but I like your BACK7 wallpaper and the self-made button very much , I don't know how to make it.
Wonder if you can send me also your original Easyboot xp file to me ? So I can learn it myself.
Thanks a lot
Posted by balder on Aug. 06 2012,16:27
@allgames71Post nr; 27
Quote: "successfully I made the xp bootable from within Easyboot menu and not from add booting to the menu.lst"
Well - I made a wild guess
that something elementary must be wrong here - that's why I sent you the 'original file' to see if it worked better that way - and it did Quote: "Was I doing anything wrong before to waste your time ? Or am I now making it successfuly by luck?"
I really cannot tell
Remember that you can create you own 'grub-kicker-image' using my script: 'easyboot kicker-image.script'
Script has option to create DOS-floppy images as well and also creates such floppy images in several sizes as well (same to 'grub-kicker-image)
Quote: "Wonder if you can send me also your original Easyboot xp file to me ? So I can learn it myself"
I use the setupxp.img in folder 'balder/USB_Resources" and extract text-file 'menu.lst' to some place and edit text in that file followed by inject it back to setupxp.img (I use 'Save as' in UltraIso to a different name like xp-1.img and save it to folder EZBOOT of course)
This means you already have the 'original floppy image-file in your position
------------------------------------------
Post nr; 28
Quote: "But when I use the 1024 x 768 size as BACK.BMP and save , it has an error message"
It looks to me you have set background size to '640x480'!!!
Please in EasyBoot press 'Options>>Configuration' and set 'Screen Resolution' to 1024x768 and also set 'Screen mode' to 256 Colour(8bits) and finally press 'OK' to confirm settings!
Note: I use this resolution 1024x768 and colour mode 256 Colour(8bits) to most of my builds!
Attention! Some 'mini-laptops' with poor graphic support in 'BIOS-mode' (when booting) only support 800x600 in screen resolution in combination with 256 Colour(8bits).
Using 800x600 in screen resolution and 256 Colour(8bits) is close to bullet-proof to work in any computer (including computers with poor graphic support in 'BIOS-mode').
But as said, I use the more elegant 1024x768 in combination with 256 Colour(8bits).
Take also attention to that size and colour mode must exactly match the background picture and it must be an BMP-picture
---------------------------
Post nr; 29
Quote: "Wonder if you can send me also your original Easyboot xp file to me ? So I can learn it myself."
As it is summer-time I'm performing some maintenance to my home residence so 'time is tight'
I have to use my back-up harddisk that I have somewhere to find these files - it takes some time...
In less than two days I can include a download link with files and some brief instruction how I did the 'buttons' to appear in picture with right colour mode
----------------------------------
EDIT!
On request from @allgames71 I have put some backgrounds together in a zip-file for download
Nothing fancy, only some simple example what I use as background
Download backgrounds from < HERE >
-----------------------------
regards balder
Posted by allgames71 on Aug. 15 2012,14:31
hello balder ,I've made a bootable Win8 VHD file , unlike before , the so called .vhd file is with folders at the root of the primary active partition :
Program Files
ProgramData
Windows
Users
boot8 (originally "bootmgr" with setupnt6.img the same name in it's menu.lst)
It boots ok with no problem.
---------------------------------------------------------------------------------
Now I made a new "win8.vhd" single file on the primary active USB partition
1. In Easyboot , i.e. "C:\EasyBoot\disk1\ezboot" , I edit the menu.lst in setupnt6.img to "chainloader /boot8vhd"
2. Copy "boot" folder to USB parition
3. Copy "bootmgr" to USB partition and name it as "boot8vhd"
4. Use menu comand "run setupnt6.img" , when make iso , I check "Joilet"
5. Use WinBuildr > EasyBoot-USB_v2 and tick 'Force script to NOT format USB drive'.
But when I boot it up , it comes out with an error message and stop :
---------------------------------------------------------------------------------
GRUB4DOS 0.4.5b 2011-06-16, Mem: 621K/2814M/1024M, eND: 3561DB
[ 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>
---------------------------------------------------------------------------------
The files and folder structure is like this , any help ? Thanks
Posted by balder on Aug. 16 2012,02:50
@allgames71Quote: "But when I boot it up , it comes out with an error message and stop"
This problem seems to be similar to issue in post nr,27 in this topic
First I must ask you to do some 'basic forensic' to make sure we do not 'walks in circles'
1. Open 'setupnt6.img' and make sure 'menu.lst' look like this:
find --set-root --ignore-floppies /boot8vhd
chainloader /boot8vhd
3. Modify 'menu.lst' inside 'setupnt6.img' to look like this:
find --set-root --ignore-floppies /boot8vhd
chainloader --raw /boot8vhd
Test and see if any improvements can be noticed
2. Insert these lines into existing menu.lst that is on the root of USB drive:
title launch Win8vhd
find --set-root --ignore-floppies /boot8vhd
chainloader /boot8vhd
Test that it launch using the 'menu.lst' that also launch ISO-file of EasyBoot
The point is to make sure nothing is wrong with the 'basic structure' regarding file 'win8.vhd' and folder 'BOOT' and file 'boot8vhd'
-----------------------
Strange is that this shouldn't be any problem at all - but in you case - by some reason I have difficulties to understand - it seems to create troubles
regards balder
Posted by allgames71 on Aug. 16 2012,04:31
hello balder ,1. When use the method to modify menu.lst inside 'setupnt6.img' like :
find --set-root --ignore-floppies /boot8vhd
chainloader --raw /boot8vhd
When boot , it hangs up right the way and even can't start Win8.
-----------------------------------------------------------------
2. When use the method to modify menu.lst inside 'setupnt6.img' like :
find --set-root --ignore-floppies /boot8vhd
chainloader /boot8vhd
When boot , I got a blue screen right at boot with error message :
Recovery
Your PC needs to be repaird
There is an invalid object in the Boot Configuration Data store.
Error code : 0x0000000f
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a disc or USB device)
contact your system administrator or PC manufacturer
Thank you.
Posted by balder on Aug. 16 2012,07:31
@allgames71Quote: "When boot , I got a blue screen right at boot with error message :
Recovery"
Okay this shows that 'setupnt6.img' (launched from EasyBoot menu) is working correctly, but it seems the win8 BOOT-sequence 'walks' into a repair\recovery mode.
I have seen this from Win7_vhd-file as well.
This happens from time to time as we launch VHD-file from an USB drive partition.
However I cannot remember what I did to solve this issue
Anyway my guess is it is related to the file 'bootmgr' (the one you renamed to boot8vhd) and the relation to files in folder 'BOOT'
To sum up...
EasyBoot launch 'setupnt6.img' that correctly then launch 'bootmgr' (boot8vhd)
It works correctly but Win8 seems to flip out and start the 'recovery process'
It can be related to from what partition you launch VHD-file
Another possibility is that you have a NT6-system (Vista\Win7 or Win8 is typically NT6-systems) already installed on the real Harddisk.
And when trying launching boot8vhd on the USB drive partition, by some reason, files in folder BOOT on your real harddisk is executed.
This can be a hard nut to crack
You may need to totally rewrite files to the USB harddisk partition (including the Win8_vhd-file)
Another and a very interesting test would be to use a USB stick instead of USB harddisk unit
I repeat, EasyBoot do what it is supposed to do - launch boot8vhd using 'setupnt6.img'
regards balder
Posted by allgames71 on Aug. 16 2012,08:29
hello balder ,1. I use a clean USB hd with primary active partition for this Win8vhd.
2. Even I don't rename the bootmgr to any other name has the same outcome
3. Even only this USB hd without any internal hd has the same outcome.
Anyway , it's just a test for me for interest. As I've already make WinXP , Win7 & Win8 Live USB HD already. And I wouldn't work on it anymore.
Thanks for your help