Win 64bit Hex BE 01C7E15F31D202FF Invalid
Win 64bit Hex LE FF03D2315FE1C701 Invalid
#PROPEDIT MAC CODE#
Here's a summary of the results for all the TimeDate formats included in DCode (presented as code so I could get the columns to line up, and including my own local time in addition to UTC, which I hope doesn't confuse things):Ĭode: Select all PropEdit.exe (708992537)įormat DCodeExample Modified Thu, 20.57.42pm UTC The PropEdit.exe PE Header TimeDate stamp as revealed in Property Edit (708992537) probably most resembles a Unix Epoch format, but that format converts to Fri, 22.22.17 UTC, which makes no sense, nor do any of the other conversions I've attempted.
#PROPEDIT MAC ZIP FILE#
More specifically, the PropEdit.exe Modified TimeDate stamp inside the ZIP file downloaded from your site is the file is Thu, 01.57.42pm PDT (local time) on my system or Thu, 20.57.42pm UTC (not, BTW, as indicated on your webpage ). However, as I was looking at this, I happened to use Property Edit to look at the Property Edit v2.5.0.0 executable itself (PropEdit.exe, md5=c53c32d441799600d516bca9e2e95ea6, sha1=1fa0e81c8237e9095f83f595d1772a440a10f8f4) and found a TimeDate stamp of 708992537, which as near as I can figure doesn't correspond to any TimeDate stamp format included with DCode, or any other I can discover. Recently, for example, I used both Property Edit and DCode to clarify the version, or at least the compilation TimeDate, of another developer's updated executable that still showed the same internal versioning information as the previous version. I've also been playing around with Digital Detective's DCode v4.02a (Nov 2, 2009) to check various TimeDate stamps. I noticed that Property Edit will reveal a PE Header TimeDate stamp which, if I understand correctly, usually represents when the executable was compiled. I've been trying to learn a bit about various programming and computer forensic issues, and in particular have been looking at various date formats/encodings. I've even started a small list of questions and suggestions re HxD (and maybe re Property Edit) that I hope to post at some point, but that file is on another computer which is down right now with a failed motherboard. I'm not a programmer, but just a self-taught computer hardware/software hobbyist, and I've enjoyed trying out your HxD Hex Editor and your Property Edit program. I hope you won't mind my posting a non-HxD question here.
0 kommentar(er)
