[Tinymux] Build problem - Visual Studio 2005 AMD64

[Stephen Dennis]

There were two issues: One issue was a bug in MUX in that is depended
upon an order of global initialization which could not be guaranteed.
The only downside to the bug (if it occured during compilation) was
perhaps that the log started with the wrong time.

The second issue is specific to the VS 2005 compiler and the VS 2005 C
Run-Time Library. A summary of the issue is in the comments:

+    // Not only can Windows not handle negative time_t values, but it also
+    // cannot handle positive 64-bit values which are 'too large'.  Even
+    // though the interface to localtime() provides for a NULL return value
+    // for any unsupported arguments, with VS 2005, Microsoft has decided that
+    // an assert is more useful.
+    //
+    // The logic of their assert is based on private #defines which are not
+    // available to applications. Also, the values have changed from VS 2003
+    // (0x100000000000i64) to VS 2005 (32535215999). The latter corresponds to
+    // December 31, 2999, 23:59:59 UTC.
+    //
+    // The message here is that they really don't think anyone should be using
+    // localtime(), but if you do use it, they get to decide unilaterally and
+    // without hints whether your application is making reasonable calls.
+    //

The fixes for both issues have been checked into CVS.

Stephen