TeraByte Product Release Thread

It could by my method. I've always had ifw.ini in the TBWinRE folder. My folder is in the D: drive and not the default position. I'll try building without inf.ini in that folder.

 

I don't need ifw.ini in that folder.

 

Did it, I rebuilt it. Same issue.

 

The only other thing I can think of is that you are boot booting from the correct RE. If you're saying that your option reflect the below, and your ifw.ini is present, that can be the only other thing I can think of.

 

Try putting ifw.ini in the folder.

 

I copied ifw.ini to C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre
When I restart the machine and boot into TBWinRE, IFW keeps asking for Name and Key

Is it safe to delete this?
C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre\WinRE_Backup\winre.wim
It's 683 MB large wasting drive space.

 

Yes. I do. Maybe keep a copy on the D: drive.

 

Maybe try editing imagew.ini in the tbwinre folder. I've never had to edit it.

 

I only have IFW.ini in:
%ProgramFiles(x86)%\TeraByte Drive Image Backup and Restore Suite

This is my new license format.

[License]
ProductKey=xxxx
User=xxxx
KeyVer=4

Before I upgraded to v4.00, I was thinking that I may have to edit the IFW.ini and add the new key manually, but the installer did it for me and added the additional KeyVer=4.

 

Yeah, this is normal and expected.

 

What for? I mean it might be re-created using IFW utility.

 

It depends on the winre.wim. I like to keep a backup of the original Microsoft version. If you alter the file with IFW to create a TBWinRE.wim then you have the option of reverting to the original Microsoft version if you desire.

 

I did. Then restarted the machine and then...

Look at this video
https://streamable.com/0ire40

There are two ini files in X:\Program Files\TeraByte Drive Image Backup and Restore Suite\

ifw_IFWWinRE.ini

Code:

[OPTIONS]
Simple=0
PHYLockUseReg=0
Bold=0

[PHYLock_OPTIONS]
UseVSS=1

[BACKUP_DEFAULTS]
UseMetaData=1
CreateHash=1
PostValidate=0x3

[RESTORE_DEFAULTS]
PostValidate=0x2
PreValidate=0x1
RFT=1
WriteMBR=1
UseMetaData=1

[LICENSE]
User=First Last
ProductKey=AAAA-BBBB-CCCC-DDDD-EEEE-FFFF
KeyVer=4

Options and Defaults settings are mine found in the ifw.ini I edited prior updating the RE.
The program seems to rename it to ifw_IFWWinRE.ini

and

ifw.ini

Code:

[Options]
Simple=0
PHYLockUseReg=0
[PHYLock_Options]
UseVSS=1

 

In my X:\Program Files\TeraByte Drive Image Backup and Restore Suite\

ifw.ini is my full file from Win11

ifw_IFWWinRE.ini does not exist

Sorry, I've no idea. I'd post in the TeraByte forum.

 

I suspect a bug.

Thanks for helping me out.

 

For what it's worth at this stage, here is what I do.

Copy C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre to
D:\My_files\TBWinRE_files

Rename it to 400re

Using D:\My_files\400re

copy your edited TBWinPE.ini into main folder
copy ifw.ini into main folder

double click tbwinpe.exe

now copy your edited BuildScript.cmd and your edited TBLauncher.ini into the config folder

etc

 

Does your TBWinPE.ini have the V4 registration info?

 

Yeah, that's all very odd. Why so many .ini files? I'd just use one ifw.ini that has all your configs. I think that's where the issue is; all these separate ini files are confusing each other. Your Options, Phylock options, Restore Defaults, Backup Defaults and license, should all be in the same ini file

Then, when you build your RE (making sure the builder is pointed to the right IFW pack), it should grab and use that ifw. I can't say it's a bug, because I've never had anything like that. I can only suggest based on what I see that's different, in this case the multiple competing .ini files.

 

Are you serious? Just because I'm the only one, for the time being, exhibiting this issue, is not a bug?

 

