David Van Horn wrote:

> The only thing more irritating than a bad solution is a bad solution
> to a non-problem.

  Ah, but is is solving *some* people's problem; that of income between
now and the year 2000, isn't it?

Martin Green wrote:

> In short, to test your PC, set your clock to a few minutes before
> midnight, December 31, 1999, then shut off your PC.  Wait a few
> minutes, until the clock should be well into January 1, 2000 and run
> your PC back on.

  ... etc.  I'm not sure what the point is here.  Whether or not the
thing rolls over neatly into the new century is of no consequence
whatever.  It won't take a lot of time to go around setting computer
clocks on the morning if the 1st January, 2000 (whichever day of the
week it happens to be.  Which is it anyway?)  What *is* meaningful is
whether that date can be entered at all, and whether it will roll over
correctly the *next* night and every other one after that.

  And yes, whether WIN99 OSR6 handles it OK, and whether your apps were
written by a smart-ar*e shyster or a competent programmer.  I have
written all my stuff Y2K compliant since the early 1980s (i.e., when I
first had real-time clocks and/ or disks!) because I didn't think there
was any other way to do it.  Also of course, as it was my *own* stuff,
now that's telling, isn't it?

  Cheers,
        Paul B.