Opened on Jul 28, 2011 at 1:49:23 PM
Closed on Aug 3, 2011 at 8:31:25 AM
Last modified on Aug 9, 2011 at 1:37:18 PM
#1986 closed Bug (Works For Me)
FileSetTime() sets wrong the TIMESTAMP when Windows 7 x64
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.6.1 | Severity: | None |
| Keywords: | FileSetTime(), TIMESTAMP, Cross Platform compatibility | Cc: |
Description
When it's used on Windows 7 x64 ( With or without the x64 autoit tools) the TIMESTAMP of "created file time" is added by 1 hour. So, when I throw the command:
FileSetTime($userFile,"20051225100000",1)
I got the same result when I was using this command on XP x86:
FileSetTime($userFile,"20051225000000",1)
I've used the same script on both systems.
After that happened, I've installed the BETA version but the same issue was showed...
Attachments (0)
Change History (4)
comment:2 by , on Jul 30, 2011 at 1:56:56 PM
is the "daylight saving time" the same for both system?
comment:3 by , on Aug 3, 2011 at 8:31:25 AM
| Resolution: | → Works For Me |
|---|---|
| Status: | new → closed |
The following script works correctly for me:
Local Const $sFile = @ScriptDir & "\FileSetTimeTest.txt"
Local Const $sExpectedTime = "20051225100000"
FileWrite($sFile, "Data")
Local Const $sTime1 = FileGetTime($sFile, 1, 1)
FileSetTime($sFile,$sExpectedTime,1)
Local Const $sTime2 = FileGetTime($sFile, 1, 1)
MsgBox(4096, "", StringFormat("Before:\t%s\r\nAfter:\t%s\r\nExpected:\t%s", $sTime1, $sTime2, $sExpectedTime))
FileDelete($sFile)
comment:4 by , on Aug 9, 2011 at 1:37:18 PM
Yeah, I still don't know what happened. But the problem happens yet. When I've time to solve it out I'll post the solution here. Thank you so far.

I'm sorry, the right command to equals the XP version is:
(((
FileSetTime($userFile,"20051225230000",1)
)))
Both systems have -3 GMT timezone setting.