Spoiler: TBWinRE.ini

Code:

[Options]
ScreenResolution=-m3
PauseBuild=0
UseStartnetCmd=0
BootPrompt=0
TimeZone=
LanguagePack=
InputLocale=
ScreenDPI=0
AddDrivers=1
AddInstalledDrivers=0
OptimizeWIM=0
InitScript=0
InitScriptHide=0
RunScript=0
RunScriptHide=0
BuildScript=0
BuildScriptHide=0
BuildScriptLog=0
WiFiExportProfiles=0
WiFiExportType=0
WiFiExportClearText=0
WiFiAutoConnect=0
MouseSpeed=10
MousePrecision=1
MouseSwap=0

[Paths]
IFW=
TBIView=
TBOSDT=
Source=

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=
Key-V3=
Name-V4=
Key-V4=

[General]
Log=1
LogReset=0
UseDismAPI=1
UseInstalledDism=0
UseDismx64=0
DismForceUnsigned=1
DismSaveLog=0
DismLogReset=1
SkipLicense=0
IgnoreWarnings=0
NoUSBLimit=0
Win7PEUSB3=1
WarnBIBMLicense=0
SkipWinREStatusCheck=0
BootWIMPromptRestart=1
BootWIMForceRestart=0
BootWIMIgnoreDrvType=0
BootWIMMatchDrvLetters=0

Nope, I stopped right here. I'm awaiting an answer from TeraByte support based on the thread you opened there. Btw, what's the link of your thread there?

 

Of course I am. Bugs need to be reproduceable to ensure they're not human error, as must bugs turn out to be. Is this reproduceable by anyone else to this point? If this is the way my .ini files are and the way @Brian K's ini files are, and we're not having the issue what does that tell you? Logic would say, follow the example of those not having the issue. The diagnosis of a problem requires as much info as possible. Now, if you don't want to eliminate that as a possible reason for your error that's fine.

 

It doesn't and I don't know why not.

Spoiler: TBWinRE.ini

Code:

[Options]
ScreenResolution=-m3
PauseBuild=0
UseStartnetCmd=0
BootPrompt=0
TimeZone=
LanguagePack=
InputLocale=
ScreenDPI=0
AddDrivers=1
AddInstalledDrivers=0
OptimizeWIM=0
InitScript=0
InitScriptHide=0
RunScript=0
RunScriptHide=0
BuildScript=0
BuildScriptHide=0
BuildScriptLog=0
WiFiExportProfiles=0
WiFiExportType=0
WiFiExportClearText=0
WiFiAutoConnect=0
MouseSpeed=10
MousePrecision=1
MouseSwap=0

[Paths]
IFW=
TBIView=
TBOSDT=
Source=

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=
Key-V3=
Name-V4=
Key-V4=

[General]
Log=1
LogReset=0
UseDismAPI=1
UseInstalledDism=0
UseDismx64=0
DismForceUnsigned=1
DismSaveLog=0
DismLogReset=1
SkipLicense=0
IgnoreWarnings=0
NoUSBLimit=0
Win7PEUSB3=1
WarnBIBMLicense=0
SkipWinREStatusCheck=0
BootWIMPromptRestart=1
BootWIMForceRestart=0
BootWIMIgnoreDrvType=0
BootWIMMatchDrvLetters=0

 

Why is your key data presented differently?

Mine:
KeyVer=4

Mr.X:
Key-V4=

Could the hyphen be causing this? Also, which version are you building, TBWinRE, or TBWinPE?

 

LOL ,who knows? I didn't edit anything in there (ini file). Actually I never touch such ini file.

 

Perhaps try editing your TBWinRE.ini file to reflect your ifw.ini, at least as far as the license presentation. It's odd that it even has a TBWinRE.ini file to begin with. I have one too, but it's a placeholder recreated every time in case the TBWinRE cannot find a valid ifw.ini file. If you delete your TBWinRE.ini file are recreate the image, what happens? If that TBWinRE recreated?