FileSetTime issue

[orbs]

i stumbles upon a bizarre behavior of FileSetTime. in brief, the issue is that after setting the time for a file, it is reported differently in DOS command prompt and in Windows Explorer. DOS reports the correct time, and so does FileGetTime; but Windows Explorer reports incorrect time - 1 hour earlier (i'm currently on time zone GMT+2, with DST of +1 hour).

 consider this very simple reproducer:

#AutoIt3Wrapper_Au3Check_Parameters=-q -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7

Global $sFile='C:\TEMP\file1.txt'
ConsoleWrite(@CRLF)
ConsoleWrite('>this is just making sure the file was created successfully:' & @CRLF)
Global $hFile=FileOpen($sFile,2+8)
ConsoleWrite('FileOpen = '&$hFile & @CRLF)
ConsoleWrite('FileWrite = '&FileWrite($hFile,'this is some text') & @CRLF)
ConsoleWrite('FileClose = '&FileClose($hFile) & @CRLF)
ConsoleWrite('FileGetSize = '&FileGetSize($sFile) & @CRLF)
ConsoleWrite('>set and verify the file time:' & @CRLF)
ConsoleWrite('FileSetTime = '&FileSetTime($sFile,'20011231010203') & @CRLF)
ConsoleWrite('FileGetTime = '&FileGetTime($sFile,0,1) & @CRLF)
ConsoleWrite('! now go and check the file time in Windows Explorer and in DOS command prompt.' & @CRLF)
ConsoleWrite(@CRLF)

SciTE output: (correct)

DOS dir output (correct, although not showing seconds):

Windows Explorer file properties dialog (incorrect - should be 01:02:03 instead of 00:02:03):

i checked all 3 timestamps (Created/Modified/Accessed) - same issue.

checked various past times, with and without DST, also future times - same issue.

using Windows 7 x64 + AutoIt 3.3.14.2. also tested on Windows XP + AutoIt v3,3.8.1 and did not observe the issue there (both systems are properly configured with time zone and DST).

AutoIt full change log does not mention FileSetTime recently.

to be honest, i do not think it is AutoIt to blame; most likely it's a bad combination of Windows and my time zone and DST. but if anyone can make any sense of it, it's probably the AutoIt community... 

Edited September 23, 2015 by orbs

[JohnOne]

Looks like it's the command prompt reporting it wrong.

 

Edited September 23, 2015 by JohnOne

[BrewManNH]

Windows Explorer uses UTC times for NTFS file systems and then takes into account your time zone settings. On my computer the console window shows one file with the correct date, but one hour off than the Windows Explorer show. One shows 11:04 am, the other 10:04 am.  This is because when it was created (November) the DST setting wasn't in effect, but currently it is. I also have a file that was created in September that has the same time values, because they were both created in the same time zone setting, next month when DST ends I'm sure that this file will have a different time stamp in Windows Explorer again.

This has nothing to do with AutoIt it is just an idiosyncrasy in Windows.