If I try to digest from various recent discussions on this forum, all the excitement about the MBR now being also included in partition images boils down to this. In terms of setting up a brand new system disk (after the old one has failed), the new feature introduced in Build 3567 brings no benefit to the partition imager. If he wants to avoid preformatting the new disk so as to mimic the structure of the old one, he will still need an entire disk image, as he did before Build 3567. Restoring the system partition only (as one of several partions from the original disk) as well as the included MBR (this one reflecting a multi-partition structure) will not guarantee a working new system disk. However, having the MBR included in single partition images will enable him to restore the MBR separately after a corruption, infection or other unwelcome modification. This, in my present wiew, is the only benefit of the new feature. Before Build 3567 the MBR was imaged and restored only within entire disk operations. This way the partition table inside the MBR always matched the actual partitioning layout being restored. Now the user can restore the MBR separately but it's upon him to assure that it will match the actual partition structure. Would anyone care to amend? I think it's most important to have this picture clear.