|
|
| Post Number: 31
|
balder 
Group: Members
Posts: 1942
Joined: Oct. 2008
|
 |
Posted on: Nov. 01 2011,16:28 |
|
   |
@allgames71
Quote: "so don't waste you time on that"
He, he to late 
--------------------------------------------------
Test this:
Create two primary partitions to your USB harddisk
I used built-in 'Disk Management' in Win7 which is the OP-system I currently run to create and format my partitions.
EDIT: It didn't work out when testing on my 'Buffalo' 2.5" external USB harddisk
Grub cannot 'Mount' partition-2.
Funny it worked to IDE-harddisk connected to USB dock-station?
1. Partition one as FAT32 and active
2. Second primary partition as NTFS not active
Download grub-kicker-image from HERE
Copy kicker-image to folder ezboot
Use menu command in EasyBoot menu: run vhd.img (I used that name to floppy image rename it if you whish)
You of course also need the big VHD-file and folder 'boot' and file bootmgr on the root of second partition as well 
---------------------------------
BartPE is as usual: run /iso/bartpe/bartpe.img
Save changes to EasyBoot menu.
Use script 'easyboot-grub-iso.script' and push directly on button: "Make USB bootable and transfer ISO-build to USB"
You also have a red arrow pointing to that button
DO NOT check: "Force Format to NTFS (Default is FAT32)" in script - use default (FAT32)
Script formats your USB drive letter (first primary partition) automatically and create menu.lst to directly launch EasyBoot menu using folder ezboot on the root of partition one (the active partition).
Script doesn't touch second partition - script is capable to find all your partitions on USB drive and still focus to the first partition as the primary 'target' 
Note: everything that is inside folder disk1 is copied to partition one including (in your case) folder ISO with BartPE etcetera...
I tested and it worked alright to my 46GB harddisk connected with USB dock station.
Very noisy that old harddisk - but works
Could this be the solution for present time, as we cannot use folder ezboot on NTFS file-system?
regards balder
Edited by balder on Nov. 02 2011,05:18
--------------
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: 32
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Nov. 02 2011,14:06 |
|
 |
