TeraByte Unlimited

Is there any documentation on the BuildScript.cmd script for TBWinPE (described briefly in the 'settings' page)?

You can use it to automate tasks that need to take place while the build is mounted. For example, if you're creating a custom build that needs to change settings, copy in files, etc. you can put the commands in the script. This could be done before but you would need to pause the build, do the tasks manually (or run a custom script), then resume.

Are you trying to do something specific?

Yes, I'm looking to copy a program (MyDefrag) from Program Files on c: to
somewhere appropriate in what will become the x: drive. I am looking at an
enhancement to my IFW_Backup scripts, TBWinPE/RE section that would require
the user to include a BuildScript.cmd to do this. Just an idea at this
stage.


PP wrote:
> You can use it to automate tasks that need to take place while the build
> is mounted. For example, if you're creating a custom build that needs to
> change settings, copy in files, etc. you can put the commands in the
> script. This could be done before but you would need to pause the build,
> do the tasks manually (or run a custom script), then resume.

Are you trying to do something specific?

First, you would need to verify if the program would even work in the build. Many programs won't run (or won't run properly) in WinPE due to lack of support. Also, for WinRE-based builds (like TBWinRE) most are 64-bit so require a native 64-bit version (which many programs don't have) since there is no 32-bit (x86) support. For simple programs you can usually test this easily by trying to run the program while booted to WinPE (the program could be at the installed location or on a UFD, for example). More integrated programs may require adding registry entries and installing support files before they can run, which takes more work. For 32-bit (x86) programs you would need to create a 32-bit TBWinPE build, which requires downloading and installing the AIK/ADK files.

That being said, you could certainly use the build script to copy the program files into the build, add registry information, and so on.

Thanks for the information.

MyDefrag runs ok under WinPE and is available in both 32 bit and 64 bit
executables. However, I think I may just copy the program to %temp% at run
time, then run it from there.

In the broader scheme of things I'm looking to process multiple physical
disks by running more than one defrag/backup script in parallel using the
IFW /nowait parameter, and I don't want the IFW to fail if another script
is running a defrag at the time. (Locking error).

Can the /nowait parameter be used to run parallel backups like this?

PP wrote:
> First, you would need to verify if the program would even work in the
> build. Many programs won't run (or won't run properly) in WinPE due to
> lack of support. Also, for WinRE-based builds (like TBWinRE) most are
> 64-bit so require a native 64-bit version (which many programs don't
> have) since there is no 32-bit (x86) support. For simple programs you can
> usually test this easily by trying to run the program while booted to
> WinPE (the program could be at the installed location or on a UFD, for
> example). More integrated programs may require adding registry entries
> and installing support files before they can run, which takes more work.
> For 32-bit (x86) programs you would need to create a 32-bit TBWinPE
> build, which requires downloading and installing the AIK/ADK files.

>That being said, you could certainly use the build script to copy the
> program files into the build, add registry information, and so on.