|
|
| Post Number: 31
|
allgames71 
Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted on: Aug. 15 2012,18: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
Attached Image
|
 |
|
|
| Post Number: 32
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 16 2012,06:50 |
|
 |
@allgames71
Quote: "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
--------------
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: 33
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Aug. 16 2012,08: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.
|
|
|
|
| Post Number: 34
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 16 2012,11:31 |
|
|
@allgames71
Quote: "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
--------------
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: 35
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Aug. 16 2012,12: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
|
|
|
|
|
|
|
© 2002-2025 EZB Systems, Inc.
|
|
|
