I tried to clone my primary hard drive to another internal hard drive via Acronis True Image. The version I'm using is 9, because I purchased it some time ago, but I've used this same version before successfully; my current setup was cloned from another hard drive using this same version. However this time the cloning failed (it seems to me that it was never really attempted by True Image), and now I can't boot normally from my primary hard drive - I have to use Safe Mode instead if I want to get into Windows. I started the True Image for cloning after quick formatting the destination hard drive. I clicked the reboot button inside True Image, and after reboot the blue "analyzing partitions" screen came up. However after it was done analyzing partitions, it appears that it skipped the cloning step and went straight to the "Congratulations..." message, which only displayed for a few seconds before my computer powered down. After I turn the power back on, the Windows XP logo comes up - but after that, my monitor goes blank and says "no signal". The computer is still on, but doesn't respond at all. Hitting control+alt+delete doesn't do anything. I have to either hit the computer's reset button, or force a power down by holding down the power button. The blue checkdisk screen follows the XP logo after I reset a few times, and does a disk check and reboots. But after the reboot, things are the same as before - following the XP logo, the monitor says "no signal" and the computer does nothing. I can still boot Windows in Safe Mode. I tried running True Image again from inside Safe Mode to see if running it again would fix things. It did not; same as before, after it analyzed partitions, it shut down without ever cloning, and Windows still can't boot up normally, only in Safe Mode. I then tried it for a 2nd time from Safe Mode (3rd time overall), this time I think it analyzed partitions a couple times and rebooted both times, but Windows still can't boot normally. What possible fixes might there be for this failure to boot the OS? Is this a problem that's been encountered previously?