GW> IM> Aw man! This really bites! I set my RTC to 2080 and OS/2 thought
GW> IM> that it was 1980! What an abortion! So what am I supposed to do
GW> IM> in 2080 -- go back to DOS? Yahoo. Don't throw out those copies
GW> IM> of Himem.Sys and Mscdex, folks -- what's old will be new again!
GW>
GW> DOS will only get you 20 more years. It breaks in 2100 :-( Anyway,
GW> how many of us are likely to care in 80 years time?

I don't know about you, but I intend to be sending E-Mail to my great-
great-great grandkids over the Galactinet with my super-conducting 
berylium parallel processing clone from my summer home on Mars. [:)

And no, I'm not kidding! [;)


GW> IM> I'm not even going to say any more about it because this
GW> IM> _really_ ticks me off.
GW>
GW> I expect OS/2 to be totally obsolete long before then,

Isn't that the kind of thinking that got us into this Y2K corner in the 
first place? [;) OS/2 users  Windows users.


GW> According to tests run by some of the other echo users the 2079
GW> thing is *NOT* a problem with OS/2 itself (by that I mean the base
GW> OS resident in memory) but with the support utilities provided with
GW> it.

Well, that distinction may mean something to somebody but like I said, I 
set my RTC to 2080 and OS/2 came up thinking that it was 1980. To my way 
of thinking, if there were nothing wrong with the base operating system 
then there would be no need for date windowing in the first place. It 
seems pretty obvious to me that while OS/2 won't have a problem in the 
year 2000, this is only due to a kludge and OS/2 has a date problem.


GW> If you've seen JdeBPs postings you'll have noted that the 32 bit
GW> OS/2 API returns time as a _64_ bit second count, which lasts for
GW> centuries rather than years.

Yep, saw 'em. That makes little difference when the O/S is going to 
commit harikare on 01 January 2080. That makes about as much sense to me 
as those clowns who use a _signed_ integer to store hard-drive 
capacity.


GW> Anyway, let's face it, compared with the problem of C time _ending_
GW> for most compilers & current versions of *NIX in 2038 it's a _much_
GW> longer time span (100 years as against the 68 of C & *NIX).

Well, yeah, but sounds suspiciously like saying, "we're not quite as bad 
as everyone else". [:) One of the reasons I don't use C.

Anyway, question answered. Thanks a lot, George, I really appreciate it. 
Take care and TTYL.

---
 þþ Vegetarianism:  Just another excuse to be picky with food.                 
       

--- AdeptXBBS v1.11y (FREEWare/2)