![]() |
|
|||||||
| Acronis Forum Sections Closed! |
| As of August 15, 2009: Please be aware that the Acronis Forum sections have closed. No new threads or replies may be made in these sections. See this announcement for more information. |
|
|
Thread Tools | Search this Thread |
|
#1
|
|||
|
|||
|
ok, here's the problem.
Computer 1 - Dell optiplex system with standard IDE drive - windows xp pro. Computer 2 - HP/compaq system with SATA drive - pre installed xp pro. Step 1: Using True Image 10 - Created image of computer 1 using backup, My Computer, NTFS (C Pri,Act. Selected my NAS device and everything went fine with no errors.Step 2: Created Bootable CD using Create Bootable Rescue Media. Once again no problems. Step 3: Fired up new computer with boot CD. Tell the system to restore my computer and point to the image file I just created stored on the NAS. Everything goes fine. Now the problem: As soon as I reboot the machine it gets a hardware failure on boot. "Windows could not start because of a computer disk hardware or config problem. Could not read from the selected boot disk. Check boot path and disk hardware." What I've tried Fired up the windows os cd and blew away the partition and had Acronis recreate it from the image trying another restore. - Reboot = Same exact error message. I have read the "cloning a windows system" method with using sysprep but I don't think this will have any effect with the current problem because it seems only to remove configuration relating to the SID and computer name - which I'm not concerned with. Anyone? Thanks! |
|
#2
|
|||
|
|||
|
Maybe the fact the hardware is different and as such the drivers included in the image are not correct. How ‘bout a Windows Repair Install?
|
|
#3
|
|||
|
|||
|
I found how to repair it.
PITA but it will work If anyone else has this problem.. Look up Microsoft Article 31447 for windows XP. The part that really blows is you need to reactivate windows which means more than likely you will need to call them becuase your copy is already reg. I followed method 2 which is to use the bootcfg utility to rebuild the boot.ini file. I still need to reboot yet to test it out completely. I'll keep you posted. I think the problem has to do with a system with IDE going to SATA... but not sure. Maybe support will chime in on this one. |
|
#4
|
|||
|
|||
|
Quote:
Dude. The article you're referring to is 314477, not 31447. Took me 25 min to figure out that little error. So....how'd it turn out? |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|