Mr.X and Nate, Would you like to try this? It uses the GUI in the recovery environment rather than in Windows but I don't see how this is a disadvantage. You have already created a TBWinRE/PE as you need this anyway for a restore when Windows won't boot. Make a batch file like this, double click and your computer reboots into IFW. You don't need a UFD. Code: "D:\tbwinre\tbwinpe.exe" /bootwim "D:\tbwinre\ISO\sources\boot.wim"
Unfortunately a script has fixed information. Any change needed you need to edit the script let alone create it in the first place. Me too, I don't have any problem using any. I know this Brian. No doubt at all but this is not the scenario I'm talking about. Imagine the following scenario: My sister living in another city asks for computer support. 1. New computer never touched by me. 2. Computer has a software issue, a bad uninstall is messing with Windows functionality. 3. I cleaned all the mess now all is good. 4. I need/want to do a system image, quickly. 5. Drop DS portable on desktop and launch it and make an image to an ext drive. 6. I try to install again her desired software but things get worse for whatever reason. 7. Drop DS again on desktop of the running OS and start an image restore, easy fast and reliable with DS. No creation or editing any scripts. All machine restarts are done automatically without editing anything or placing files here and there.
Mr.X, I like the scenario with your sister's computer. All done over the phone? Do you connect to her computer?
Truth is IFW needs to develop automatic reboot/backup/restore feature. It would be wonderful a IFL environment when the computer restarts
Mr.X, I'll contact TeraByte with your suggestion. We've agreed there is no difference in clicking through the GUI inside or outside of Windows. We all know we need bootable recovery media in case we can't boot into Windows. So after creating media, open IFW, Settings, Create Boot Media (Windows), TBWinRE, Modify the installed Windows Recovery Environment (WinRE). This only has to be done once. To do a restore, hold down Shift and click Restart. The computer boots into TBWinRE. Click TBLauncher on the left, double click Image for Windows, do the restore. Any issues with this method? No scripts to use.
For me, it would be nice is restores could be completely, automatic; no clicking anything at all after setting the restore from within Windows. This method is not. Having it be able to reboot into a restore environment restore the already-agreed-upon image, and restore normally after would be nice. That way I can walk away and this process will complete without my intervention. But we've been discussing this for years. Terabyte seems to not want to implement anything like this, much like Macrium with imaging of flash drive. Of course that changed with version 8, so maybe there's hope.
For me, completely automatic restores mean not using the GUI at all. Either before or after the reboot. I've been doing that for years.
Except that restores that way are not completely automatic, as we've discussed before. They require renaming. To understand what I mean, I wish IFW had something similar to Macrium Refledct and Drive Snapshot. Again, as we've discussed before. Apparently, I'm not the only one either.
That was just so you could use my test computer script. In my test computer the most recent image is always 10_01.TBI and this image is restored 99% of the time. So the script and image name don't need to be edited. At one time we both used the same backup script which led to the most recent backup always having the same name. I can't recall if I've changed that script. Maybe you are using a different one.
Really? that would be so great, thank you. Yes we have. Without a doubt. Didn't try but I'm sure it works out but you know my needs. As for the gui-based (no scripts) automatic restore/reboot feature instead of a DOS (like DS) or a WinPE (like MR) after machine restarts, an IFL environment would be so so nice and fast. If Terabyte Unlimited implemented such IFL environment, the setup would take less time and disk space. IFL files are so small, less than 70 MB compared to a WinPE.
See there: https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=2736&p=14720#p14720 Sôôô difficult and complicated! As often with terabyte, you must be a professional to uderstand!
Yes I did the other day. I hadn't used before and when I did it l liked it. However I prefer Terabyte's unlimited technology. That's why I want them to implement something similar for IFW. Not similar to Macrium Reflect.
No I didn't, why. I want to make clear I like the way DS boots automatically and starts to restore in a DOS like environment but I think is not, I need to look at it later today. I want anything similar to be implemented for IFW, don't want anything like MR style such as a WinPE. MR puts a huge amount of files in a Windows hidden folder named Boot.
I have been working with IFW for a very long time (I believe my first release was 1.20 !!) and I have to admit that it is a software that is extremely reliable. Personally, I have never had a single problem with it. What is correct is that it is getting more and more complicated to use. There are so many options, and when doing a restoration, you can't go wrong. It was much easier at first. Other example :Terabyte has also realized BING (the ancestor of BIBM) in which there was the possibility of saving the first sectors of the HDD on a floppy disk. One button and done. Currently with BIBM this is no longer possible: one has to work with one or more scripts and I never understood how! Not to mention the restoration of these first sectors! I am interested by Drive Snapshot because we can see that there is a real programmer behind this software (which is obviously also the case with IFW). This is easily seen because the .exe is barely 500Kb. And yet it is very comprehensive. But when it comes to disk images, we must be sure that the product is almost perfect! As for restoring in DOS, I don't think that's doable in UEFI. Personally I bought (at minimum price) a small capacity hard disk (80 gigas) on which I put Ventoy. And in Ventoy I put the ISO of IFLinux and I placed imagew64.exe (5megas!) in the Windows (of Ventoy). If there is a problem, F11, boot to the disk that contains Ventoy and done.
As I said above, I believe is not a DOS environment, is not a different OS which boots to start the restore process. I need to look later today but I believe it's the same DS executable using CMD line scripts cause the first thing you see when the machine begins to boot from the HDD is Windows itself. This is what I'd like to see in IFW.
