> > > Before watching that box of bytes ride slumped over into the sunset, try changing the year to
> > > 1973 instead of 1999. The days in 1974 are the same as 2000 and your 'puter won't know the diff.
> >
> > I personally don't think that's a very good fix. Sure, the weekdays and the date will match, but I think having the computer know what year it is is more important. This may be too picky for most home users, but there are computers out there that *need* to know what year it is.
> >
> > (I read in the paper yesterday that there's been a new wave of Y2k problems caused by lazy bug fixes that result in computers not recognising the year 1900.)
> >
> (snip)
> >
> > Pa"Y2k, incidentally; Y2K is 2048"ul
>
> I realize that setting back the year is, of course, not the most preferable solution by a longshot. I just thought I'd offer an alternative to letting it commit technicide on its own, as it did sound as if she had already resolved herself to that eventuality. Lord knows it could wreak havoc on trying to keep your check book in order (i.e.: MS Money, Quicken), but I may be better than not having one at all.
>
> I understand that a computer would *need* to know the year, but how would it know if you lied to it?
You could just claim, with the checks, that you kept forgetting to switch over the dates when the new year changed... ever, for over 20 years. But considering I dated a paper with 1997 only recently, hey, it could happen.
Fob"who, me, scattered? BTW, I'm back, and maybe my messages won't truncate from a Lynx browser"ulis