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

Number   :  5198
Date     :  2003-08-03
Author   :  Garry Deane
Subject  :  Re: Error: "Warning: Failed timestamp"
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "galoot53"  wrote:
> I'm trying to backup select folders/files from the hard drive
> my new PC to the hard drive on my old PC (networked).
> 
> SOURCE PC: Windows XP (NTFS C:)
> DESTINATION PC: Windows 98 SE (FAT32 mapped as N:)
> 
> The first time I ran the command below...
> 
> C:\xxcopy C:\Data N:\PCBackups\Data /s /clone /yy

You should get into the habit of specifying directory paths in
the above command with a trailing "\" to avoid any potential
ambiguity about whether you are referring to a file or a
directory. Also, there is no need for the "/s" as this is
included in the "/clone" settings e.g.

C:\xxcopy C:\Data\ N:\PCBackups\Data\ /clone /yy

> ...I got the error "Warning: Failed timestamp" when each 
> folder/subfolder was created on the destination drive. However
> the bottom line said "Exit code = 0 (No error, Successful
> operation)" and all files/folders seemed to have copied okay.

This is just a warning which you can safely ignore. The reason
for the warning is that you're copying between NTFS and FAT32.
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:

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



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