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

Number   :  5204
Date     :  2003-08-03
Author   :  Kan Yabumoto
Subject  :  Re: Error: "Warning: Failed timestamp"
Size(KB) :  3



Garry wrote:

>NTFS/XP maintains modifiable timestamp properties for directories
>(created, modified, accessed) whereas (I think) FAT32/W98 only
>maintains a non-modifiable directory timestamp in which the
>modified time is set to the creation time. By default, Xxcopy
>tries to set the date stamps for the destination directories
>as follows:

The timestamp behaviors of NTFS/FAT and Win9x/XP are very
confusing one. I have made mistakes a few times when I explained
this topic here and there.

Here's my understanding.

1. with the FAT volume, the timestamp granularity is 2 seconds,
regardless of what Windows version you use.

2. Using WinNT/2K/XP, you can set the timestamp of the
directories. Therefore, using XXCOPY, when you copy
directories, the timestamps can be modified on directories
even in a FAT volume.

-------------------------------------------------------
This gives an interesting opportunity. If you really
need to logically copy one volume to another which is
used in a Win9X system including the directory time,
you may temporarily connect the disk to an XP machine
and make a full duplicate using XXCOPY. In that case,
you can reproduce the directory timestamps exactly
as they appear in the source volume. The only problem
with this is that the SFN-synthesis algorithm in a
crowded directories (such as the cookies directory),
Win2000/XP OSes create different SFNs (beyond 4th
SFN with the same beginning (see XXTB #
-------------------------------------------------------

3. In the case of NTFS, the case is simpler. That's because
Win9X cannot access NTFS volume (except you can write to
an NTFS volume of remote computers via LAN even from a
Win9X system). For a local NTFS volume (accessed by
NT/2K/XP), you can change directory timestamps and
they are stored in the fine granularity (100 nsec).

Kan Yabumoto














>Create time=current
>Modified time=same as source
>Accessed time=current
>
>It is the attempt to set the modified timestamp to other than
>the current time which generates the warning. If the warning
>bothers you, you can add /TCW0 (the last is zero) to eliminate
>it. This switch sets the modifed time to the current time (which
>it will do on FAT32 directories regardless) but note that it will
>also set the timestamps for all the files to the current time
>which you almost certainly don't want.
>
>If you really wanted, you could carry out the clone in 2 steps.
>
>:: Clone the directory structure supressing the warning
>C:\xxcopy C:\Data\ N:\PCBackups\Data\ /clone/t/tcw0/pz0
>:: Clone the files
>C:\xxcopy C:\Data\ N:\PCBackups\Data\ /clone/pz0
>
> > Subsequent uses of the command didn't have the error, but some
> > of the files (not all) are getting copied although they haven't
> > been changed.
>
>Again this is because you are copying between different file
>systems which maintain slightly different precision for the
>timestamps. Add /FF to give a 2 second leeway on matching the
>timestamps
>
> > I tried creating the files & folders on the destination drive
> > by copying within Windows Explorer first, but it made no
> > difference. I also experimented by copying the source folder
> > to a FAT32 partition on my new PC before issuing the XXCOPY
> > command -- no luck there.
>
>Same issue but in reverse. /FF will fix it.
>
>Garry
>
>
>
>
>---------------------------------------------------------------
>To unsubscribe eMail to: 
>Or to post a message, send eMail to 
>---------------------------------------------------------------
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



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