Thats right, it did not. I could not stay away so i tried it again, now it worked with the licensed version. Beautiful. But the switching with the usb is a problem. Goodnight.
I'm like that too. Can't sleep until it's done. Can you try this. Add --wco and --rb:8 switches to your script. Let it shut down. Then power up with the UFD in place. I hope that will work. I use --wco for all SSD restores.
Add where, please be specific. What will it accomplish? The actual restore takes 11sec instead of 23 with IFW, all in all, 67sec. IFW about 120sec if i remeber correctly. Nice.
Is this how you mean: sub main()<cr> exec("/tbu/imagel --r --uy --d:l0 --f:l0@0x5:^"/IFW W10/pb1^" --sp:0x1,0x2,0x4,0x6" --wco --rb:8", 1)<cr> end sub<cr> What does wco mean?
That's correct. --wco is Write Changes only. Say your partition contains 20 GB of data and you make a backup. When you restore that image tomorrow, if only 100 MB of data has changed then only 100 MB will be written to the partition. That is, less writes to the SSD. All sectors have to be read so the restore isn't any faster. It takes the same time as a restore without --wco.
I missed the * not being there... sub main()<cr> exec("/tbu/imagel --r --uy --d:l0 --f:l0@0x5:^"/IFW W10/pb1*^" --sp:0x1,0x2,0x4,0x6" --wco --rb:8", 1)<cr> end sub<cr>
Ok. Well that`s nice but since SSD:s last Shutdown of what, the pc? If so, what is the idèa behind that?
Immediately after the restore the computer shuts down. You don't have to do it. Then press the power button to start the computer and I'm hoping you won't have a USB issue.
Tried the new script. It did restore as it should but the Run Script frame showed up in the background saying: that the key, or was it command, was not valid. Please remember that the what`s in paranthesis is part of the name. Not exactly so but, something like it. But the actual restore went fine anyway. But it still looped when starting, so pulling the UFD is a must. To bad. The wco command is ok but i will stick with 4, not 8. Anyway, now i truely am going to bed so, goodnight. Or goodmorning, soon.
My mistake. Your script should be... sub main()<cr> exec("/tbu/imagel --r --uy --d:l0 --f:l0@0x5:^"/IFW W10/pb1*^" --sp:0x1,0x2,0x4,0x6 --wco --rb:8", 1)<cr> end sub<cr> I removed the " after 0x6
For what it's worth. IFL runs in RAM so as soon as the restore commences you can remove the flash drive. If you have --rb:4 you will restart into Windows and you can replug your flash drive. I'm different. I never leave flash drives plugged in. Or external USB HDs either.
I was wondering about that myself when doing the script. I shall try the script today with wco but without 8, 4 instead. What difference will the removal of " make?
That makes a real difference but not big enough, this handling of the UFD makes this option, compared to IFW, inconveniant in the long run. Not me either but for this type of action i would be ok with it since i am the only user and i trust my security. It would be real nice if Terabyte could make changes so the reboot could happen instead with a script command.
I don't use UFDs for restores. I have an IFL partition on the SSD which boots and does the restore. Also a TBWinRE partition. You need BootIt UEFI for this to work. I click a script in Windows, the computer restarts into IFL or TBWinRE, does the restore and restarts into Windows. No booting problems as with a UFD.
Sounds interesting, and smoooth. And Bootit UEFI has no full featured trial version i suppose? All this, and a possible future test of Booti UEFI, was and will be mostly out of curiosity, i actually do not restore all THAT much that i need something faster and/or better then IFW. But speedier, smother and more conveniant is always tantalising. Enjoy your holiday and the, soon to come new years eve, and, thank you! Happ
This tutorial on IFL branched into more complex areas. Most people using IFL will simply use standard IFL boot media to create and restore images on Windows computers. It's a fast, reliable app.
Hi Brian, I'm creating a IFL boot media (UFD) and came to this step in the wizard: If I enter my Name/Key, will I get a full featured BootIt Collection 2 like in bootit_collection_en_v2.zip package? See, I don't want to have two separated UFD for each program. I know I know, I could try and see but you are the expert having experimented a lot with these programs so it's better to ask...
Mr.X, You don't need two IFL UFDs. I always add the BootIt license information and get Scripting and Partition Work in IFL. Naturally you don't get the Boot Manager. In my computers, Partition Work runs faster in IFL than in BIU. So if I'm going to do a lot of partitiong, especially Slides, I'll do it in IFL. I rarely use the IFL UFD. After making the UFD, the UFD partition is copied to Free Space on a SSD and the SSD partition is resized to 150 MiB. A Boot Item is then created in BIU. IFL boots faster from a SSD than from a UFD. In Windows, you can create a BootNow shortcut so you can go straight from Windows to IFL without having to use the BIU Boot Menu. Convenient.
I had some spare time with IFL. I put 117 GB of data files in a partition and imaged that partition to another drive. NVMe to NVMe. The image size was 107 GB. The backup took 61 seconds. The image was then restored using the Metadata option. (Called a Delta restore by Macrium). The restore took 9 seconds. I also used the Restore Changed Sectors Only option for that restore and only 1 GB of data was written to the target partition. An interesting test with a large image.