Hello, We are seeing time problems caused by the AFS NT client again since we have gone into Daylight Savings Time. It appears to be that copying a file from an AFS replication RO volume to the local NTFS volume shows file times to be off by 1 hour. We saw this last year also. We are currently running AFS Patch level 6. Its funny because copying the file from the replicated RW volume sets the time correctly. This is causing quite a bit of annoyance since we keep our machines updated by determining file changes using last write times. To see this in action simply copy a file using the command shell copy command, or explorer, to "c:\", then check the times on the files. Has anyone else seen this problem? Are any fixes in the works? Note: I also do quite a bit of NT development work and I noticed that the GetFileTime API call, which by the way returns a 64 bit number, is also off by 1 hour. The standard C 'stat' call returns the correct number. Help is appreciated... Thanks, Rodney Rodney M. Dyer Systems Programmer II Project Mosaic NT Network Group College of Engineering University of North Carolina at Charlotte Email: [EMAIL PROTECTED] Phone: (704)547-3518 Help Desk Line: (704)547-3150 Office: 267 Smith Building
