Personal choice. It does take up a primary partition slot so that can be a disadvantage for some. It is essential for booting (if it's present) so if your drive fails you need to restore the SRP and the OS partition to a new drive otherwise Win10 won't boot because there are no booting files. In my Win10 MBR computer I prefer no SRP. I note you have 348 GB of Free Space in your Win10 partition. If you wanted to use BIBM to multi-boot, you have stacks of space for a test Win10 and a Linux OS. Also TBWinPE and IFL partitions. Edit ... The SRP is necessary for those using BitLocker.
Hadron, I've been looking at putting backup/restore scripts into TBLauncher. They work. Code: [Menu_Item_13] Name=Restore_Win10 Path=%ProgramFiles%\Restore\Restore.cmd WorkingDir= Parameters= Icon=0 Create the script by running IFW in Windows. On the Summary screen click Save for TBWinPE, click OK, choose Desktop, File name of Restore.cmd, Save. Copy Restore.cmd to a folder named Restore. Deal with the Restore folder in the same fashion as DS and Explorer++ folders. You can have multiple Restore or Backup folders, each with different names of course. Start your tests with a backup script for your 500 MB partition. Progress to restore scripts when you feel comfortable.
Thanks, Brian. I haven't had a chance to look into that one yet. I've been busy doing other things. So, what does Restore.cmd do for me in practical terms?
I will think about getting BootIt Bare Metal also. I have never really bothered with booting multiple operating systems from the one computer. But maybe...
Hadron, It's for enthusiasts. Instead of clicking through the restore windows you do the restore with a single click. It suits me as I do lots of test restores.
If you used a Microsoft multi-boot on your SSD you could only have two Windows OS. Then all 4 of your partition table slots would be filled. If you used a BIBM multi-boot on your SSD you could have over two hundred OS. Not that you you would ever do this but BIBM supports independent OS with no sharing of booting files. With Microsoft multi-booting, each OS has its booting files in the initial Windows OS partition. If this partition is deleted or corrupted, the other OS won't be able to boot.
There must be a better workaround or fix for this. Can the developer do something about it, or can the Video Mode be pre-selected somehow?
I've never had to type 1fb before. Here is TeraByte's recommendation... https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=3257 https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=871
Hadron, you can edit syslinux.cfg in ifl.bin and 1fb will boot. But this takes several minutes and typing 1fb only takes a second.
Brian, I thought that you said that it's happened to even you in a previous post. Edit. It's in Past # 141.
That was ambiguous. By "before" I meant prior to this particular IFL bootfile. I have to type 1fb every time with this bootfile. Previous IFL bootfiles (I used them several years ago) didn't need 1fb. Edit... I don't use IFL bootfile as I have an IFL partition (bootable) on my SSD. With the bootfile, it only works if you can get into Windows. With a bootable IFL partition, it works if Windows won't boot.
Hello @Brian K , I have a quick question for you. I have never used BIBM before and am going to use it on an old system. I have wiped my hard drive and installed BIBM on the clean drive. The first thing that I noticed was the size difference compared to BIU (BIBM is only 5 MB). I assume this is normal and OK. I am going to install Windows, ubuntu, and three imaging partitions (Macrium, IFW, and IFL) when the next Windows 10 version is released. I am assuming that I will proceed pretty much the same as when I have used BIU. Can you think of anything that I may need to be aware of as to differences between the two as I proceed?
Kent, 5 MiB is a typical BIBM partition. Some background. BIBM handles the partitions differently. GPT allows 128 primary partitions per drive. MBR only allows 4 primary partitions per drive. BIBM creates an Extended MBR (in LBA 1 to LBA 62). The EMBR can hold more than 200 Primary partitions. But at any one time the MBR partition table can only hold 4 primary partitions. So only 4 primary partitions (per drive) can be seen in Windows and Linux. BIBM allows you to choose which 4 (or less) primary partitions you want to use with a particular Boot Item. For example, your partitions might be... Win10 Win8 Data1 Data2 TBWinRE IFL Mint Ubuntu BIBM Your Boot Item for Win10 could be... Win10 Data1 or Win10 Data1 Data2 The other partitions aren't in the MBR partition table of LBA 0. So they aren't seen in Windows. They are represented by Unallocated Free Space in Disk Management. This is why you must not use other partitioning and probably other imaging software as only TeraByte apps can see the partitions. It would be easy to over-write partitions that the non-TeraByte software can't see. If you run BIBM in Limited Primaries mode (I don't) then you can't have extra partitions in the EMBR and all partitions are seen in Windows. You (Kent) need to use Unlimited Primaries as you want more than 4 primary partitions on your drive. In BIBM Settings, remove the tick from Limit Primaries. Page 74 in the BIBM pdf explains how to install an OS. Windows or Linux. Basically it involves creating the OS partition, creating a Boot Item, deciding which partitions you want seen (MBR Details section using Fill and Clear), doing a sham boot of the Boot Item to set the intended OS Active and then installing the OS. You don't need to have the BIBM partition in the MBR Details. That would waste a partition slot. To install a Linux OS you must be careful to install the booting files in the partition and not in the MBR. See "Something else"... https://www.terabyteunlimited.com/kb/article.php?id=279 https://www.terabyteunlimited.com/kb/article.php?id=281 Any questions?
I'm confused by Section 6 in the BIBM pdf. I don't use that section. After creating the Boot Item I try to boot it from the BIBM Boot Menu. A sham boot. It will fail to boot as no OS is present and you will see an error message. This has set the partition Active. Insert your Boot Media, press Ctrl-Alt-Del and use your Fn key to bring up the Boot Menu.
I found one of my tutorials... Now to set Win10 partition active and install Win10 Click Resume Try to boot the Win10 entry. It will fail of course and give an error message but this procedure loads the relevant partition table (as seen in MBR Details) and makes the Win10 partition Active Press Alt Ctrl Delete to Restart (don't follow the error message) Boot from the Win10 UFD Install Win10. Choose Custom. Install to the 40000 MiB partition on HD0. You will see it is marked System. Don't start if it isn't marked System. When installed, play around with the Win 10 OS and restart it a few times. BIBM will be Deactivated by the Win10 install. When you are ready to use BIBM again, boot the BIBM UFD and select Reactivate BootIt Bare Metal. OK. You will be instructed to remove the boot disk and click OK to restart the computer. Now your Boot Menu will be present.
Hello Brian, I pretty much understand your above posts. I do not have the time right now to read the two links you posted but will do so tomorrow. I guess that there is really no need to install Macrium as a backup imager since it would not be able to see or backup all of the partitions...
Creating Boot Media partitions. TBWinRE, IFL, Macrium, etc. As before. Copy the UFD partition (not drive) to Free Space and choose your desired resize. Create a Boot Item.
Hello Brian, Thanks for all of the tips... Regarding ubuntu, on my BIU system (Dell XPS 8920 i7-7700 with 40 GB ram), I do not use a swap file. With BIBM on a 15 year old HP 64-bit system (AMD Phenom with 16 GB ram), would I need a swap file?
Kent, you don't need a swap partition. My netbook has 2 GB of RAM and Mint runs fine without a swap partition.
BootIt Bare Metal sounds like it might not be as easy to use as BootIt UEFI. Or is that just the way I am reading things?
