|
|
| Post Number: 1
|
allgames71 
Group: Members
Posts: 299
Joined: Nov. 2008
|
 |
Posted on: Oct. 25 2011,02:41 |
|
   |
Hello balder
I use the new WinBuilder_Complete and found that :
1. The Easyboot-USB_v2 has no defrag ISO option. This again cause my Win7PE.iso cannot be boot in my usb harddisk (but can boot in usb thumb drive).
2. The Easyboot-USB_v2 when start to detect the usb drive and found there are 2 or more usb drive (e.g. one usb thumbdrive and one usb harddisk) , it would stop progressing. I admire this is a wonderful idea to avoid destroying usb harddisk datas. Before the old scripts , when I unplug the usb harddisk and left only one usb thumbdrive in the computer , and start again Easyboot-USB_v2 , it will continue to progress normally.
But now the new Easyboot-USB_v2 scripts , even I unplug the usb harddisk , it still regard that I have 2 usb device in the computer. Nomatter how many times I try , it won't go on anymore. Unless I reboot my computer , then it would be normal to make my iso file to usb thumbdrive.
Hope that you can look into it and have the error corrections. Please let me know that. Thanks in advance.
|
 |
|
|
| Post Number: 2
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Oct. 25 2011,02:52 |
|
 |
@allgames71
Quote: "even I unplug the usb harddisk , it still regard that I have 2 usb device in the computer"
Thanks for your feedback @allgames71 - I'll take a look into this issue during this day  .
Hopefully before evening I have found some solution - however it is better to reboot computer than destroying data, just in case it cannot be changed 
Reason might be I have to built-in support to both 32-bit as 64-bit systems - it gives me head deck 
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
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Oct. 25 2011,07:32 |
|
|
allgames71
Quote: "it still regard that I have 2 usb device in the computer"
Done some tests with USB-harddisk (2-partitions on that one).
One USB stick (one partition on that one).
I tested both Defrag-button as the "Main-Process" Start-button!
Test performed to three different computers (different motherboards) with three different OP-systems!
One system with Windows-7_64-bit (Asus motherboard)
One system with Windows-8_32-bit (beta-version) (Gigabyte motherboard)
One system with Windows-7_64-bit (Barebone computer)
Note: There is no difference when using defrag-button or the "Main-Process" Start-button!
Script uses exactly the same procedure to find amount of USB drives that is connected to motherboard 
Tested scenario A:
Plugged in USB stick followed by plugging in USB-harddisk
Script complained (found two USB drives)
Unplugged only USB-stick - waited a couple of seconds - but script still found two USB drives and halted!
Unplugged USB-harddisk - waited a couple of seconds - plugged in USB-harddisk - script found one USB drive with two partitions and continued with its normal procedure!
Tested scenario B:
Plugged in USB-harddisk followed by plugging in USB stick
Script complained - found two USB drives!
Unplugged USB-harddisk but script still found two USB drives and halted!
I unplugged USB stick as well and waited a couple of seconds...
Plugged in USB stick and script found one USB drive - which script accepted - and continue with its normal procedure.
Tested scenario C:
Plugged in USB-harddisk followed by plugging in USB stick
Script complained - found two USB drives!
Unplugged USB stick - script found one USB drive with 2-partitions - which script accepted - and continue with its normal procedure.
Take in consideration it takes several seconds for computer to find USB-harddisk - especially if USB-harddisk has several partition!
I cannot create scenario where I'm forced to reboot any of the three different computers I run test to (no need to reset the system - basically reset Windows Explorer) - it's not the script you "reset", it's the Windows Explorer that keep on reporting wrong data.
Seems Explorer is "hooked up" in some way, and in this way keep on reporting wrong data to script.
------------------------------------------------------
Script is depended of the Explorer in the Windows system Read below...
Some basic explanation how script behaves:
1. Script is doing a kind of "handshake" to the Windows system.
2. Script "asks" Windows explorer to report what USB drives that might be plugged into motherboard.
Note: script never looking or touch your internal hard-drives - script only focus to the USB drives.
To make this work, script uses a small command line tool that quickly create a simple text-file using Windows Explorer which is 100% reliable.
When script has received information from Windows Explorer - script at once starts to manipulate (clean out) text-file to collect "USB parameters".
This procedure  takes less than 2 seconds, and script continue with following:
1. Can find out how many USB drives that is plugged into motherboard!
2. Sort out what type of USB drive(s) - "removable" and/or "fixed" drive (USB-harddrive) that is plugged into motherboard!
You may ask why all this examinations?
A: Make sure no data is lost (to make sure script doesn't format wrong USB drive).
B: And because script  uses different methods to format USB-drive if run WinXP or Vista\Win-7
Yes, it is true - script is checking what sort of OP-system you are running - and need to adjust what tool to use during format-process - and also depending of what kind of USB drive that is found!
Note1: If script find USB-drive with several partitions (usually USB-harddisk) script always focus on first partition on USB-drive - script never touch second partition as the first partition normally is set to "active partition" (you can name it: "bootable partition")!
In case first partition to such USB-harddisk isn't set as active - script fixes it during format process - you don't need to worry about that part
Note2: You can also create several partitions to USB stick as well - but second partition to such USB stick is not present in Windows Explorer, it's hided!
But amazingly, script is able to find out that USB stick do have two partitions (including second not visible partition) - and still focus to partition one (never touch the second invisible partition)
He, he it is really a lot of parameters I have to take in consideration when constructing such script - but it works mostly okay 
I'm pretty sure it is something with your system (Windows Explorer) that seems to "hook up" what USB drives that is connected to motherboard.
Windows Explorer should automatically reset itself when removing USB drive(s), but seems in your case having some issues with that part
Final note: Option "Defrag-button", should be able to fix your ISO-file on USB-harddisk to contiguous shape - though this it is an rather rare problem.
As the last resort to solve this problem, you might need to format partition one on USB-harddisk 
EDIT: Make sure to not use USB-hub as use hub can fool system in many ways - plug-in USB drives directly to motherboard!
regards balder
Edited by balder on Oct. 25 2011,10:15
--------------
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: 4
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Oct. 25 2011,11:03 |
|
|
hello balder,
Thanks a lot for your long explanation for my question. May be I'm an impatient guy to unplug my usb harddisk and right the way I press the "Start" button again. Not waiting the explorer to refresh the existing usb situation. I've try your way and wait for few seconds. It works.
Sorry for my foolish.
Thanks again.
|
|
|
|
| Post Number: 5
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Oct. 25 2011,12:12 |
|
|
@allgames71
Quote: "I'm an impatient guy... Not waiting the explorer to refresh the existing usb situation"
He, he sounds like an eco from myself - are you my "unknown" brother Â
He, he I don't think you can bet me in an race of impatience - I think I'm the winner 
I tested scripts on me old laptop "Amada-300".
I was close to fire a bullet into the "face" of that laptop - it was so sloooo...w 
I'm now convinced I have the common disease "computer-stress" - I cannot wait until any computer is finished - especially not 10 years old "super-slow" laptops
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: 6
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Oct. 25 2011,15:37 |
|
|
hello balder,
I fail to make my Win7PE many times (over 10 times) by using either EasyBoot-USB_v2 or EasyBoot-USB (old version) :
I've check the "run defrag to USB drive" already , my USB thumbdrive works properly. But when I copy that iso.iso to my usb harddisk , it comes out many times the same error message and stop ......
-----------------------------------------------------------------------
Booting [0] Win7PE (Windows 7)
(hd0,0)
map /iso/win7pe.iso (hd32)
Error 60: File for drive emulation must be in one contiguous disk area
Press any key to continue....
-----------------------------------------------------------------------
I remember last time I made this Win7PE successfully by using the older version of "winbuilder_complete" , by that time after it finished making the iso.iso , it defraged the iso.iso without stopping and showed not stopping and not finishing. You have to stop it manually. But that old version made me success for building up my Win7PE.
I'm wandering if you keep all your version of "winbuilder_complete" , if so , can I download them and have I try to each one so to find out which one is the one I want. I know this is impolite , but I really need it. Thanks
Actually it's my mistake not to keep each version of "winbuilder_complete" , instead , I always overwrite it by the new version.
Hope you can help me , thanks again.
|
|
|
|
| Post Number: 7
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Oct. 25 2011,17:31 |
|
|
@allgames71
Quote: "Error 60: File for drive emulation must be in one contiguous disk area"
Yes I know what you are asking for 
Reason to not use that kind of command-line-tool was, it didn't always worked properly (nothing was harmed but stalled occasionally from time to time - I don't like when things aren't running smooth).
What I do not understand is; if you have used built-in defrag-tool (you have button in script "Run defrag to USB drive" - if so, this procedure should already solved defrag-problems to all files on USB drive
This defrag-tool is an update to command-line tool "contig"
It's basically contig with a graphic style - so why doesn't work as supposed
---------------------------------
Please test this solution
You can simply manually in "easyboot-USB_v2.script" push on button "Run defrag to USB drive" while having checkbox "Show result of defrag" checked.
You are hereby able to manually pinpoint any specific file to run defrag to.
While having program "Wincontig" up and run chose "Add" in upper left part of program-window
Now scroll to USB drive and chose ISO-file(s) (hold down "Ctrl" if choosing several files to defrag)
ISO-file(s) shows up in central part in program-window "File Name"
In program-window lower part push on "Defragment"
Program start to defrag chosen file(s)
------------------------------------------------------------
If still not working - solve it using the "last resort"
I guess size to win7pe.iso is something like 250MB or similar
Solution is to change grub-command to this:
(hd0,0)
map --mem /iso/win7pe.iso (hd32)
Hereby ISO-file is loaded to RAM and put together in contiguous shape in RAM before launching.
Difference in time to launch ISO this way is a couple of seconds - in my opinion negligible.
Note: win7pe is anyway loaded to RAM before it is launched (you can watch it while loading "boot.wim" to RAM).
Only difference if using "--mem" is that ISO-file consumes twice amount of RAM - which these days isn't any problem - in my opinion negligible
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: 8
|
allgames71
Group: Members
Posts: 299
Joined: Nov. 2008
|
|
Posted on: Oct. 26 2011,01:39 |
|
|
hello balder,
According to your instruction , I made it successfully in the following ways :
1. Firstly I use another blank new partition usb harddisk to set up the win7pe , bypass set it up in a usb thumbdrive then copy the win7pe.iso to usb harddisk. it means , I use directly a usb harddisk to set up the win7pe.iso with "Defrag" button checked. It works fine.
Then I copy this iso.iso to my computer harddisk say drive D: and name it win7pe.iso. And I plug in my old usb harddisk with Easyboot Menu which was fail before ... I copy D:\win7pe.iso to this old usb harddisk and boot fail with the same error message "contiguous disk area". Then .....
1. I use your way to change the boot menu to boot win7pe to memory ,
---------------------------------------------------
(hd0,0)
map --mem /iso/win7pe.iso (hd32)
---------------------------------------------------
It works and bootable and delay for 8 seconds to load to ram at the beginning (my computer is not a slow one).
2. I change back the boot menu to normal
---------------------------------------------------
(hd0,0)
map /iso/7PE_My.iso (hd32)
---------------------------------------------------
This time I use the "EasyBoot-USB_v2" 's "Defrag" button and checked "Show result of defrag". It works fine also.
Thanks a lot balder for your instruction and tutorial. I made it. Thanks again.
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
