Page 1 of 1

HDClone Hangs Up after 19 minutes

PostPosted: Thu Oct 09, 2008 8:49 pm
by Ed
Hello,

I am cloning my Windows XP OS system to a new hard drive on the same computer. The source hard drive with the WinXP system has some bad sectors on it, hence, this is the reason I am replacing the hard drive with a new one.

When operating HDClone (Free Edition Ver 3.6.2), after 19 minutes into the clone, the software hangs up. Notably, there 114 Read Errors, and 0 Write Errors.

I have restarted the computer and reran HDClone from floppy, and the same thing happened two times. The first time it got to the point of 89 Read Errors, then hung up.

I am using a PC/2 mouse (no USB).

Please help.

Thanks.

--
Ed

Re: HDClone Hangs Up after 19 minutes

PostPosted: Fri Oct 10, 2008 9:58 am
by Alex
if by "Hung Up" you mean the sector number does not advance anymore (but mouse cursor still is working, as is the animated graphic during the copying process), then it's the fact that the erroneous drive has too much errors for the driver to bear, so it exits.

A complete hang (where the mouse cannot be moved anymore) should not happen and is something for the support (https://www.miray.de/support/index.php).

In any case, it is also necessary to know how the drives are connected: are both connected as IDE or S-ATA drives, or is one disc connected with an external USB or FireWire case? Each case has its own implications and potential error points, so it's not easy giving a definite answer quickly.

It's also necessary to know if the Windows or the Stand-Alone-Version of HDClone was used, since both use different drivers (the Windows Version uses Windows's own drivers).

Re: HDClone Hangs Up after 19 minutes

PostPosted: Tue Apr 07, 2009 9:58 pm
by Eddy
I have the same issue after 21% all I get is read errors and it slows way down. The current HD is 150 gb the new hd is 1 TB there are both SATA. Help me Alex!!

Re: HDClone Hangs Up after 19 minutes

PostPosted: Wed Apr 08, 2009 9:27 am
by Alex
Hm, I thought the problem was already solved in the previous version. It's definitely ATA-related, but using the new 3.7.4 (which is available from today on) you should be able to work better with it... if not, please report back here, so we know there's still an issue...