hello balder,
I haven't start to test your tutorial yet as there's something that I don't understand. What I can understand is :
1. Create First Primary Active FAT32 partition
2. Create Second Primary non-bootable NTFS partition
3. Copy the new grub-kicker-image (vhd.img) to "C:\EasyBoot\disk1\ezboot" with menu command "run vhd.img"
Also copy "VHD-file" and folder "boot" and file "bootmgr" to the second primary NTFS partition.
4. And for BartPE with the menu command "run /iso/bartpe/bartpe.img"
My question is here :
Do you mean there are 2 menu command and 2 menu text like :
run /iso/bartpe/bartpe.img Run BartPE
run vhd.img Win7 USB
Then when boot up the Easyboot menu , you can either choose "Run BartPE" or "Win7 USB" with the up and down arrow keys ?
Question 2 :
You've mentioned that your IDE 2.5" usb-hdd is funtional with your above idea . Does it mean the 'Buffalo' 2.5 SATA usb-hdd fail ?
Hope for your tutorial again. Thanks.
|
|
|
|
| Post Number: 33
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Nov. 02 2011,14:27 |
|
|
hello balder ,
Sorry, I've Question 3 :
Now my usb-hdd has 2 partitions
1st primary active NTFS partition
2nd logical NTFS partition (for data storage)
I've a habbit to hide the "1st primary active NTFS partition" , the reason is :
1. Everytime when I plug in my usb-hdd to any computer , I don't want Windows to search my 2 partitions's content , that would take a long time to finish or break it. That's annoying.
2. If some of my Windows's folder path is D: , and when somehow my usb-hdd become drive D: , then unwant files or folders may be generated on my usb-hdd 1st partition.
Actually hidding "1st primary active NTFS partition" is a good staff to me , and Easyboot work normal all over.
My question 3 is :
According to your above idea , can I hide the 1st and 2nd partition as usual ?
Thanks
|
|
|
|
| Post Number: 34
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Nov. 02 2011,15:02 |
|
|
@allgames71
Quote: "Does it mean the 'Buffalo' 2.5 SATA usb-hdd fail ?"
Yes, unfortunately that is the case 
This is hazardous - and far from stabile solution.
Best result is achieved using bold part of tutorial in post nr;27 in this topic
But strangely that 3.5" IDE-unit plugged into USB dock-station did work 
So I took a chance and created Ghost image of whole IDE-harddisk and run ghost to Buffalo 2.5" (a 'real' USB disk powered directly from USB-connector)
But it didn't work 'File not found' was all grub reported.
This USB disk units behaves differently and we must use the most reliable method we can find.
And that method is describe in post nr;27
However I'm not sure NT5-PE-systems (BartPE as example) can be launched this way - but NT6-PE-systems (MsDart60/65/70 and similar can be launched correctly from NTFS partition)
Note: you must create one primary NTFS partition and one second FAT32 partition to make it work.
NTFS partition is supposed to hold VHD-file(s) including any NT6-PE-system (MsDart etcetera) and the FA32 partition can hold linux\isolinux distros.
However you can put NT6-PE-ISO-files directly into folder ezboot and simply use menu command: run ***.iso
Create iso and follow tutorial in post nr;27
In this way you automatically have your NT6-PE-file(s) already in EasyBoot-ISO-file.
But you cannot use this solution to NT5-PE-files (I'm searching for an solution to this problem).
Okay, it isn't every day we launch VHD-files and thereby need to start from NTFS but I guess it will be more common in future
And the solution is to create and launch ISO of EasyBoot menu system, instead of launching ezldr (folder ezboot) as it cannot be run from NTFS.
Quote: "According to your above idea , can I hide the 1st and 2nd partition as usual"
This should be possible as we use grub as boot-loader to launch created ISO-file of EasyBoot menu.
Grub should be able to find hided partition(s) as well.
You can copy some NT6-PE-ISO to another NTFS-partition and hide partition.
Create menu entry in menu.lst on first partition typically like this:
title Launch NT6-PE
find --set-root --ignore-floppies /iso/nt6-pe.iso
map /iso/ nt6-pe.iso (hd32)
map --hook
chainloader (hd32)
boot
Above menu entry in grub automatically scan all partitions (hided should be found as well) and launch nt6-pe.iso 
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: Nov. 03 2011,01:41 |
|
|
hello balder ,
I've tried Post No.27 and fail to load BartPE after Ram counting in the black and white screen ! I do it as your tutorial like this :
1. Delete folder ezboot from USB drive
2. Copy C:\EasyBoot\disk1\ISO\BARTPE\BartPE.img to C:\EasyBoot\disk1\ezboot
3. Remove C:\EasyBoot\disk1\ISO folder
4. Change menu command in EasyBoot menu to: run bartpe.img (save changes to EasyBoot menu)
No need to create mycd.iso again.
5. Use 'easyboot-grub-iso.script' and push on 'Create ISO-File' - ISO is created by script
A new TEST.iso will be generated in C:\WinBuilder_Complete
6. Copy C:\WinBuilder_Complete\iso\easyboot folder to usb-stick
7. Copy C:\WinBuilder_Complete\iso\menu.lst to usb-stick (overwrite the existing one)
When boot and there's a Ram counting process , after that it hangs up like this :
----------------------------------------------------------------------------------------
Starting cmain() ... (hd0,0)
Fat12 BPB Loading ISO to RAM can take serveral minutes !
probed C/H/S = 80/2/18, probed total sectors = 2880
floppies_orig=0, harddrives_orig=2, floppies_curr=1, harddrives_curr=2
(hd0,0)
Load segment: 0x0 System Type: 0x0 Sector Count 0x4
Load RBA: 0xBA Boot Type: 0 = No Emulation
----------------------------------------------------------------------------------------
Please help , thanks.
|
|
|
|
| Post Number: 36
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Nov. 03 2011,11:31 |
|
|
@allgames71
Quote: "When boot and there's a Ram counting process , after that it hangs up"
Yes I know it happens - but I think I have a solution to this problem
First we need to set up the goal for this "mission", which is to launch Easayboot menu from NTFS-partition
1. Reason to use NTFS-partition is the need to launch VHD-files which must be run (launched) from NTFS-partition.
2. We cannot simply move folder 'ezboot' and launch 'ezldr' as it doesn't work from NTFS-partition
3. Solution is to use the in Easyboot created ISO-file as it is.
4. We cannot launch NT5-PE-ISO-files from NTFS-partition if such ISO is copied to the root of NTFS-partition
Above is the 'main'-problem we are facing
Solution is this:
I designed a new script (easyboot-nt5-iso.script) that creates a 'grub-iso'-file that can be launched with 'memdisk'-command in Easyboot.
Download beta-script-collection from HERE
Extract zip-file and you get a new folder 'balder_usb' (this is our experimental 'USB-solutions' which we can expand and test with during our 'mission')
Launch 'winbuilder.exe' inside folder as usual, and you now only have two scripts to chose between
1. Use 'easyboot-iso-nt5.script to integrate your BartPE.ISO-file (or ERD5 or similar NT5-based PE.ISO-file)
2. You automatically is given right menu command to use in EasyBoot.
Some notes: script creates a new folder 'ISOFILES' inside folder ezboot and put created BartPE.ISO-file (with grub-boot-record) inside folder 'ISOFILES' (this also gives you a clean environment inside folder ezboot).
Script also automatically update your 'memdisk'-file in folder ezboot to a newer better version, as the old one don't work correctly in EasyBoot anyway!
But from this point you can use 'memdisk' as menu command in EasyBoot menu.
You can also integrate WinPE.ISO-files based on NT6-systems (typically; Ghost15-rescue.iso, MsDart60/65/70 etcetera
Integration of such ISO's is done by simply copy WinPE.ISO-file(s) to folder ezboot\ISOFILES and use menu command in EasyBoot menu: run /ezboot/isofiles/***.iso
When creating ISO in EasyBoot test with checking *Joliet* as it can come in handy when integrating Knoppix/linux-system 
So the steps are:
1. Use 'easyboot-nt5-iso.script' to integrate your 'BartPE.ISO-fil' as first step followed by creating ISO in EasyBoot as usual (we need that ISO)
2. Manually format (recommended) your USB drive partition (the first partition) to NTFS
3. Use script 'EasyBoot-USB_v2 .script' and check "Force script to NOT format USB drive! (Only refresh grub and ISO\Image-file)".
Push on Start-button and chose ISO created by EasyBoot.
Note: you can later manually modify 'menu.lst' on USB drive
Optional: If already having grub boot-record and grlr and menu.lst on USB harddisk - you can manually copy ISO-file created by EasyBoot to your USB harddisk and modify menu.lst to launch your ISO-file
The created Easyboot-ISO-file can of course grow to a very large ISO as you having all ISO-files inside created ISO
However this is no problem as you anyway must move (copy) all 'data' to USB drive in some way - and why not do it the 'handy' way and have files collected inside EasyBoot.iso-file from beginning
Final note: You can of course use above solution from CD\DVD-unit as well!
But for present time let's test and report our results before I go ahead and change scripts to an more optimal way.
The 'easyboot-grub-iso.script' (in folder balder) is working alright with above solution to WinPE5.iso-files as well - same to the memdisk command - no problems!
Test and see if it works out better this time
regards balder
Edited by balder on Nov. 03 2011,15:09
--------------
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: 37
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Nov. 03 2011,15:28 |
|
|
hello balder ,
It works this time , it seems there's nothing impossible to you. Thanks. I follow your tutorial like this :
1. Use balder_usb...WinBuilder_Complete...Easyboot-NT5-ISO script to integrate pebuilder.iso with menu command "memdisk /ezboot/isofiles/bartpe.iso"
2. Use Easyboot to create "mycd.iso" and check "Joliet" only
3. Use balder_usb...WinBuilder_Complete...EasyBoot-USB_v2
I made this BartPE like nomal way , I do it in my usb-stick instead of usb-hdd. As there's a lot of existing program in my usb-hdd.
After making the usb-stick , I manually name the iso.iso to BartPE.iso and copy it to my usb-hdd and modify the menu.lst in usb-hdd.
Thanks for spending so much time on my raised program. Thanks
------------------------------------------------------------------------------------------
-------
balder , I want to tell you one more thing , that's about "CLONE Windows 7 USB Drive Edition (7USBEditionByiMortaluz.vhd)".
Just like you I made the Win7USB with my own language successfully and place it in my usb-hdd , by that time I made a whole copy of my usb-hdd to my son's usb-hdd as well. Every program works fine except the Win7USB , it failed to boot. So I changed another new usb-hdd and copy exactly the same thing in there and the Win7USB works also.
What I'm trying to say is this Win7USB may not be compatible with every usb-hdd. As two of my friends usb-hdd also can't boot Win7USB. So the best way is to keep your working usb-hdd well and try not to change another one. Test it.
Thanks again.
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
