While interesting, I guess the 2/29/00 doesn't surprise me.  Consider that
the HP3000 doesn't know, on its own, to change to and from Daylight Savings
Time.  That doesn't bother me.  I would just as soon have ME worry about it
twice a year and not dedicate those extra few processing cycles every day to
check whether or the computer should change its time.

Just my $.325 worth.

Gary

-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]]
Sent: Tuesday, February 29, 2000 7:45 AM
To: [log in to unmask]
Subject: Re: Feb 29 Almost Half Over


Art hehehe's:

> hmmm... well.... At our house the Better Half and I have 9 watches that
> think it is 01 March and one watch that thinks it is 29 February!  Leave
> it to Nike (tm) to be the only watchmaker that got it right! hehehe

Art, unless your watch knows what year it is, Nike got it *wrong.* The
"75% solution," the one most watch makers use, is to roll from 2/28 to
3/1, since that's what happens 75% of the time. If your watch always rolls
to 2/29 it means 3 years out of 4 you'll have to manually set it to 3/1,
instead of only having to set it to 2/29 once every four years.

Of course, if your watch *does* know what year it is... that's "way cool."

My .02
Patrick
--
Patrick Santucci
Technical Services Analyst
Seabury & Smith, Inc.