Turns out, the end is nigh.
For Newton users, the year 2010 poses a serious problem. It’s put simply by NewtonTalk’s tweet, but Marisa from the list says it like this:
The problem is that the Newton stores numbers as 30-bits instead of 32, and in 2010 the number of seconds since the “epoch” of 1901 or whatever date it is runs out of bits to keep track of the date.
Newton users have reported everything from date screw-ups to total crashes when they try to set their date to 2010 and get anything done.
Remember Y2K? This is Newt2K+10.
Avi Dressman developed a fix, which he describes in detail here, and you can find the package patch on UNNA (though Avi warns of the patch’s Alpha development stage – so be warned) [Update: Don't download Dressman's patch. It helped lead to the 2010Fix bug in January 2009].
Some who have tried setting their Newton to 2010 have had it crash everything from a MP110 (with OS 1.x) to the 2×00 series, but the bug mostly effects OS 2.x Newtons. So for gosh sakes, don’t try it at home.
But if you plan on using your Newt in 2010, by all means download the patch and prevent Newtpocalypse.
[Update 2: Eckhart Köppen, with help from the Newton community, developed a patch that fixes the 2010 bug. Use this instead of Dressman's patch.]