home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Software
Tools and other software
FREE Acronis Drive Image tool
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="VdR" data-source="post: 541245" data-attributes="member: 25818"><p>Thank you guys for the reactions. The discussion is helping me to understand this better.</p><p></p><p>I have done a lot of reading up on the issue. I did meanwhile find out that the MBR is seperate from any of the partitions. But the failure was the missing NTLDR (boot loader). The MBR must have been fine, else the system would not have been able to inform me about the missing boot loader.</p><p></p><p>From what I found out, the boot loader and other boot related files such as boot.ini (which holds the information about where the boot partition is or boot partitions are) are part of the system partition. This diferentiates the system partition from the other partitions. And that's why I beleive that you cannot restore a non-system-partition image to the system partition.</p><p></p><p>The MS terminology of system partition and boot partion is somewhat counter intuitive;</p><p></p><p style="margin-left: 20px">The system partition holds the information about booting (and possibly but not mandatory a bootable OS). The information includes (boot.ini) a list of partitons which have a bootable OS installed (boot partitions).</p><p></p><p style="margin-left: 20px">The boot partitions hold a bootable OS.</p><p></p><p></p><p>Please correct me if I'm wrong.</p><p></p><p>VdR</p></blockquote><p></p>
[QUOTE="VdR, post: 541245, member: 25818"] Thank you guys for the reactions. The discussion is helping me to understand this better. I have done a lot of reading up on the issue. I did meanwhile find out that the MBR is seperate from any of the partitions. But the failure was the missing NTLDR (boot loader). The MBR must have been fine, else the system would not have been able to inform me about the missing boot loader. From what I found out, the boot loader and other boot related files such as boot.ini (which holds the information about where the boot partition is or boot partitions are) are part of the system partition. This diferentiates the system partition from the other partitions. And that's why I beleive that you cannot restore a non-system-partition image to the system partition. The MS terminology of system partition and boot partion is somewhat counter intuitive; [INDENT]The system partition holds the information about booting (and possibly but not mandatory a bootable OS). The information includes (boot.ini) a list of partitons which have a bootable OS installed (boot partitions).[/INDENT] [INDENT]The boot partitions hold a bootable OS.[/INDENT] Please correct me if I'm wrong. VdR [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Tools and other software
FREE Acronis Drive Image tool
Contact us
RSS
Top
Bottom