[Harold Estrada]

I sent a support inquiry on this issue but it is taken a while to get a response so I am hoping I can get an answer sooner from this forum.

I had already cloned my drive to nother drive and now I would like to image that cloned drive to a new drive but the software hungs up when I select the Drive to Image.

What I am trying to do is to sort of backup my master drive to another drive withing the same system using the Drive to Image option available in the professional edition but it hungs up in the drive recognition message.

Any help would be appreciated,

Thanks

Harold

[Alex]

Does this mean it hangs up on the message: "Detecting Devices" or later when you select the drive to write the image to?

And what version of HDClone are you using (and are you using the Self-Booting Edition or the Windows version, which should not hang)

[Harold]

After I select the Drive to Image and click on "Next" it hangs up on the message "Drive Recognition, HDClone is scanning for connected drives. One moment please..."

I am using the Windows version, and it HANG UP.

[Alex]

Ok, here's what I don't understand: Using the same HDClone, but selecting something different than Disk->Image, you could use HDClone and create a Disk->Disk clone? Or did you do this in the self-booting edition, or in another (older) Windows-Version?

If you run the Windows Version and the application seems to be blocked, try the following: press Ctrl+Alt+F8 to open a shell window within HDClone.

In this shell Window, enter 'procinfo' (without the quotes).
It should read something like this:
[pre]
/emb>procinfo
ID V T Runti Name
65541 0 1 0.07 procinfo.exe
65542 0 7 9.25 shell.exe
65543 0 5 10.92 hdclone.exe
65544 0 1 10.92 svc.sysint.srv
....
[/pre]


It could also read like this:
[pre]
/emb>procinfo
ID V T E Runti Name
65541 0 1 0.07 procinfo.exe
65542 0 7 9.25 shell.exe
65543 0 5 1 10.92 hdclone.exe
65544 0 1 10.92 svc.sysint.srv
....
[/pre]

This means that there's an exception in hdclone.exe, during the recognization phase. In this case, more info about the Windows Version you use (XP, Vista, ...) is needed. Perhaps the support can you provide with a more verbose version of HDClone that prints what is causing the exception.


Oh, and btw: if you enter 'halt' (again without the quotes) on the command line, you can terminate HDClone even if it is blocked.

[Harold]

I don't think it is being blocked by the OS because I have already used to clone the drive for the first time. I cloned the master drive Disk to Disk. The Os is Windows 2003 server and I did not have any problems in cloning the master drive, so now all I want to do is to image that same drive, but it hangs up?

Also, I am not running this app from the command line, all I am doing is runnig it from windows explorer. I click on the app and it runs fine it only hangs up when I try to image the master drive.

I will try your commands to see if I can unluck it when it hangs.

I have sent this same inquire to support and I am still waiting.

[Harold]

Here are the results of the command you asked me to do. They're a little bit different than what you gave me.

/emb>procinfo
ID V T E Runtime Name
65541 0 1 0.09 procinfo.exe
65542 0 7 1:26.42 shell.exe
65543 0 5 1:36.96 hdclone.exe
65544 0 1 1:36.96 svc.sysint.srv
65545 0 7 1 1:36.96 svc.w32blockdev.srv
65546 0 2 1:36.98 svc.root.srv
....
11 processes, 37 threads
/emb>

And by the way, the halt did work fine. I was able to close the app.

Thanks

[Alex]

In the past, exceptions on the svc.w32blockdev.srv happened only on special defective devices. Here a sys info of your installation would help.

To create such a info, connect all drives as you would for doing the clone, then execute from the command line msinfo32.exe
Within this program, under File > export you can create a complete list of all attached devices, and hopefully we're able to find some indication why a special device is not recognized.