Jump to content
Posted 02 October 2007 - 08:32 AM
Posted 02 October 2007 - 03:13 PM
Posted 02 October 2007 - 06:11 PM
Posted 02 October 2007 - 08:47 PM
Posted 02 October 2007 - 09:08 PM
Posted 03 October 2007 - 06:29 AM
Posted 04 October 2007 - 12:35 PM
Posted 04 October 2007 - 05:49 PM
Posted 04 October 2007 - 08:59 PM
Posted 05 October 2007 - 04:56 AM
Vista uses different files - these ones are just a hangover from the original XP installation and the new Vista boot sector placed on Disk2 points to the Vista and not the XP boot files on the System Partition on Disk 2. They, in turn, were then loading Vista on the boot partition on Disk 0.
Not sure but it makes sense unless Vista uses a different type of Boot ini, ntldr, and NT DETECT.
Disk Management System Partition is the partition booted FROM.
Disk O: Basic 298 Gigabytes OnLine Computer (V) drive (Vista) Healthy, Boot, Page File, Crash Dump, Primary Partition
Disk 1: Basic 149.01 Gigabytes OnLine Computer (D) drive-Healthy Primary Partition 78.13 Gigabytes and Computer (E) drive-Healthy Primary
Disk 2: Basic 93.37 Gigabytes OnLine Computer © Windows XP drive Healthy, System, Active Partition 13 Megabytes unallocated
Edited by komski, 05 October 2007 - 05:07 AM.
Posted 05 October 2007 - 06:54 AM
Posted 05 October 2007 - 07:46 AM
Posted 05 October 2007 - 09:02 AM
Edited by uhaligani, 05 October 2007 - 09:16 AM.
Posted 05 October 2007 - 09:26 AM
Posted 05 October 2007 - 11:08 AM
Fdisk has a number of options which include just looking at the partition information and of setting an active partition. The former writes nothing to the drive and the latter only changes one byte on the mbr from 0x00 to 0x80 and doesn't touch the boot sector at all. The greatest risk is probably doing things to the incorrect hard drive by mistake. BootIt-NG would be my own favorite app for these manoeuvres nowadays.
If you Fdisk V: you will totally screw up your Vista bootsec.
0 members, 0 guests, 0 anonymous users