Hi me too , i like differentials , maybe in the *.ini file there is a way or an option to disable incremental backups thanks
There is no disabling to be done. Nothing relevant in the .ini. It's your choice whether you create differentials or incrementals. If you base the Changes Only backup on a Full backup you will get a differential backup. It can be done manually or from a script.
There are few issues being reported with TeraByte Drive Image Backup And Restore Suite v3.63. I just upgraded and tested IFW, and it seems to be working fine. I think the issues are confined to IFL. I don't use IFL.
Indeed, as Brian stated, differentials do not need to be disabled. BTW, I too, like Brian, prefer them. Slower when creating than incrementals, but faster (and more reliable) when restoring. Acadia
Out of pure curiosity, I installed this package terabyte_drive_image_backup_and_restore_suite_en_cui.exe for the first time. I don't see any difference between cui and gui versions though. Well at least there's none in my first impression. I must be missing something for sure.
The differences between CUI and GUI are also explained here. And if you hover your mouse over the two trial download links, a tooltip has some info about the installers. There is also a CUI/GUI screenshots link. I've only ever used the GUI installer.
How do you have access to TeraByte OSD Tool Suite Pro in a WinPE disc? I have access to it in the IFW utilities menu, but I don't have it in WinPE I can build a custom disc with the IFW builder but I don't want to recreate the disc every time there's an update. I'd rather use a custom disc I create via theoven. In that case, IFW would need to be portable. I can use imagew64.exe in my custom winpe, but I don't have access to TeraByte OSD Tool Suite Pro. Any ideas?
Don't you have access in the downloads page to the standalone tbosdt zipped file? Code: https://www.terabyteunlimited.com/product-download.php Spoiler
Yup. It's accessible in IFW within Windows, but not in a custom WinPE. The bottom line is, what good is it if you're restoring an image but don't have access to its scripts?
I'm on holidays and don't have access to a computer. I'm using my phone. Can you give me an example of what you are trying to do? Do you have something like Explorer++ in your WinPE? I assume your WinPE is not the standard TeraByte one, made using makedisk.exe.
@Mr.X is correct. Theoven is essentially a series of winbuilder scripts that lets you create winpe boot discs. These are custom and not from terabyte. You can user terabytes plugin with it. That will work, but you'll end up having to recreate the entire disc with every update. I'm looking to avoid that. Essentially, in Windows IFW seems like it's portable; imagew64.exe relies on ifw.ini and can be used without being installed. The same is not true for their OSD Tools. They require installation to be recognized in the IFW utilities menu and do not use the ifw.ini file. Meaning that I can use IFW in any custom winpe disk I build, but I cannot use their OSD Tools with them. Is there a way I can without recreating the disc each and every time?
Right. But that way uses the RE menu, right? I don't want that in a custom disc. Having the options appear just like they do in Windows would be ideal, but in custom winpe discs those options are not there.
@n8chavez Did you get a solution? I've found a not-so-elegant solution/workaround using a Strelec's WinPE thinking it's fully functional, I haven't tested it though:
What?!? I couldn't even get that working in WinPE 11-10-8 Sergei Strelec 2023.06.25; when I launch their included version of IFW there were no ready to run scripts there. Of course, I do not recommend using this. It's an illegal disc that uses stolen paid-for software. But I was curious, since @Mr.X said he was able to access OSD.
Try this. Put your IFW files and Tbosdt script files in the same folder in your WinPE UFD. Say a folder called 000. Open a Command prompt and CD to 000. tbosdtw64.exe runtbs osdtool.tbs You could also try double clicking tbosdtw64.exe in the 000 folder. If tbosdtw64 opens, then.... runtbs osdtool.tbs I can't test the above methods at present.
I guess it's just confusing me as to why IFW seems to be a functional portable app but OSD is not. It's not like users can run OSD hot anyway. Isn't the point of OSD scripts to be run outside of Windows? Why then make it so difficult to do just that?
More interesting is: why it is so difficult for you to just ask for the workaround? TB is not going to change their program to make it fully portable unless many others request for such functionality, I guess. 1. Download tbosdts_pro_en.zip 2. Unzip it in a folder 3. Boot your WinPE 4. Open the unzipped folder and run setup.exe 5. Install TBOSD Tools defaults, do not change anything in the installer 6. Run your standalone portable IFW 7. Scripts should be now available in the drop down menu