Jump to content
Posted 13 May 2008 - 06:31 AM
Posted 13 May 2008 - 07:32 AM
Posted 13 May 2008 - 07:39 AM
Posted 13 May 2008 - 10:59 AM
Posted 13 May 2008 - 11:04 AM
Posted 13 May 2008 - 11:19 AM
A newly cloned drive may not boot under various circumstances.
IMO, lack of a proper boot.ini file is the most likely cause.
What software are you using to create these cloned drives/partitions?
Are you removing the previous drive and replacing it with the clones?
Are you attempting this with only the cloned partition/drive installed on the system...and the boot order reflecting the hard drive as the primary boot option?
If you attach one of these cloned drives as a secondary drive...with the original drive as the primary...can you see a boot.ini file in the files for the second/cloned install?
Posted 13 May 2008 - 11:20 AM
Posted 13 May 2008 - 04:38 PM
Well...if you created images which don't reflect a SATA driver for XP...they probably won't boot when attempted to be inserted as replacements...unless the images were made from an original SATA drive (which would mirror the clones in already having the SATA driver installed for the XP install to see).
I'm not sure the reverse would be true (if you mixed PATA and SATA drives in your cloning), but that error message seems to make sense to me (if I'm comprehending the possibilities correctly).
XP will not install on a SATA drive unless it sees that driver present. XP cannot install on something it doesn't see/recognize and it's only set up to recognize PATA drives without any additional drivers being inserted into the XP install.
What I might try is a repair install of one of these clones...with insertion of the SATA driver at the proper point in the repair install process. That should work, if I'm understanding properly.
Posted 14 May 2008 - 06:09 AM
0 members, 0 guests, 0 anonymous users