How move XP HDD (under PM7) to new PC?

  • Thread starter Thread starter driver
  • Start date Start date
D

driver

I want to move my WinXP Pro hard drive (40gb, partitioned into
C:,D:,E:,by Partition Manager 7) to a new PC I am building (new
mobo,cpu, DDRAM, graphics card). I have tried Michael Stevens' "Move
XP" guide....repair(http://www.michaelstevenstech.com/moving_xp.html)
but XP Setup does not recognise the boot and partition info,
presumably because it was created by PM7. Is there any way round this?
My WinXP Pro is an upgrade version (from WinME). At the time I did a
clean install but could not get WinXP Setup to let me partition the
HDD into 3, which is why I had to resort to PM7.
Any solution would be much appreciated.
 
driver said:
I want to move my WinXP Pro hard drive (40gb, partitioned into
C:,D:,E:,by Partition Manager 7) to a new PC I am building (new
mobo,cpu, DDRAM, graphics card). I have tried Michael Stevens' "Move
XP" guide....repair(http://www.michaelstevenstech.com/moving_xp.html)
but XP Setup does not recognise the boot and partition info,
presumably because it was created by PM7. Is there any way round this?
My WinXP Pro is an upgrade version (from WinME). At the time I did a
clean install but could not get WinXP Setup to let me partition the
HDD into 3, which is why I had to resort to PM7.
Any solution would be much appreciated.


due to the different hardware, your XP prob would not have worked anyway
you may want to at least try a repair instalaltion however
 
philo said:
due to the different hardware, your XP prob would not have worked anyway
you may want to at least try a repair instalaltion however

I had tried a repair install, following Michael's guide, but this
failed, which was why I posted. It failed, as best I can tell, because
WinXP Setup did not recognise the partition table created by PM7, nor
the boot record. It saw a single 40GB partition, not the 3 x 13.3GB
that WinXP had run quite happily for a year.
My worry is that if I let XP Setup repair what it thinks it sees,it
will rewrite the partition table and MBR, ignoring the existing
records, and thus I lose access to my logical partitions.
That is the problem I am trying to get round.
Help would be much appreciated.
 
philo said:
due to the different hardware, your XP prob would not have worked anyway
you may want to at least try a repair instalaltion however

I had tried a repair install, following Michael's guide, but this
failed, which was why I posted. It failed, as best I can tell, because
WinXP Setup did not recognise the partition table created by PM7, nor
the boot record. It saw a single 40GB partition, not the 3 x 13.3GB
that WinXP had run quite happily for a year.
My worry is that if I let XP Setup repair what it thinks it sees,it
will rewrite the partition table and MBR, ignoring the existing
records, and thus I lose access to my logical partitions.
That is the problem I am trying to get round.
Help would be much appreciated.
 
I had tried a repair install, following Michael's guide, but this
failed, which was why I posted. It failed, as best I can tell, because
WinXP Setup did not recognise the partition table created by PM7, nor
the boot record. It saw a single 40GB partition, not the 3 x 13.3GB
that WinXP had run quite happily for a year.
My worry is that if I let XP Setup repair what it thinks it sees,it
will rewrite the partition table and MBR, ignoring the existing
records, and thus I lose access to my logical partitions.
That is the problem I am trying to get round.
Help would be much appreciated.


If there is any way you can slave that drive into another win2k or XP
machine
I would do so...and see if you can view the partitions and recover your
data.

also, you may want to run partition magic from a boot floppy (requires two
actually) it may detect and error and ask you if you want to correct it.
NOTE: there is a possibility that the utility could make things even worse!
 
driver said:
I had tried a repair install, following Michael's guide, but this
failed, which was why I posted. It failed, as best I can tell, because
WinXP Setup did not recognise the partition table created by PM7, nor
the boot record. It saw a single 40GB partition, not the 3 x 13.3GB
that WinXP had run quite happily for a year.
My worry is that if I let XP Setup repair what it thinks it sees,it
will rewrite the partition table and MBR, ignoring the existing
records, and thus I lose access to my logical partitions.
That is the problem I am trying to get round.
Help would be much appreciated.

As also happened to me when I needed to do a repair install, as I stated
in another thread. The repair install in my circumstances also messed
up the partition information. Changing a 30gb partition down to just
3gb and a 9gb partition down to about 5gb.

I was trying to upgrade an old HD containing XP to a new HD, but the new
one would not boot into windows without requiring, in M$'s solution, a
repair install. Not only did the repair install muck up the partition
info, but also removed all startup references, caused the M$ office
programs to ask for the cd when they were started (not sure about other
apps.) and also meant that all M$ updates would need to be re-
downloaded. I have tried to figure out a way to avoid this problem, but
as yet no-one has been able to come up with a definitive solution.

Unfortunately, I am unable to get access to the problem computer for
long enough to try out various potential solutions that I have thought
up for myself. :(

I hope you have more success.
 
philo said:
If there is any way you can slave that drive into another win2k or XP
machine
I would do so...and see if you can view the partitions and recover your
data.

also, you may want to run partition magic from a boot floppy (requires two
actually) it may detect and error and ask you if you want to correct it.
NOTE: there is a possibility that the utility could make things even worse!

Thanks, philo.
I have run the PM floppies,they found no errors.
I am going to put a spare drive in the new PC and try to set up XP on
that to see if that works or if there is something else in the PC
which is the problem.
I will report the results.
Thanks to everyone for the comments & suggestions.
 
Back
Top