This is just purely out of curiosity... but why, when I copy a package out to a DP and it's at an install pending state, does it have the year under "Last Copied" as 1970? I've been told that it was an awesome year, what with all the cool cars, music and kicking hairstyles... but surely there's another reason? It also appears that the month is always the same as the current and the day is always a couple of days into the future. Like today is 4/2/2010 at 2:20pm and "last copied" date shows (for all the DPs who didn't have the package previously) as 4/10/1970 at 6:35am. This presents no issues... merely something I wondered about has I clicked refresh. It could be too that my mind is in Friday afternoon wander mode. :)

The standard for storing time in most modern OSes is the number of milliseconds since 0:00 Jan 1, 1970. Those times are probably some default, round number of milliseconds that the data structure under the covers is getting initialized to. One interesting thing to note is that given a 32-bit architecture, this value (the number of milliseconds since 0:00 Jan 1, 1970) will actually wrap in something 2023 giving us another Y2K like issue (at least on 32-bit systems).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Well thanks for humoring me with that info!