TrueImage Home 2010 cloning problem

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 3

I have a Viliv S5 with 60gb Samsung HDD running Windows 7 Pro. That operating system was installed by Dynamism (US rep for manufacturer of Viliv) replacing Windows XP. The machine can be erratic at times (crashes) and Dynamism support believes it is a hardware problem (hard drive). I wish to replace that HDD with 30gb Runcore SSD.
Runcore ships the device with TrueImage Home 2010 (which I already have installed on the Samsung HDD) and an external enclosure and USB cable. Their instructions are to install the drive in their enclosure; install TrueImage Home; clone the drive; and then replace the HDD with the SSD.
For some reason that I don't understand there are 2 partitions on the hard drive. A small one (something like 100mb) that is called Secure. The rest of the drive is C: drive.
When I try to clone the old drive, TrueImage will go through check, ask to reboot, load, go through cloning of first partition, and start cloning the large partition (step 4 of 5). Without battery charger connected it will get to about 12% and machine shuts off. If I connect the battery charger it will get to 30-40% before shutting off.
I have created an image of the HDD and recovered it to the SSD (installed in Viliv) but when I try to boot from that, error message says something like BOOTLOADER is missing. I either need that file or figure out how to clone the SSD.
Do I need a powered USB hub (I don't have one) or are there any other suggestions from this group?

Sun, 11/28/2010 - 20:59
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 3

The answer was right in front of me but it took several days to figure it out. Windows 7 Power scheme was shutting machine down. After changing everything to "Never" (or Always On) cloning progressed just fine.

Wed, 12/01/2010 - 15:18