Weird MBR problem installing windows after repartitioning

  • Thread starter Thread starter cmccormick
  • Start date Start date
C

cmccormick

I'm having this weird issue when installing Windows on a new drive. I
used GParter to repartition the drive into a small system partition and
a larger data partition. When booting the windows CD to install, I see
what appears to be 2 hard disks, one called Disk on disk [MBR], another
called Disk 0 at Id 0, and another called Disk 0 at Id 1. I really
should only be seeing disk0id0 and disk0id1, but somehow the MBR is
also there.

When I attempt the install anyway to Disk0id0, after copying files and
rebooting, the computer just boots the windows CD again as if the drive
is blank (I assume because the MBR is empty or something). Does anyone
know what exactly could have caused this or know a possible solution?

Thanks,
- Coleman
 
(e-mail address removed) wrote
I'm having this weird issue when installing Windows on a new drive.
Click to expand...

Just because of the way you are partitioning the drive.
I used GParter to repartition the drive into a
small system partition and a larger data partition.
Click to expand...

No need to do anything outside the install CD. Just create
the system partition of the size you want very early in the
install and create the larger data partition later in disk
management once you have XP installed.
When booting the windows CD to install, I see what appears
to be 2 hard disks, one called Disk on disk [MBR], another
called Disk 0 at Id 0, and another called Disk 0 at Id 1.
I really should only be seeing disk0id0 and disk0id1,
but somehow the MBR is also there.
Click to expand...

Its likely just a weird way of displaying the first track on the drive.
Its not used for the partitions and likely is being displayed as a
sort of pseudo partition since it can be backed up independantly.
When I attempt the install anyway to Disk0id0, after copying files and
rebooting, the computer just boots the windows CD again as if the
drive is blank (I assume because the MBR is empty or something).
Click to expand...

It might be because you have the motherboard virus protection
turned on and that is preventing the MBR from being changed.
Does anyone know what exactly could have
caused this or know a possible solution?
Click to expand...

See above assuming that the 'windows' you mention is XP.
 
Back
Top