TeraByte Product Release Thread

Yeah, that's disappointing. I want to upgrade, but geez Terabyte has to give users a reason to.

Edit - I ended up buying it anyway. I wanted to support terabyte. There's not much difference; a few gui changes and a new PE/RE plugin system which doesn't have very many yet. But the plugin which changed the RE background to dark was kinda cool.

 

I bought the bundle upgrade. With 50% off, it was a very small price to pay for ongoing updates. It also supports the developer so this great program can continue.

 

Thanks for pointing that out. I missed it. Nice.

I think IFW is a little faster in my computers. The graph sits on higher numbers than before.

IFL UFDs will now boot with Secure Boot enabled. It didn't work with ver 3. But I had to update IFL, TBWinRE and TBWinPE on the SSD to version 400 before Secure Boot worked on a IFL UFD.

 

In ver 400 there is an extra line to use near the User/ProductKey lines in the ini.

IFW and IFL have KEYVER=4
BIU and BIBM have KEYVER=2

I couldn't get TBOSDT to register as the BootIt version in IFL (rather than the Pro version) until I added KEYVER=2 in BOOTITBM.INI. (I was using ifl.ini and BOOTITBM.INI in the IFL build process)

You will notice ifw.ini has already been updated by the install.

 

Upgraded BIU and IFW.

 

So this is an upgrade which has to be paid for, the license so far is not valid?

 

see https://www.terabyteunlimited.com/k...kup-and-restore-suite-v3-upgrade-information/

 

Thank you.

Then the question is, will that discount still be present in the future?
A year or 2 from now e.g.

 

I would think so. I bought my v3 license in 2018 and was about to get the v4 license 50% off.

 

I don't even see an INI file in my IFL folder, although my license appears in the IFL MakeDisk GUI. It must be stored somewhere else.

I still have BOOTITBM.INI and BOOTIT.INI in my BootIt Collection folder, but no KeyVer below my license like IFW.INI has. It appears to have accepted my old license, although I have since added the new license key to the INI files.

I have KeyVer=4 below my license in IFW.INI and KeyVer=2 in BOOTIT.INI in my TeraByte OSD Tool Suite Pro\win folder.

 

You can't see it on the IFL UFD but you can if you copy the UFD partition to a SSD and boot the partition.
I have put ifl.ini and bootitbm.ini in the downloaded IFL folder. It makes creation of the UFD faster. Less typing.

ifl.ini...

Code:

[Options]
SaveUEFIData=1
OutputDiskID=1
MDUseDirData=1
GlobalGeoAlign2K=1
TimeZone=AUS-10
ISO8601=1
LogFile=/tbu/boot/ifl.log

[License]
KEYVER=4
User=xxx
ProductKey=yyy

[BACKUP_DEFAULTS]

[RESTORE_DEFAULTS]
WriteChangedSecsOnly=1

[COPY_DEFAULTS]
WriteChangedSecsOnly=1

bootitbm.ini...

Code:

[Options]
TimeZone=AUS-10
GlobalGeoAlign2K=1
ISO8601=1

[License]
KEYVER=2
User=xxx
ProductKey=yyy

bootit.ini doesn't work in this folder.

 

Same here.

 

I edited too.

BOOTIT.INI...

Code:

[Video]
Method=1
Mode=42

[Options]
TimeZone=AUS-10
ISO8601=1
GlobalGeoAlign2K=1
OutputDiskID=1
MDUseDirData=1

[License]
KEYVER=2
ProductKey=xxx
User=yyy

BOOTITBM.INI ...

Code:

[Options]
TimeZone=AUS-10
GlobalGeoAlign2K=1
ISO8601=1

[License]
KEYVER=2
User=xxx
ProductKey=yyy

 

I only use IFL that comes with the IFW installer located in:
%ProgramFiles(x86)%\TeraByte Drive Image Backup and Restore Suite\IFL
When I use MakeDisk - Image for Linux, it holds my Licensed Name and Product Key in the gui in two separate fields. I don't know where it is actually stored though.

