TeraByte Product Release Thread

Hi @Brian K . Just to let you know that I did try the tbibckup.tbs script as you suggested and it certainly does the job "as advertised" for a full and complete backup of all drives. I wasn't able, however, to persuade it to do precisely what I wanted with multiple (but not all) drives.

That's not any major problem so far as i'm concerned. Scripting sequential backup operations to my own requirments is reasonably straightforward. For that matter, when I'm working in my WinPE setup, it's just about as easy to right-click each drive and let its context menu association (contextbackup.cmd) run the backups automatically. Very happy with that once I figured out all those $~$ parameters.

__
P.S.: IFW running in the WinXP PE (Gena) setup seems to want Phylock for some strange reason, but that can be overridden and the backup runs and verifies fine without it.

 

Arvy,

Thanks for the links to Win10PESE. This 1709 one seems to boot faster than a previous version I tried. I made a UFD today. How do I add your script to a fresh build?

 

Hi Brian. It's simply a matter of adding my script (TerabytePE.script) into the Win10PESE project and then (re-)running that project to create a new WinPE ISO or WIM file or whatever type of bootable end result suits you best. The TerabyteScript.zip download link for my script is in the top line of my virtech.org webpage as direct download links here are frowned upon. Please be sure that you get the most recently updated version with shell integration as I mentioned above to Froggie.

The first left clickable image in the bottom row on my webpage shows the script's runtime options and where I placed it in relation to other Win##PESE project scripts. I specified "HD Tasks" as the default Start Menu placement, but you can change that to whatever you may prefer and there's also a runtime option to add a desktop shortcut if you wish.

Yes, all of ChrisR's WinPE Builder projects are constantly being improved and copying the complete Windows installation package source onto a fast drive also makes a major difference in the build speed.

Let me know if you need any additional details or help with my script, but you shouldn't run into any problems. I've tested it very thoroughly will all WinPE build versions that I have available, from XPx32 to W10.1709x64. And please feel completely free to modify, pass it along, or do anything else you want with it.

 

Arvy, a problem. At step 39/59 I see...

""Terabyte" files not found in %pFileBox1%. Script will exit."

I put the script in ....Apps\HD Tasks\Imaging\

Before starting I looked at the Script tab and the TeraByte path was correct. It looked the same as your screenshot.

 

Thanks for posting that "feedback" and sorry that you're having a problem with it. That's very strange. The relative location of the script has no effect on the absolute "Path to Terabyte files" setting. The default setting of "C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite" has worked for me in all cases, but I did build a "safety check" into the script.

It checks for the presence of "%ProgramEXE%=imagew.exe" in the specified folder location. If that imagew.exe file is found in the specified folder, the script then assumes that the full current Terabyte Suite has been installed normally in that location and it proceeds accordingly to copy all of the required files to the PE build, etc. If that executable file is not found in the specified location, the script exits gracefully with the error message that you've noted.

The only other thing that I can suggest would be to hit the browse button beside the existing "Path to Terabyte files" entry and select the correct Terabyte Suite installation folder manually. If that doesn't work, I can modify the "safety check" in the script so that it looks only for the executable file "bitness" that's needed in each case.

__
EDIT: For the current script download, the "safety check" is now specified as:

Code:

If,NotExistFile,"%SourceFolder%\%ProgramEXE%",Run,%ScriptFile%,NotFound

where %SourceFolder%=%pFileBox1% and %ProgramEXE%=imagew.exe OR %ProgramEXE%=imagew64.exe as appropriate for the build architecture. Suggest that you redownload and try that updated script to see if that works better for you. Please let me know.

 

Arvy,

I used your new script but deliberately didn't browse to the TeraByte path for the first attempt. I saw an error at around 35/59. "Build stopped due to a script error". The title heading was "TeraByte IFW PE (TeraBytePE.script)".

The log showed...

That makes sense because I don't have bartpe.exe. There are several components in the IFW install that I don't install...

TBI Notify
TBICD2HD
BINGBURN
BURNCDCC
PE Builder
Image for Linux CD Boot Files

 

Ahh, okay. I understand now what's causing your problems.

The WinPE Builder process has been made intentionally unforgiving of any filecopy failure. I'll need to modify the entire filecopy section of the script with an "If ExistFile" test for each individual Terabyte Suite file in order to accommodate users of partial installation setups. I should have a revised version ready for you to download and try within an hour or two. I'll update this post when it's available.

 

Thanks. Just an explanation for the "Image for Linux CD Boot Files". They are need if you backup to optical media and you want the optical media to be IFL bootable. It will boot to IFL. If you don't have "Image for Linux CD Boot Files" then the optical media will boot to IFD. As I never backup to optical media those 41.5 MB of files in the C: drive would not be used. I like to keep my C: drive lean and mean.

 

I understand, Brian. In fact, the script at this stage has no option for including the IFL files either, but it does try to include all of the files that may be installed in the main Terabyte Suite folder and, depending on system architecture and on the runtime options that are chosen by the user, some files from its TBIView and Phylock subfolders are also included. I had originally hoped to use a much simpler DirCopy process, but that just wasn't possible under the circumstances.

