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

Number   :  3209
Date     :  2002-12-07
Author   :  jgwirt2
Subject  :  Re: the elusive timestamp value of the NTFS directory
Size(KB) :  2


If I understand this issue from the two emails in this thread and 
FAAQs #15 and #17, XXCOPY normally compares the LastWrite date, which 
is stable and is not changed by XXCOPY in comparing a source with a 
destination file in order to determine whether it should be copied.

Not so? The compare can change the Source LastWrite date?

Suppose the Source and Destination files have the same names but 
different LastWRite dates. What does /DA do? If the source date is 
newer than the destination date doesn't XXCOPY copy the source file 
to the destination and date stamp the destination with the source 
Last Write date?

This all is very relevant to me because I am using XXCOPY with file 
management software called Xythos. The Xythos client can be used to 
map a local drive letter to a remote WebDav folder. Then XXCOPY can 
be used to transfer files directly between computers over the 
Internet. Also, the Xythos package includes a web interface for 
uploading and downloading files using your browser.

XXCOPY was working pretty well in this application but now I finding 
that the file dates reported by DIR on the source and destination 
directories do not always agree with what XXCOPY determines in 
comparing the dates. Today, a problem was that DIR reported files on 
the source (remote) and desitionation (local) directories as being 
dated 11/25/02, which is when they were created, while I know that 
the source file was last modified on 12/5/02. However, XXCOPY figured 
out that the source were newer than the destination files and coppied 
them! So DIR _apparently_ reported the file creation dates while 
XXCOPY used the File Modified dates.

My question is whether this is a Xythos problem or maybe an XXCOPY 
problem. I think it is probably a Xythos problem, because Xythos has 
a complicated file versioning scheme built into it that could be the 
source of the problem. I do not understand this versioning system 
very well yet.

So might there be a problem with XXCOPY here or is it more likely a 
Xythos problem.

PS Xythos is a product that XXCOPY should know about 
(www.xythos.com). Xythos recently purchased (or something) the 
TeamDrive product.

John Wirt



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