I for one can't wait for the Year 2000, because I'm hoping to return to doing useful work. And I can take a well-deserved rest from this messy problem until 2100, which won't be a leap year. [Worried look] Uh-oh, that might be a problem.

[Brightening] Wait a second. I'll be dead by then!
Wait a second.  I'll be dead by then!  What a relief!

What a relief!

But let's not end on a note of doom and gloom. Let's all pat ourselves on the back. See? [Demonstrates] Kronos makes mission critical products, which do extensive calculations with dates. Yet the majority of our products pass when tested. Every Kronos-designed terminal we tested has passed, except for one hand-held. Versions of TKC going back to 6B.01 have been tested, and they all passed. As we considered older and older products, we stopped testing because we hit products that have been long obsolete, not because we hit products that didn't work. Our problem areas are largely with products made for us by third-party vendors. We're clearly doing better than most software developers, and that's something I think we can all be proud of.

Can I say there will be no problems in January of 2000? No, it's likely that something unexpected will go wrong; one thing we've learned about this problem is that it's full of surprises. But I hope to see all of you as part of an even larger and even more prosperous Kronos in the next millennium.

I'd like to give special thanks to my wife, Margie, who had a lousy Mother's Day while I was finishing up my speech and working on my visual aids. OK, Margie, I'm ready to autograph your body parts now. Thanks, everyone.

Click here to return to the Introduction