Anyhow, I have now uploaded a revised version (v025) of the TerabytePE.script which should, I hope, eliminate all those problems that you encountered. It now tests for the presence of each file in the specified source folder before it attempts to copy it to the PE build, thus avoiding the WinPE Builder's copy failure shutdown reaction. I should have done that the first time, but I got a bit lazy when my simple DirCopy plan didn't work as I had hoped. Anyhow, I apologize for your bad "beta testing" experience, but you may have saved others some considerable amount of frustration and you've certainly helped me. Thanks for that and for your patience. Much appreciated.

 

Arvy, no need to apologize. Your script is amazing. I've just booted a UFD and I'll soon copy it to a HD partition on a GPT disk. I can boot that partition with TBOSDT...

set UEFI bootnext bootnum

In a MBR system I'd use BootNow to boot the partition.

Your script is great!!!!

Edit.. It is now running in partitions on GPT and MBR disks.
How can I auto run an IFW script on startup of WinPESE? Thanks.

 

Thanks very much, Brian. Glad you like it and, I hope, may find it useful for your own purposes. Your feedback has certainly been very beneficial for me.

If anyone thinks that adding an option to include the IFL subfolder would actually serve a good purpose, I could do that without any great difficulty. Like Brian, however, I didn't see much point to including it in the WinPE environment. Would anyone use its CD boot option there?

 

I should not have hidden my script request at the bottom of my previous post. I have a quick and dirty method. I edited TheOven_Startup_CD.cmd to...

Code:

.....

:AMD64
ECHO AMD64
REM Example nircmd.exe shortcut "%CDDrive%\MyApplication\blabla.exe" "~$folder.desktop$" "TEST TEST"
REM Example Start "SH" /D "%CDDrive%\MyApplication\BlaFolder" "%CDDrive%\MyApplication\BlaFolder\Bla_x64.exe"
call D:\PESE.cmd
GOTO:eof

....

PESE.cmd is...

Code:

start "" %CDDrive%\Programs\Terabyte\IFW\imagew64.exe /wait /b /d:w0@0xA /f:"E:\Backup-w0-0xA-$~YYYY$-$~MM$-$~DD$-$~HHMM$"

After PESE loads it does an IFW auto backup. I'm mainly interested in auto restores but I can now work on that issue by editing D:\PESE.cmd in Windows.

 

An auto restore and restart to the restored Windows works fine...

 

Sorry, Brian, I retired early last evening and completely missed that edit, but it looks as if you did fine without any input required from me. AFAIK, the method you chose is the best "run at startup" process available for any of those WinPE Builder projects. Any of the other PE startup command processes (for drivers, network, etc.) would be premature for your purposes.

__
P.S.: An alternative would be the inclusion of an AddAutoRun option within the script itself as discussed in this article by paraglidernc. But, other than providing "per script customization", it amounts to about the same thing from an operational standpoint.

 

Arvy, it's running well. Thanks again for your help. I'll keep it simple.

 

hi Brian
i would like to create an TBWinRE and not a TBwinPE
but image for windows asks me to download from microsoft server 1.6GB (i guess it's windows AIK or ADK)
is it normal?
thanks

 

No. There should be no download with TBWinRE or TBWinPE.

Are you starting the build by copying the "tbwinre" folder to the D: drive and then double clicking TBWinPE.exe? That's what I do.

 

hi Brian
i have nver unzip tbwinre in D but always in C:
but may i ask you why image for windows supports bitlocker only with TBwinRE ? macrium can create images with and it uses winpe
do you use wbwinRE or tbwinPE?
thanks

 

It's not a question of Terabyte support. WinPE builds can be made fully capable of supporting BitLocker. Like Windows itself, however, they require the WMI Win32_EncryptableVolume Class to be able to do so. (See http://msdn.microsoft.com/en-us/library/aa376483(VS.85).aspx.) For WinPE builds, that resource is found in the AIK WMI-package* which needs to be installed to the build using DISM (the same way Macrium's rescue media "wizard" does it) as follows:- Dism /image:<Mountpath> /Add-Package /PackagePath:"<WAIKpath>\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab"

__
* The availability of which depends, in turn, on what was included in your WAIK installation. Note also that all of ChrisR's WinPESE projects (7,8,8.1 an 10) provide plugin scripts for including Bitlocker support in their WinPE builds using the full Windows install.wim base.

 

mantra,

BitLocker, using with IFW...

http://www.terabyteunlimited.com/kb/article.php?id=616

Both. I mainly use them for the TeraByte tools. Adding a File Manager to the build is handy too...

http://vault32.com/a56/

 

Anyone remember when this thread used to be used to talk about updates? No that it matters, since Terabyte doesn't give use many notable changes anyway.

 

hi
i have read the terabyte link , instead they say that i need a winRE to backup offline
about the file manager is cool , i bought total commander and i got a free copy of xyplorer
would be great to add them
thanks

 

You can use IFW with VSS to backup your BitLocker Windows partition...

 

Hi Brian
but i need winRE ? right? to backup up offline with the usbstick
thanks

 

hi
are there some script to add total commander and xyplorer ?
or is there a list of script?
thanks