5 replies to this topic

[Voltaire]

So, this morning I finished my tweaks (everything looks good and seems working in the virtual machine) so tonight I will FINALLY make a bootable DVD - with Boot USB to follow when I get a new one.

 

SO, I am thinking to experiment by invoking teracopy in the three areas that are the time hogs of the many builds.

Those being the two driver related scripts and the one in finals 'YY_1 something' that do a lot of file copy & move operations.

 

Has anyone tried this, and if so, was there enough speed boost to be worth it?

 

I realize to include this in a standard build would at the least require adding teracopy to the utilities and running it in standalone mode.  So perhaps that is more bother - but I am currious.

 

 I hope the dvd boots [positve thoughts,positive thoughts]

[Motasem]

maby this help

http://support.codes.../4/command-line

[Wonko the Sane]

Of course tests need to be made, but *generally speaking* teracopy is not that much faster than "normal" OS copy.

 

I would personally try Fastcopy:

http://news.softpedi...ws-176022.shtml

http://ipmsg.org/too...astcopy.html.en

 

as it seems to me, besides "faster" also more suitable, given it's BSD style License.

 

In any case the saving will be a matter of seconds.

 

Wonko

[Voltaire]

Wonko,

I hadn't even looked into speed thing yet, as I was mostly curious as to IF this had been tried already.  But the amount of data in that test was MUCH larger, and if it was only a minute faster then you are dead on that it would only save seconds (if that.)  Not worth the effort to mod a script - much less doing test builds.

 

Motasem,

Thanks, but I already looked the available command line options.

[RoyM]

Hi Voltaire!

Thanks for the scripts you have recently published.

 

I have succeeded speeding up my builds using this.

http://reboot.pro/fi...basebuildex-v2/

 

 

It's purpose is to run the scripts you include on basebuildex.script interface, 

then disable the scripts so that Winbuilder will not run them again, 

it then copies the results of your Basebuild somewhere, and then uses

that basebuild on every run/build thereafter using robocopy

to copy the basebuild back into your target directory and 

then allowing Winbuilder to continue building as normal

 

You can acheive faster copies by tailoring the robocopy 

switches for desired results. See Notes in script.

On development machine I keep the basebuild results on raid0 ssd's.

 

I use this as a development tool when building scripts.

For instance, I can have a nearly completed basebuild

with most scripts included, so when I run winbuilder it 

is running maybe 5 scripts, because basebuild has already

done all the work, you then run your new script somewhere

further down, this also helps to insure that your script registry

entries won't get overwritten by another script.

 

This script was inspired by Peter's great work "BaseBuild" from a prior project,

and then taken a little to the extreme by myself, thus BaseBuildex.

My personal script has nearly 200 entries for adding other scripts.

Instead I use the extra interface entries to group the same type

of scripts together and also add notes and such to interface.

 

 

Hope this helps

RoyM

[Voltaire]

ThanksRoyM, I will look into that.   As for my scripts, you and everyone are most welcome.  Just glad I can contribute.