FileSetTime() Bug?

[Mechaflash]

Using FIleSetTime() to update the Date Modified tag on a copied file. I noticed that while it's updating the Modified time, it also updates the Created time.

$sFile = @DesktopDir & "FileSetTime Testtest.txt"
$hFile = FileOpen($sFile, 9)
FileWrite($hFile, "Test")
FileCLose($hFile)
FileSetTime($sFile, "20120101123456", 0)
msgbox(16 + 262144,@ScriptName, "Check the file properties.")
FileSetTime($sFile, "20120622245612", 0)
msgbox(16 + 262144, @ScriptName, "Check it again...")

EDIT: Looking at the bug tracker... I suppose I should note that the files sit on a NAS (linux)...

Tested my above code and it seems to work fine, so I suppose the NAS is the problem.

Edited June 22, 2012 by mechaflash213

[JLogan3o13]

What happens if you omit the third param, and just let it use default instead of specifying the 0?

Edited June 22, 2012 by JLogan3o13

[Mechaflash]

@JLogan, I just discovered that my above code actually works, but when targeting files on my NAS via mounted network drive, it happens =/

[JLogan3o13]

Glad you worked it out

[Mechaflash]

I just remembered... Linux doesn't save a "Created" timestamp for files in its file system. So by the looks of it... it's adopting the Modified timestamp, and placing it into the Created timestamp.