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

Number   :  3256
Date     :  2002-12-12
Author   :  Kan Yabumoto
Subject  :  Re: Files keep getting copied when they should not be
Size(KB) :  1



Chaz:

I'm just curious on one little thing:

You repeatedly showed the switch /FF3 which adds the fuzzy filetime
matching range of plus/minus 3 seconds.

My question is did you choose this setting because the default
value of /FF (which is equivalent to /FF2) had some problem
which /FF3 solved in a real world situation?

Or is it your intuition to play safe using a slightly more
forgiving value (but not exceedingly loose) on the occasion?

I'm just curious about this point. That's because with the
experiments that I ran, I always found /FF2 to be sufficient
to eliminate a filesystem mismatch. What I was (and still am)
not sure is whether /FF2 is always sufficient, or
there is a real case where /FF2 does not work but /FF3 does.

If your answer is no (not soure) but you chose /FF3 to be
"safe", I still wonder if anyone else had cases where /FF3
really made the difference.

I'm curious but it's hard for me to know which is the truth.

Kan Yabumoto
============================================================

At 2002-12-12 00:25, you wrote:
>You didn't say if both machines are the same version of Windows and/or
>running the same file structure (FAT/FAT32/NTFS).
>
>If there is a dissimilarity of file systems that could cause you pain.
>
>Why not use this form:
>
>xxcopy "f:\Palm\KjellbT\" "R:\Palm\KjellbT\" /clone /ff3 /yy /OA"BackupLog.
>txt"
>
>That's what I use for the same purpose when one of my machines is running
>XP Pro/NTFS and the other Win98SE/FAT32
>
>Chaz



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