|
Post Number: 11
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 30 2012,12:42 |
|
|
@allgames71
Quote: "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
-------------- 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: 12
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted 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
|
|
|
|
Post Number: 13
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 30 2012,15:41 |
|
|
@allgames71
But 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
Edited by balder on Jul. 31 2012,01:42
-------------- 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: 14
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted 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 ?
Attached Image
|
|
|
|
Post Number: 15
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 31 2012,07:29 |
|
|
@allgames71
I'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
-------------- 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: 16
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted 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
|
|
|
|
Post Number: 17
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jul. 31 2012,12:59 |
|
|
@allgames71
Quote: "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
-------------- 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: 18
|
|
Post Number: 19
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 01 2012,06:33 |
|
|
@allgames71
I am a little bit occupied this afternoon Starting 'investigating things' during tomorrow
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: 20
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Aug. 02 2012,06:18 |
|
|
@allgames71
I 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
Edited by balder on Aug. 02 2012,11:16
-------------- Download complete set of scripts including help file HERE Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|