frustrated999
Distinguished Member
I have two separate questions here regarding adding a new controller:
1) Looking at installing a separate SATAII controller in a couple of boxes here which currently only have SATA1 controller on board. For a test I copied the two primary partitions from my main hard drive on one of these machines to a spare SATA2 hard drive I have connected to the new controller. I disconnected the main hard drive so that there is currently only one hard drive in the machine connected to the new controller.
First primary partition is Win7 which boots fine. Second primary is WinXP which does not boot. The boot process is trying to open partition(1) in a boot.ini file. As far as I can determine the partition(1) parameter should be in fact partition(2) in this case or am I wrong? I tried finding this entry in a boot file but I can not find it. I am using the current build of EasyBCD to create the boot entry for XP automatically. Any idea what is going on here?
2) Another computer here which I am thinking of adding a SATA2 controller has SATA1 right now. This computer is using Hide 'N Seek and has Windows XP in the first primary partition followed by Windows7 in a second primary partition. I want to remove XP all together so that Win7 is the only o/s on the drive. Then I want to move the hard drive to a SATA2 controller.
I was thinking of telling Hide N Seek to start over again so that it is no longer in used.
While the hard drive is still connected to the current controller and after deleting XP Is there any way of moving Win7 partition to the beginning of the hard drive and still have it boot properly? Is using the Win7 boot DVD and Repair option the best way to fix the boot problem after the partition is moved?
1) Looking at installing a separate SATAII controller in a couple of boxes here which currently only have SATA1 controller on board. For a test I copied the two primary partitions from my main hard drive on one of these machines to a spare SATA2 hard drive I have connected to the new controller. I disconnected the main hard drive so that there is currently only one hard drive in the machine connected to the new controller.
First primary partition is Win7 which boots fine. Second primary is WinXP which does not boot. The boot process is trying to open partition(1) in a boot.ini file. As far as I can determine the partition(1) parameter should be in fact partition(2) in this case or am I wrong? I tried finding this entry in a boot file but I can not find it. I am using the current build of EasyBCD to create the boot entry for XP automatically. Any idea what is going on here?
2) Another computer here which I am thinking of adding a SATA2 controller has SATA1 right now. This computer is using Hide 'N Seek and has Windows XP in the first primary partition followed by Windows7 in a second primary partition. I want to remove XP all together so that Win7 is the only o/s on the drive. Then I want to move the hard drive to a SATA2 controller.
I was thinking of telling Hide N Seek to start over again so that it is no longer in used.
While the hard drive is still connected to the current controller and after deleting XP Is there any way of moving Win7 partition to the beginning of the hard drive and still have it boot properly? Is using the Win7 boot DVD and Repair option the best way to fix the boot problem after the partition is moved?