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

Number   :  3484
Date     :  2003-01-08
Author   :  Kan Yabumoto
Subject  :  Re: xxcopy hangs up on a file
Size(KB) :  1



My bold guess is that you have a huge swap file (it is usually
very large), it is simply taking a very long time.
I believe it is worth waiting for a long time.
But, the best way is to exclude the swap file using the /X switch
because copying the swap file is waste of time. Then, why
doesn't XXCOPY automatically exclude the file in the first place?
The answer is that if you know what is the swap file, you can
explicitly exclude it. It is not very straightforward for XXCOPY
to know what is the current swap file setting is and where it is
stored. Although in most cases, people don't change the name
of the default swap file but it could be changed to any other
name and anywhere you want. So, even though it may sound
reasonable to skip the file, it has an adverse consequence.

Just as an example, if the regular COPY command refuses to copy a
file simply because the name is WIN386.SWP even though it is
not actually the current swap file, then, that is not right.
The copy command should not make such an automatic (and potentially
erroneous) exclusion. The copy command should faithfully
try to execute what it is told to do.

Anyway, the typical exclusion syntax is

xxcopy c:\ x:\ /clone /xc:\win386.swp

Usually it is the largest file and you may use the size limit
as the exclusion mechanism:

xxcopy c:\ x:\ /clone /sz:-500M // exclude files larger than 500MB

Kan Yabumoto
===============================================================
At 2003-01-07 22:48, you wrote:
>I have the freeware. In trying to xxcopy my drive c to a usb hard
>drive the operation stops at windows/swap. It does not resume. Does
>anyone have a sugtgestion.
>
>John



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