The short version of my problem is this: I have a disk with two primary partitions (1 = active and bootable, 2 = regular). I want to create a 3rd partition using free space at the end of partition 2, and then make this 3rd partition a clone of the 1st partition. At the end of this process, my disk should have three primary partitions (1 = active and bootable, 2 = regular, 3 = bootable). Now, here are more details on the issues I have encountered trying to do this: First off, I should mention that I actually have a second disk as IDE slave, and it has 4 primary partitions as follows: 1 - active and bootable 2 - bootable (Acronis Disk Director and True Image installed...let's call this my tools partition) 3 - regular 4 - regular I do not use Acronis OS Selector. Instead, I just always make sure to put ntldr, ntdetect.com, and an appropriate boot.ini file on the active partition of the IDE master, and that does the trick...much faster and simpler in my opinion. Now, on to the experiment! I boot into my tools partition. I have its OS set to mount the 2 partitions of the IDE master as F and G respectively. F, of course, is the active and bootable partition I want to clone. At this point, I need to make something clear: All three of my bootable partitions have variants of Windows XP installed on them, and all three are set so that they become the C partition when I boot into them! In other words, when I boot into the tools partition, the tools partition mounts as C, and the 2 partitions of the IDE master mount as F and G. When I boot into the partition that I want to clone, it mounts as C, and the 4 partitions of the IDE slave mount as J, K ,L , and M. In this case, K is my tools partition. Now, let's continue... I have booted into my tools partition, and first I create a full backup of F using True Image. Next, I use Disk Director to resize G so there is unallocated space at the end of the disk. Finally, I go back into True Image and restore the image I just created, using the new unallocated space as the destination, and choosing H as the drive letter (because I want the OS on my *tools* partition to mount this new partition as H). So far, so good... Now, the first hint I get that Acronis True Image is not supposed to be used in this way comes when I check out Windows Disk Management, where I notice that F is listed as (System) and H is listed as (Active). Doh! Two active partitions on a single disk!? This is not supposed to happen. Especially since when I did the restore I chose the option for Primary, not Active...and yet Acronis went ahead and made it active anyway! Furthermore, the "two active partition" problem cannot be fixed within Windows Disk Management! Apparently, I can fix this in Disk Director by choosing to edit the MBR, but I did not know about this feature at the time. Now, the next hint I get of Acronis screwiness is when I go to edit the boot.ini file on F, in order to enable booting into the new partition. Well, apparently Acronis screwed with my boot.ini file. The default ARC was changed from 0,0,0,1 to 0,0,0,2, as was the corresponding entry in [operating systems] section. Also, "WINDOWS" was changed to "windows" on the two altered lines, though this change in case probably doesn't matter. Nevertheless, I'm glad I noticed this, because as it happens, partition 2 is now the only partition on the IDE master that doesn't have an OS installed on it! Anyway, I changed the lines back to 0,0,0,1, and then added an entry for 0,0,0,3 in the [operating systems] section to enable booting to partition 3. My recollection of the experiment gets a little fuzzy at this point, but basically, I restarted, booted into the newly restored partition (can't remember what drive letter it mounted itself as), and about a minute after the desktop appears, I get an svchost process crash on me (something that has never happened to me before!). I try the reboot a couple more times, and continue to get the crashing. Anyway, this kind of thing makes me worry that I have created an unstable OS, so I boot back into my tools partition, delete H, and resize G to take the new space, basically putting myself back to square one. At this point, I decide to learn more about MBR's, and so look up MBR at wikipedia.org and start from there. I believe one thing that may cause problems is incorrect registry entrys in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. In particular, the entry for "\DosDevices\C:" will still point to the first partition, but we need it to point to the third partition, so that the OS partition will always mount to C, no matter what OS I boot into. But, is changing this one registry key enough? What other references might the registry have to the first partition? I don't know, and don't want to end up with yet another unstable OS. My final possible fix to the problem might be to just edit the MBR, changing the Disk Signature to some other random value. Correct me if I'm wrong, but since the OS in general, and the registry in particular, references a disk using the Disk Signature in the MBR, this change would cause the OS to see the disk as a "New" disk, causing it to "forget" everything it knew about the disk, and regenerate new and correct registry entries. I don't like this approach, though, since my other 3 OS's would also "forget" and I'd have to redo the drive letter mappings when I booted into them. Blah! So what's the solution? Surely someone out there knows the secret to cloning an OS partition to another partition on the same disk! Lisa B.