[<<]Message[>>]    [<<]Author        [<<]Subject        [<<]Thread    

Number   :  10639
Date     :  2005-02-26
Author   :  David Mozer
Subject  :  Re: Xxclone: A newly introduced bug?
Size(KB) :  3



--- In xxcopy@yahoogroups.com, "Ray McCormick"  wrote:
> --- In xxcopy@yahoogroups.com, "jamesvmerrill" 
>  wrote: 
> 
> --- In xxcopy@yahoogroups.com, "Ray McCormick"
>  wrote:
> >> I normally run xxclone from a shortcut specifying:
> >> %windir%\system32\Xxclone.exe C: G: /backup2 /bc0 /start
> >>
> >> I have had no problems over many months, except for the lack of an
> >> unexpired copy of xxclone.
> >> Previously an expired version said that it was no longer valid and
> >> that was that.
> >>
> >> Now that is no longer the case.
> >>
> >> On double-clicking on the shortcut nothing happened.
> >> A right click followed by 'open' gave an empty window
> entitled 'xxclone'
> >> The command 'Xxclone' from the cmd shell gave a message box 'The
> designed life of this program has been expired'
> >>
> >> Downloaded the new version and unzipped it in a temporary folder. I
> couldn't guess at the new name so had to re-register [New version is
> 0_31_0, file name as before though previous version designated
> 0_31_0a].
> >>
> >> Attempted to copy xxclone.exe to its proper location (overwriting
> the old version) but found 'Cannot copy xxclone: There has been a
> sharing violation. The source or destination file may be in use'.
> >> Ended all tasks in Task Manager (nothing xxclone-ish)
> >> Repeated copy attempt with the same result.
> >>
> >> Attempted to reboot. Would not shut down. Had to reset - but there
> was no improper shutdown notice when booting.
> >> Subsequently the new file copied ok and xxclone did its thing.
> >>
> >> [When running in this way the Source Volume and Target Volume are
> blank (grey). I much prefer the previous system where, though greyed
> out the Source and Target volumes were indicated].
> >>
> >> I have W2kSP4/IE6SP1 with all updated in place
> >>
> >> Ray
> 
> >The explanation, I think, is that when the "expired" XXClone shows
> >the message, it does not exit -- it keeps running. A running copy of
> >XXClone won't allow Windows to shut down, because it thinks it's
> >doing something -- the fact that there was a /start made it think it
> >had begun the backup.
> >
> >You could have used any of a number of tools (e.g. Process Explorer
> >from www.sysinternals.com) to "shoot" the running XXClone process.
> >Then you would not have had to reset in order to copy and run the new
> >XXClone. 
> 
> 
> 
> {[I have been unable to sign in to Yahoo Groups (try later!) for a few days
> so I have sent this as an email - hope the formatting is ok, though the 
> link will no doubt be broken. Previous messages were 10628 and 10632]}.
> 
> The point that I was making was that this was the first time that I had seen
> this. Previously I just got a message that Xxclone had expired (or similar).
> 
> Also when Xxclone is running (normally) it appears in Windows Task 
> Manager - Applications. It was not there on this occasion. 
> Furthermore there should not need to be another companies utility 
> to get over a problem caused by Xxclone.
> 
> Perhaps Kan could give the definitive answer.
> 
> Ray
There is no need for another utility to get over the problem caused by Xxclone when it expired.

All you need to do to kill the XXCLONE process in Task manger is via the "Processes Tab" highlight XXCLONE and then mouse-click on "End Process" [near the bottom right-side of the Task Manager dialogue] which will invoke a warning dialogue to which you respond accordingly. That's what I did and it works just fine.



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.