Example:
Dec: 3596946
Hex: 36e292
Good example can be found if using Internet Explorer 9 with a tpl file:
"HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Safety\PrivacIE\Lists\" & UNIQUE KEY & "\LastUpdateTime"
"HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Safety\PrivacIE\Lists\" & UNIQUE KEY & "\LastUpdateTime"
Strange.SYSTEM wrote:It doesn't seem to be any of the date formats supported by http://www.silisoftware.com/tools/date.php. When I set it to interpret the number as FILETIME, it returned a sensible date (April 22, 2009), but other fields had very odd values (e.g. Microsoft timestamp -109205), so I think the number is not FILETIME either.
Thanks. I continued your analysis: 3 614 804 hours is approximately 412 years and 136 days. That means that the base year is either 1600 or 1601. I think bugmenot2's opinion at http://www.autoitscript.com/forum/topic ... ?p=1025857 is right...I am Baas wrote:Hex 372854 = Dec 3614804
Hex 36e292 = Dec 3596946
Subtraction of the Hex / Dec numbers gives:
Hex 45c2 = Dec 17858
This, I believe, represents the number of hours passed between those 2 dates
17858 hours = 744 days and 2 hours
Remember this post?
Still trying to figure out the base year for the hex time stamps in the registry.
Course I do, I thought it was weird (scary) that 2 years had already passed. In hindsight I should have referenced this link.I am Baas wrote:Remember this post?
What? Subtraction was exactly the right way to solve the date format. It told us that the counter had advanced 17 858 units in a bit over two years, i.e. that the unit is one hour.guinness wrote:Edit: Actually those two dates are just examples and shouldn't be subtracted. The first value I provided was from 2 years ago, so I decided to provide a more up to date example.