TeraByte Product Release Thread

mantra,

I'm not familiar with how those apps work. BIBM can do a wipe (secure) on SSD partitions.

I noticed my Intel Toolbox app can't do a Secure Erase unless the SSD has no partitions.

 

but it's very fast? Magician Software or PartedMagic keeps 1 or 2 seconds


may i ask you a second question about bibm?
can bibm erase only the MBR( i mean Bootstrap code) too?

 

A BIBM wipe isn't fast.

You can copy TeraByte's MBRWork to a BIBM USB flash drive and use it to zero LBA-0 and/or LBA 1-62. You can use BIBM to backup/restore these same sectors.

http://www.terabyteunlimited.com/downloads-free-software.htm

 

Hi Brian
may i know where is the option

i gave a look to the program settings and restore settings , i did not find it
i use image for windows ,winpe w8.1 based
maybe a screenshot would be great
thanks
http://i.imgur.com/uYfyYsf.png


in the manual i found but can find the option to enable it

 

It's going to be in the Restore or Copy options (not in the Settings window). Also, you need to be using 2.84 or later.

 

hi
on my w8.1 i have 2.87 and i did not find it
n the changelog , there is 2.84

but but it's only about the command line /wco
there is not a checkbox to enable/disable
thanks

 

Make sure you're looking in the Restore or Copy settings. It's been there since 2.84.

Select the Restore (Normal) option, then continue until you get to the Restore Options screen. Also, the screenshot in the 2.84+ manuals show it (page 107 of the 2.87 manual).

 

Thanks

reading the manual , i found lots of command lines

is there a way to pass a switch to image for windows(winpe 8.1) or image for linux ?

there is show command but let me save to a file , not run
could i add a command line under ifw(winpe) or image for linux?
thanks

 

You don't pass command line switches to the program as a way of setting options separate from the running of the program -- command line switches only apply to that run of the program. If you want to affect the GUI interface options you put the appropriate settings into the IFW.INI file (or IFL.INI file). For command line options, you use them on the command line when you run the program or when run from batch/script files.

For example, if you boot into TBWinPE (or any WinPE) and want to run IFW from the command line, you'd open the Command Prompt window and browse to the program (unless you want to specify the long path) and then enter the commands:

cd "x:\program files\terabyte unlimited\image for windows\v2"
imagew /r /d:w0 /f:"j:\mybackups\win8" /wco

---

Running IFW (or IFL) via the command line in WinPE (or Linux) is no different than running it from the command line in Windows (or Linux).

When you use the "Show Command" function you can save the command to a file. Then you would browse to that file and run it. For example, if you saved it to "myifwrestore.cmd" you would open the Command Prompt, browse to where you saved "myifwrestore.cmd" and then run it.

 

I have a question re IFW's 'Backward Compatibility' checkbox. If I were to check this would it slow-down my backup or materially change the size of my backup (all other factors being equal)? For that matter are there any adverse consequences when enabling 'Backward Compatibility'?

TS

 

The file format and support would be more limiting. For example, you wouldn't be able to use the newer compression options which could result in longer/larger backups (depending what you normally use). Also, if the backup requires the newer version the option won't be available (backing up GPT, for example). If you wanted to use newer options and still use an older file format you could use the BackwardsCompatibleLevel setting (not a GUI option) to specify 2.78-2.85.

Using the Backwards Compatible option basically makes it create a .TBI file that would be supported by the older version of the program (2.50 or 2.78-2.85). Some options introduced since then could still be applied if they don't affect the format; others may be ignored. The backup image would still be valid (like if you created it with 2.50).

Personally, if you don't need to be able to use the older versions to handle your backups I'd just use the current version.

 

Agreed with MudCrab.

Yes there are advancement in imaging/compression algorithm and bug fixes in newer versions. On top of that, new technologies come out, such as GPT/UEFI and secure boot, and Terabyte normally adds support to them quickly. Therefore it makes a lot of sense to always use the latest version.

IFW/IFL/IFD is an amazing piece of software that I came across in here about 5 years ago. It's currently the only disk imaging software that I actually purchased. The upgrade policy is another amazing thing: users have been able to get free update ever since V2 was released about 5 years ago. The developers are really generous.

 

Thanks - I really appreciate that insight.

TS

 

so about for imge for windows 2.83 to enable Restore Changed Sectors Only
imagew.ini must include this setting
[OPTIONS]
WriteChangedSecsOnly=1

while after 2.83 imagew.ini must have this setting
[Restore_Defaults]
WriteChangedSecsOnly=1

 

The settings don't go in imagew.ini (it contains the key info) -- they go in the IFW.INI file.

For example, your IFW.INI file might look like this:

Code:

[OPTIONS]
PageHiberClear=1
GlobalGeoAlign2K=1
PHYLockUseReg=0x1
LogFile=E:\IFW.LOG