When you talk about the downloaded IFL folder, I assume you mean the standalone download. I guess it must be different to what I use.

 

Hadron,

There are 3 ways to make IFL boot media. They appear much the same apart from a few options.

The method you use will make a NET version but it can't be installed in a Linux OS.

The NO NET download makes a NO NET version but it can't be installed in a Linux OS.

The NET download makes a NET version but it can be installed in a Linux OS. (it has installation files)

I prefer the NO NET version as it boots somewhat faster. If you don't have ethernet, it boots 20 seconds faster than the other two.

No ini is needed to make IFL boot media but it's convenient to use an ini.

 

Thanks Brian.
Do you happen to know where the IFL Licensed Name and Product Key are stored?
I just download the standalone Net and No Net versions of IFL, and run MakeDisk from my backup drive, and the Licensed Name and Product Key fields are still populated. The obvious place to look would be the registry, but I've looked in there.

 

You can view and/or copy your ifl.ini or bootitbm.ini from a loaded IFL UFD.

Open MC, maximize the window. Select the file and press F3. To Quit, press F10, twice.

To copy the file. Click Mount (mnt). Select a target partition. One that you can identify. Click OK. OK again to exit. That partition will be /tbu/mnt1 in MC.

Open MC, maximize the window.
Select mnt1 in the right pane. Double cilck. You now see the contents of the partition you mounted.
Select the file in the left pane. Press F5 (see the menu at the bottom of your monitor. They are F keys)
You will see a Copy window showing ifl.ini to /tbu/mnt1
Click OK
You can now see ifl.ini in the right pane as well as in the left.

Do the same for bootitbm.ini

F10 to exit from MC.

Restart and you will find the files in the root of the partition you had mounted. They can be moved into the IFL folder for your next build.

 

Not really as my computer behaves differently.

If I don't have the 2 ini files, the fields are blank.

 

Instead of copying those files to a local partition, you can copy them to a network shared folder.

 

Using IFL Network...

Right click the IFL desktop
Configure Network
It might be UP with an IP Address, if not.....
select eth0, OK
select IP Address Mode, OK
select dhcp, OK
Start eth0, OK
wait
you should see UP with an IP Address
select Finished/Exit Menu, OK
select Finished/Exit Menu again, OK



click net1 icon
auto Detect SMB Servers, OK
it rarely works so, Specify SMB Server Manually, OK
Specify By NetBIOS Name
type your remote computer name (eg MYBLACKBOX), OK
type User Name (eg Brian), OK
type your WORKGROUP (eg FAMILY), or accept NONE, OK
type your password (Windows login password for remote computer), OK
now you can see the shares on the remote computer
select your desired shared folder (they are all UNMOUNTED), OK
you should see the folder is now MOUNTED: (/net1) but don't select it as it will become unmounted
OK (twice)

to copy ifl.ini to the Share...
MC as before
double click /net1 in the right pane
select ifl.ini in the left pane
F5 (Copy), OK
F10 to Quit


To do a backup to the Shared folder
IFL
Backup
Full backup
Linux
choose disk
choose partition
File (OS) (different from what you usually choose)
select net1 and press Enter (not Next)
you should see the folders in your Share and the proposed Name of the backup
Next
choose your Options (if needed) but accept the defaults
Start

A restore is similar. You choose the TBI to restore in net1.

 

Upgraded from v3.64 to v4.00.
TBWinRE updated too. It's asking for Name and Key when launching it at boot though.

 

Did you copy your new IFW.ini into the TBWinRE folder before you did the build?

 

Do you have a version 4 key? Do you have the "KeyVer=4" in your ifw.ini? Also, make sure the RE builder is pointed towards the correct IFW installation dir.

 

Yes both.

In this case I always use the default installation path.

No I did not, am I supposed to do so since forever or is it new to this new v4.00? I can't recall doing it before. Anyways I think the Builder should copy ifw.ini file by itself not me doing it manually.

 

Odd. I've never had to do that either. That's why I asked you if the RE builder's path to IFW was correct. Can you rebuild the RE again? Don't update it, rebuild it.