> The big question is..... Can you fix this in time????
> After-all, we have less than 38 years before the Y2038_BUG hits us.<vbg>
This is a known problem with C which I discovered when researching the
Y2K bug. The variable in C used to track the time (think it is the number
of seconds elapsed since 1st Jan 1970) will roll over to 0 in 2038
(which the software of course thinks is 1st Jan 1970)
So a lot of software written in C (which includes Linux or Eudora
(see Eudora's Y2K page) ) will have this problem which
includes Insight since it is written in Borland C.
>
Is this why Arachne behaves OK when the date is set back 6 years, to 1994, but
goes bananas when the year is 2094?
I suppose, as the computer world approaches 2038, 32-bit processors will be long
gone. 64-bit processors will replace 32-bit processors, and likely a few more
upgrades within 38 years. Maybe 64-bit processors will be ancient history by
then?
Support the International Alliance for Compatible Technology
http://pages.cthome.net/iact/