[Restore_Defaults]
WriteChangedSecsOnly=1
Compression=14

[Copy_Defaults]
WriteChangedSecsOnly=1

In 2.83 WriteChangedSecsOnly was a global option. In 2.84+ it's specific to restore/copy operations and goes into those sections of the INI file.

 

Version 2.88 (Image For Windows) - February 25, 2014

• Added /csigut (ChangeSigUseTarget) to allow /csig option to keep the target drive signature if unique.
• Allow renaming of a partition on a single partition restore.
• Schedule option added for simple mode backups.
• Fixed a spurious error message about an invalid hash file which could occur when being used for a changes only backup.
• Changed the /phc default to include clearing of the hibernation file.
• Other various changes, updates and enhancements.

 

Version 1.25 (BIBM) - February 25, 2014

• Added option to save boot menu location (F11) or reset location (Shift-F11).
• Added a memo field to boot items that will show on the boot menu when selected.
• Other potential changes, updates and enhancements.

 

Version 1.51 (TBOSDT Suite) - February 25, 2014

• Added index [0] for GetHDInfo() results on non-partitioned drives.
• OSDTOOL.TBS script updated to install custom driver store.
• Added enhancements to most .TBS scripts.
• Other changes, updates and enhancements.

 

Version 2.88 (Image For DOS) - February 25, 2014

• Added /csigut (ChangeSigUseTarget) to allow /csig option to keep the target drive signature if unique.
• Allow renaming of a partition on a single partition restore.
• Fixed a spurious error message about an invalid hash file which could occur when being used for a changes only backup.
• Changed the /phc default to include clearing of the hibernation file.
• Other various changes, updates and enhancements.

 

Version 2.88 (Image For Linux) - February 25, 2014

• Added /csigut (ChangeSigUseTarget) to allow /csig option to keep the target drive signature if unique.
• Allow renaming of a partition on a single partition restore.
• Fixed a spurious error message about an invalid hash file which could occur when being used for a changes only backup.
• Changed the /phc default to include clearing of the hibernation file.
• Update Linux Boot Disk (LBD246EN)(3.11.10).
• Other various changes, updates and enhancements.

 

hi
thanks
what do you mean for global option?
IFW.INI should contain WriteChangedSecsOnly under option to be inside the global option?
[OPTIONS]
WriteChangedSecsOnly=1

 

Correct -- the [Options] section is where the global options go. Keep in mind that for WriteChangedSecsOnly that it's only a global option in 2.83.

 

thanks
i want to update to 2.87
but the last time , when i created the winpe was a nightmare

 

by the way today i update to 2.88
i created the winpe iso , i was again a nightmare , last TBWinRE included in image for windows 2.88
it moved the WINRE.WIM and not copied

1) is there a way to run TBWinRE inside sandboxie to avoid it
i tried but i got error about mounting winre.win but maybe a setting for sandboxie could let me create it without mess up my original winre.wim

2) is 2.88 100% compatible with the image full and differenzial created with 2.83?


thanks

 

1) You shouldn't need to. I remember you had problems before, but don't remember exactly what they were. If you just want to build the TBWinRE boot media (UFD, CD, ISO), you can do that easily without needing to do anything with the built-in Windows version. When the build is created the winre.wim file is copied to the WinRE_Backup folder in the TBWinRE folder. If the backup exists it is used when creating the media (there is no need for the script to find the installed version of the file).

The easiest method when finding the installed winre.wim file is problematic would be to do the following:

1. Create a folder just for TBWinRE and leave it on the computer. Deleting it will remove the backup of the winre.wim file. For example, you could make C:\TBWinRE and use that.
2. Place the TBWinRE files into the TBWinRE folder. Download tbwinre.zip from the tutorial or copy the files from the installed IFW folder. This gives you easier access to them and avoids permission problems if you need to edit the files/settings.
3. Since the script isn't able to find your installed winre.wim file, create a folder name WinRE_Backup in the TBWinRE folder (C:\TBWinRE\WinRE_Backup) and copy the previous winre.wim file you used into it. You can copy from the installed location if that's easily accessible or you could copy it from a previously created TBWinRE flash drive (copy boot.wim from the sources folder and then rename it to winre.wim).
4. Edit imagew.ini and add your key info.
5. Run the script and select option 2.

The main thing here is that you keep the TBWinRE folder. If you delete it you'll have to start over. If you keep it all you have to do to update your TBWinRE boot media is to run the script, select option 2, and create the media. You don't have to edit imagew.ini again or find winre.wim -- they're still there and ready to go.

If the problem is with MakeDisk creating the UFD boot media, then you can certainly just copy over the updated boot.wim (located in the TBWinRE\ISO\sources folder) to the UFD's \sources folder to update it -- no need to run MakeDisk.

2) It should be 100% compatible. I've never had any problems with image files created using different versions. The newer versions support all the older version formats (within the same major version number).