Cruise, glad I could help. Once you get the hang of "Partition Work" it is easy. But not so easy the first time.
That makes two of us! Thanks again for lending your Terabyte expertise. Brian, would you explain the reasons behind each of the steps in your instructions, including why ticks (in tick-boxes) were or were not needed? That would go a long way in my Partition Work learning process. Cruise
Is this just inconvenient or are you saying because of this you would not rely on MiniTool? Everything was there in the end?
Cruise, OK. The boot sector is the first sector in every partition. If you delete a partition you just remove its entry from the LBA-0 partition table. The partition data is still present on the HD so the partition can be Undeleted and everything is back again. When you delete a partition in Disk Management the Boot Sector isn't cleared so you can go into BIBM and Undelete the partition. But if you know that you will never need to Undelete the partition, clear the Boot Sector as it's not ideal to have lots of irrelevant Boot Sectors on the HD as it makes Undeleting wanted partitions difficult. Wiping is very time consuming and is rarely needed. Maybe when you give your HD to someone and you don't want them to recover sensitive data. Sliding. You can slide up or down. Sliding up can be slower than down. If you remove the tick from "Data Only" you will get a "GParted type" slide. I have never used that type of slide in BIBM. See my "Times" above. Resizing. To make a partition larger is fast. To make a partition smaller may be fast or slow. It will be slow if sectors have to be moved to fit inside the smaller partition. For example, you have a 500 GB partition with 100 GB of data. That 100 GB of data can be scattered over the 500 GB. So if you resize that partition to 200 GB then you can understand why it can be "slow". On the other hand, if the data is in the first 200 GB then the resize will be fast. Anything specific you need to ask? To learn BIBM I suggest using it on an old computer where it doesn't matter what you do to the HD. Or remove the HD from your computer and work on an old blank HD.
trott3r, I'm not saying it is unreliable. I just don't like the way it has "un-optimized" the OS partition. On a data partition it probably doesn't matter.
Moving partitions is not a good practice. It´s prone to cause problems, no matter what software is used, and it usually can be replaced by operations with images, which are more reliable and can be faster.
Robin, I've been moving partitions for over ten years and never had a problem, except when I pull the power plug out of the wall (deliberately) during the process. Edit... I do all partitioning procedures from boot disks. I recall folks getting into trouble using Partition Magic in Windows.
Cruise, You have TBOSDT for BIBM. It can do command line partitioning. You can create batch files that perform multiple partitioning procedures. Now that's something most people would avoid but I had to use it on an ASUS tablet that only booted UEFI disks. BIBM wouldn't boot. IFL wouldn't boot because of the Atom processor. I ran TBOSDT from a WinPE. The lines are instructive... add partition 0 0x82 8000 7 DATA1 2500 /a=2048 This will create a primary partition on HD0 0x82 is the ID of the unallocated free space where you want the new partition 8000 is the partition size in MiB 7 is NTFS DATA1 is the partition label 2500 is the Free Space Before /a=2048 is the alignment Other lines are... del partition 0 0x01 resize 0 0x01 3500 /a=2048 slide 0 0x01 1500 /a=2048 copy partition 0 0x01 1 0x81 1000 /a=2048 SET PART ACTIVE 0 0x01 SET MBR SIG 1 0xA3C77D1F This is a batch file I have used to remove the Win7 System Reserved Partition list hd 3 interactive open fs 1: 3 0x01 open fs 2: 3 0x02 copy 1:Boot\* 2:Boot\ /s copy 1:bootmgr 2: close fs 1: del partition 3 0x01 close fs 2: set part active 3 0x02 slide 3 0x02 0 /a=2048 resize 3 0x02 /a=2048 reboot Edit... The batch file copies the booting files in the SRP to the Win7 partition. Deletes the SRP. Sets the Win7 partition Active. Slides Win7 to the front of the HD. Resizes Win7 to fill the unallocated free space behind it.
Brian, just a couple of comments re the above post. 1. I am not at all comfortable using command lines or scripts. 2. My W7 no longer has a system reserved partition. I removed it long ago using the Terabyte KB on the issue. Cruise
Cruise, Sorry, I wasn't suggesting you even trial TBOSDT. I just mentioned it in case you were ever stuck in a situation like my UEFI Asus VivoTab. TBOSDT was the only solution. You probably know that IFL contains Partition Work. Almost identical to Partition Work in BIBM and it boots in UEFI systems. But not Asus VivoTabs as no Linux disks will boot.
Yes, I am aware of that but I seldom use IFL. I typically backup and restore with the much more user-friendly IFW. I will even opt for user-friendly IFD over IFL, but that's just due to my PC comfort-level.