Bizarre Date/Time Stamp

[PKMills]

MasterCam crashed on me last September. I took this screenshot and saved it on my pc and forgot about it. I thought it was funny and figured I'd share it and see if anyone has any idea how I got this. The date is the day after my 2nd birthday, so I know I wasn't using MasterCam at the time.

 

[Guest]

Posted in the wrong forum

 

 

Moved to Industrial.....

[Thad]

Maybe you were using FBM. It's so easy a 2 year old can use it!

[billb]

Time in computers is often measured as the number of seconds from January 1, 1970.  Called Unix time. 

[Thad]

Time in computers is often measured as the number of seconds from January 1, 1970.  Called Unix time. 

 

...and the final calculation (converting Unix time to the correct, current time) was left out of the code?

[billb]

No.  I'll guess that the crash corrupted the file's internal time stamp.  If the internal time stamp is just an integer then "0" maps to January 1, 1970.  +500 maps to some time later that day.  +1457028668 maps to a few minutes ago (March 3, 2016).  I'll bet that the corrupted file time stamp was some negative number.  Then the final calculation (converting Unix time to the Day, Month, Year, Hour : Minute : Second format) came up with that time just before January 1, 1970 (the zero hour).  It went back in time!

[Matthew Hajicek - Singularity]

I bet it was zero but was adjusted for time zone.