40Hz

Patch 71J059

2010-07-16T18:43:35Z

Note: This patch has been replaced by the newer Patch 711000!

This is the native system level patch version 71J059 for the US MessagePad 2000/2100. The patch contains a fix for the Newton's 2010 problem, as well as the contents of the original 717260 patch.

Version: 71J059
Download via SourceForge

Patch Credits

2010-07-16T18:41:01Z

Credits

Thanks to Jonathan Kipling Knight for the disassembly of patch 717260 which is the basis for all other patches.

Thanks to Paul Guyot for fixing the reset to 2008 problem.

Thanks to the following people for testing:

Tony Kan
Don Zahniser
Ronnie Simon
William Ponciengel
Sonny Hung
Rhonda
Greg Goodwin
Stefan Hassenstein
Grant Hutchinson
Christian Kwoll
William Ove
Jan Stoltenhoff
Hans Lefeber
Andy Hill
Woody Smith

Newton Year 2010 Solution

2010-07-16T18:36:34Z

Patch

The Y2010 problem is fixed with the Patch 711000, Patch 73J186 and Patch 74J185.

Solution Outline

Solving the Newton Year 2010 Problem is achieved by applying these fixes:

Changing the time base for seconds based C++ functions
Changing the time base for NewtonScript functions
Replacing old C++ functions with new functions via a NewtonOS patch
Replacing old NewtonScript functions with new functions at startup via a NewtonOS patch
Ajdusting the time to fall always into a safe range
Fixing the entries in the system alarm soup
Putting safeguards in place to allow installation only on the matching OS version

Completed Steps

Patched C++ functions
- FDateFromSeconds
- FSetSysAlarm
- FTimeInSeconds
Patched NewtonScript functions
- TimeInSecondsToTime
- TimeToTimeInSeconds
Registering NewtonScript functions in InitScriptGlobals
Time adjustment in InitScriptGlobals
Installation safeguard
Patches for MP2100D and eMate

Newton Year 2010 Problem

2010-07-16T18:36:06Z

The NewtonOS has a bug in handling years past 18:48:31 on January 5, 2010. The bug is located in the NewtonScript interface of certain time functions, and it is caused by an overflow of a NewtonScript integer value. This bug seems to only occur in NewtonOS 2.1 devices.

In case of problems, the Y2010 Diagnostic application can be used for initial first aid

Symptoms

The overflow of the timer causes alarms to go off in an endless loop. Alarms can be shown for example for calendar events, to do items or birthdays. The alarm notification can be dismissed, but will reappear immediately because due to the overflow, the time for the alarm is in the past.

Solution

A solution has now been released as a set of patches for the different NewtonOS 2.1 devices:

Patch 711000: Patch for the US MessagePad 2000/2100
Patch 73J186: Patch for the eMate 300
Patch 74J185: Patch for the German MessagePad 2100

The Newton Clock

On 2.1 devices, the Newton has one high resolution realtime clock. The interface to the RTC is the TURealTimeAlarm class in LongTime.h. Time values are stored in obbjects of the TTime class. The RTC can handle very large time spans, but most of the functions use unsigned 32 bit integers as seconds from January 1st 1904.

Classes and Functions

C++

The more common C++ funtions are the RealClock and RealClockSeconds functions for reading the RTC, and SetRealClock and SetRealClockSeconds functions for setting the RTC. The base for these functions is always January 1st 1904, and the resolution is either minutes or seconds. The use of an unsigned 32 bit integer creates an overflow problem in the year 2040. In general, all C++ functions can be considered safe and problem free until 2040.

NewtonScript

The NewtonScript functions are all based on the RTC, there is no separate clock maintained for the NewtonScript layer. They are based on the RealClock functions described above, and work with a minute or second resolution.

The Time function works with a time base of January 1st 1904. The TimeInSeconds function, and all functions using seconds as the resolution use a time base of January 1st 1993.

The Bug

The overflow happens in all NewtonScript functions which use seconds as the resolution. In contrast to the 32 bit unsigned integer used by the C++ functions, NewtonScript integers are only 30 bit wide. While the C++ functions can handle times from 1904 until 2040 without an overflow, the NewtonScript functions had to be designed with a smaller range of applicable times due to the limited precision.

The seconds-based functions are implemented by taking the value of the real-time clock, subtracting the offset to January 1st 1993, and converting the results to a NewtonScript integer. This limited range causes an overflow on Tuesday, January 5, 2010 at 6:48:31 PM.

This is the list of affected functions:

SetSysAlarm
TimeInSeconds
TimeToTimeInSeconds
TimeInSecondsToTime

Fix Possibilities

Rebasing the Minute based Time Functions

The problem of an overflow in the seconds based functions is caused by the system time advancing past the overflow time. By ensuring that the system time stays within the safe interval, the overflow can be avoided. This fix was implemented by Avi Drissman in the Fix2010 package. The Fix2010 uses the concept of a hexade (16 years) and adjusts all functions which use minutes as a time base to always fall into the safe interval, taking the offset for the hexade into account.

Rebasing the Seconds based Time Functions

A more low level approach is to change the offset used by the seconds based functions so that the safe interval starts and ends later.

Considerations

There are some pitfalls to consider for any fix. The parts of the NewtonOS which are not patched might activate before the patch goes into effect (e.g. when rebooting or after a cold boot), and some data might carry wrong values. So far, these issues are open:

State of the clock after loss of time: The clock resets to 1996 in this case, and this value might conflict with the patched functions
Alarms in the alarm soup: Alarm times can be wrong if the alarm was entered without the patch
Hardcoded assumptions about the time bases: Programs assuming that the seconds-based functions always start in 1993 might stop working

40Hz

2010-07-16T18:35:51Z

Newton

Software

This is a list of Newton software available on this site:

Internet

Courier: Web browser and RSS reader
NHttpLib: Newton HTTP library
Raissa: RSS news and headline reader

Connectivity

Blunt: Bluetooth protocol stack
Blunt 2: Enhanced Bluetooth protocol stack
Nitro: IrCOMM Communications Protocol
Neo: OBEX data exchange over IrDA and TCP/IP
IC/VC: iCalendar and vCard import/export, package installer
RDCL: Desktop connectivity library written in Ruby

Utilities

ntox: Newton version of the tox XML parser
The Fish: Encryption utility for the Notes application
Soup Mover: Enable better filing for Soup entries
Small Extras: Popup menu for the Extras Drawer
Minibar: Compact button bar replacement

Patches

Patches for the Newton Year 2010 Problem:
- Patch 711000: Patch for the US MessagePad 2000/2100
- Patch 73J186: Patch for the eMate 300
- Patch 74J185: Patch for the German MessagePad 2100
Patch Remover: Patch which removes all user applied patches on NewtonOS 2.1 devices

Other Software

Project80: Time Management for the Newton
MAD Newton: MP3 decoder based on MAD
Essen: MX2 recipe file reader
Various Experiments: Unsorted experimental code, reverse engineering results and other things, information on how NewtonOS patches work, an analysis of the Newton Year 2010 Problem and its solution

The actual downloads are hosted at SourceForge, which has also the bug and feature request tracker pages.

GTD and the Newton

The Newton was designed to be a personal digital assistant, and as such, it is very suitable for Getting Things Done:

Getting Things Done on the Newton

Software:

Flashpoint: A self contained Getting Things Done application
Project Stationery: Manage projects and actions via the built-in Notepad and To Do list applications
Nitch: A customized viewer of the Notepad application to manage projects and actions

Others

tox: An XML parser
Kino: An XML and HTML rendering library
SWIGLua: A SWIG wrapper module for Lua (outdated)
BagLock A tool for managing Scrum backlogs, sprints, developers and bugs.

People

Eckhart Köppen

Patch 711000

2010-07-16T18:35:14Z

This is the native system level patch version 711000 for the US MessagePad 2000/2100. The patch contains a fix for the Newton's 2010 problem, as well as the contents of the original 717260 patch. It also corrects an issue with Patch 71J059 where the date was reset to January 1st, 2008 after power loss, reboot or reset.

Version: 711000
Download via SourceForge

Compatibility

This patch is only compatible with US MP 2000/2100 models. The patch is not compatible with:

Patch 710031: This patch needs to be removed before the 711000 patch can be applied (see below). The functionality of patch 710031 might at a later point be merged into a new patch.
Fix2010: This fix changes some of the same time functions, and needs to be removed as well (see below). Fix2010 is not necessary anymore after patch 711000 has been installed.

The patch can be applied independent of the OS version or current patch (with the exception of a previously installed patch 710031), i.e. is is possible to install this patch over patch 71J059.

Files

The files in this patch are:

Patch.pkg - the actual patch.
ROMPatch.pkg, RExPatch.pkg - individual parts of the patch, not for installation (they can't be installed by themselves)

Installation

NOTE: THIS PATCH IS PROVIDED WITHOUT WARRANTY. DUE TO THE COMPLEX NATURE OF SYSTEM PATCHES, FAILURE TO INSTALL PROPERLY MAY RENDER THE NEWTON UNUSABLE, RECOVERY REQUIRES A TEMPORARY ROM BOARD SWAP, AND WILL RESULT IN THE LOSS OF ALL DATA ON THE NEWTON!

The patch has however been applied by many people without problems so far.

The patch is installed like any other Newton package, e.g. using NCU, NCX or any other installation tool. After installation, the Newton prompts for a reboot. After the reboot, the Newton OS patch level is updated to 711000.

The installation steps are:

For MP2000, freeze or uninstall all applications, and remove any memory cards to ensure that as much memory as possible is available
Create a backup of the Newton
If you have any year 2010 related fix such as the Fix2010 package, first use the diagostic tool to clear all alarms. Then, remove the Fix2010 package or any other related fixes from the Extras drawer
If you have patch 710031 installed (can be checked from "Extras/Memory Info") use the Patch Remover to remove this patch
Install the patch pkg file and reboot the Newton

The patch process does not modify or delete any data (such as a brain wipe), and the Newton is ready to be used after the patch was applied.

After the patch has been applied, it is permanently installed (it will stay in place even after a brain wipe), and can only be uninstalled with the Patch Remover.

Troubleshooting

IF THE NEWTON FAILS TO REBOOT AFTER PATCH INSTALLATION, PLEASE CONTACT support@40hz.org IMMEDIATELY! The actual patch process is very sensitive and can only be reverted by replacing the ROM board with a board from a German MessagePad 2100 or an eMate.

If the Newton shows strange behaviour related to alarms and other time related functions, please contact support@40hz.org, or revert to the original system version using the Patch Remover.

If the Newton enters an endless alarm loop, it is possible to clear all alarms using the Y2010 Diagnostic application. Alarms have to be re-entered manually afterwards.

Credits

Thanks to Jonathan Kipling Knight for the disassembly of patch 717260 which is the basis for all other patches.

Thanks to Paul Guyot for fixing the reset to 2008 problem.

Thanks to the following people for testing:

Tony Kan
Don Zahniser
Ronnie Simon
William Ponciengel
Sonny Hung
Rhonda
Greg Goodwin
Stefan Hassenstein
Grant Hutchinson
Christian Kwoll
William Ove
Jan Stoltenhoff
Hans Lefeber
Andy Hill
Woody Smith

Mottek/2010-02-10

2010-02-10T08:40:25Z

The 2008 Bug

The NewtonOS still has one problem related to the year 2010 problem: Very early in the boot sequence, the OS adjusts the real time clock to a "reasonable" value. Unfortunately, dates past 2009 are not considered reasonable, and the OS resets the date therefore to 1996.

The 2010 patch kicks in after that, and it can then only get the date to something slightly better, which is 2008. A proper fix would require to change the function which adjusts the clock, but it is not in the patchable area. It also occurs so early in the boot sequence that there is no easy way to intercept it, backup the proper clock value, and restore it later.

There are some workarounds possible, for example storing the correct time every minute when the Newton is turned on, but they require a good place for the time value. Flash memory is not ideal, a better place would be somewhere in RAM which survives resets and reboots. I'm now on the hunt for such a buffered location...

Patch Installation

2010-01-13T05:23:38Z

Installation

The patch has however been applied by many people without problems so far.

The installation steps are:

For MP2000, freeze or uninstall all applications, and remove any memory cards to ensure that as much memory as possible is available
Create a backup of the Newton
If you have any year 2010 related fix such as the Fix2010 package, first use the diagostic tool to clear all alarms. Then, remove the Fix2010 package or any other related fixes from the Extras drawer
If you have patch 710031 installed (can be checked from "Extras/Memory Info") use the Patch Remover to remove this patch
Install the patch pkg file and reboot the Newton

The patch process does not modify or delete any data (such as a brain wipe), and the Newton is ready to be used after the patch was applied.

After the patch has been applied, it is permanently installed (it will stay in place even after a brain wipe), and can only be uninstalled with the Patch Remover.

Troubleshooting

If the Newton shows strange behaviour related to alarms and other time related functions, please contact support@40hz.org, or revert to the original system version using the Patch Remover.

If the Newton enters an endless alarm loop, it is possible to clear all alarms using the Y2010 Diagnostic application. Alarms have to be re-entered manually afterwards.

Known Bugs

After a soft reset (via the reset button, or a reset utility), the Newton will lose the current date and reset the date to 1.1.2008.

Nitch

2009-12-05T18:39:49Z

Nitch is another implementation of GTD on the Newton.

Version: 3.1
Author: Eckhart Köppen
License: GPL 2.0
Download via SourceForge.

Concepts

Nitch is based on the concepts of projects and associated actions. Actions can be marked as next actions to be done. Nitch makes use of the built-in Notepad application, but offers a custom view to view all next actions.

Projects

Projects are maintained in Notes, using the Project Stationery (this stationery is different than the one used by the Project Stationery package to avoid confusion). A new project is created using the "New" button in Notes. Projects are simple checklists, and they can be stored in any folder in Notes.

Actions

Nitch considers a checked item in a project as the next action. It is possible to mark multiple items in a project checklist as next actions. Using hierarchical checklists is usually not practical though since the checked state of a parent checklist depends on the status of the child items.

A project which has a checked item (and thus a next action) is marked in the Notes overview with a small circle icon to easily spot projects without actions.

Goals

GTD uses no priorities for actions. Each next action is as important as the other, and the choice which action to start depends on multiple factors. GTD also uses the concept of a hard landscape, which includes actions due on a specific day.

Nitch provides a simple, optional way to facilitate the selection process for next actions. The method is based on roles and goals described in Stephen Covey's Seven Habits and First things first. Goals are collection of projects, grouped by role. Actions for projects which are set as a goal will have a priority above regular actions, and below the hard landscape actions.

Goals are managed in the same way as projects, via the Notepad. Any note which is in the designated goals folder (set in the preferences) will be shown in the goals view. Projects can be added and removed from goals via the button located in the top right corner of an expanded goal.

Nitch Application

While projects are viewed in Notes, the usual way to work on actions is via the Nitch application itself. It lists all actions (i.e. marked items) in all project stationery notes, and allows sorting by action name or project name.

Nitch has two main views, the actions and the goals views. They are selected via the folder tab in the top right hand corner of the application.

Actions View

The actions view shows all next actions as marked in the project notes in the Notes application. It also shows all items from the ToDo application which have priority 1.

Actions can be marked as done in the action list, after which they will be removed from the project note. A preference setting controls whether to open the project of a completed action, to quickly mark the next action. Tapping an action opens the Notepad with the corresponding project note.

Actions can have different highlights depending on their importance. If an action is a ToDo item for the current day, or if the action ends with a date, it has a solid border. If the action is for a project which is marked as a goal in the goals view, it will have a grey border. Other actions are not decorated.

The actions view has four buttons which have the following functionality:

New: Creates a new project note and switches to the Notes application where more details can be filled
Sort: Allows sorting of the actions by action title, project title, action age (oldest first), and randomly
Done: Marks the action as complete removes it from the corresponding note in Notes
Action button: If the corresponding transports are installed (such as IC/VC and Neo, or Mail V), actions and projects can be sent via the action button.

Goals View

Goals can be defined in the goals view. It shows a list of roles, each of which can be associated with a list of projects. Those projects represent the goals for that specific role.

Before entering goals, the roles list has to be filled first. Tapping the "New" button will prompt for a role name, and will add the role to the list. Expanding a role by tapping on it shows the goals (or projects) defined already for the role. If a goal project has a next action, it is indicated via a small icon left to the project name. Two buttons are used to manipulate the roles:

+/-: Select which projects are to be used as goals for the role
Delete: Remove the role

The "Reset" button is not used yet.

Preferences

The preferences view allows control over the folder where project notes are located. In case where many Notes are in Notepad, this can speed up operations, e.g. by storing all GTD notes in one folder "Projects".

The preferences view can also be used to enable or disable opening of a project note after completing an action.

Since Nitch patches the Notes application for some enhancements, a conflict may show up when using Standalone's SuperNotepad. It is visible as a garbled shortcut bar in Notes. To prevent this from happening, it is possible to let Nitch delay its patching of the Notes application by twenty seconds, to let SNP hook into the application first.

Finally, the view shows a history of the number of completed actions for the past 14 days.

Workflow

Goals and Roles

In the setup phase, roles are defined in the goals view. Those roles are populated weekly with projects. The usage of roles and goals is optional, if they are not used, actions will only have two priorities: Regular next actions, and actions for the current day (hard landscape).

Regular Flow

The typical workflow daily using Nitch follows the GTD flow:

Any upcoming issue which cannot be handled in a short time is a project, for which a new project note should be created.
The project review phase is used to check each project for the best possible next action. The review should happen at least once per week, if not more often.
A certain amount of pre-planning can be managed by adding more potential actions to a project note, but it is essential that each project has one easily doable next action.
Projects which are too complex (e.g. frequently result in next actions which are to broad), or projects which require more attention should be split into multiple projects
After marking an action as done in the Nitch action overview, it can be beneficial to immediately check the next possible action

Changes

Version 3.1: Changed goals functionality
Version 3.0: Added 'waiting for' and 'someday' functionality
Version 2.2: Fixed scrolling bug, added next action indicators to goals view
Version 2.0.2: Added goals view, minor bug fixes
Version 1.0.3: Minor fixes to history view
Version 1.0.2: Added sorting
Version 1.0.1: Minor bug fixes
Version 1.0: Initial release

Bugs and To Do List

Undo/Redo
Import/Export
Watching multiple folders
Archiving of tasks (either a separate list, or in "archive" notes)

Mottek/2009-10-07

2009-10-07T05:06:46Z

Enjoy your retirement, JE7420LHAYL

After twelve years of service, my first MP2100 is headed for retirement. It has been working very reliably over the years, but recently, one strange problem started to occur: It stopped playing sounds. I checked the usual suspects (wiring, software patches, ...), however the very first Newton on this planet to play MP3 files is now mute.

This device is one of the first German MP2100s, and I bought it back in 1997 from a Swiss web store. I used to baby the Newton way too much, before I realized that it can only realize its full potential if I have it close by all the time. The case looks pretty battered now, even though all clips and doors are still in place. The backlight it maybe at 50% brightness, and the screen is slightly worn. This particular Newton has seen quite a bit of places from California to Australia, and went up all the way to 70° 54' 48" North.

Now it is time to retire this lovely device, and start using its successor, probably one of the last produced MP2100 I bought already quite a while ago. I'm not sure if it will also see twelve years of service, but you never know

Mottek/2009-09-30

2009-09-30T05:43:36Z

The case of the never ending project

One observation from using Nitch now for almost two years is that GTD is not only about projects and actions, but a higher level concept on top of projects is still needed. I added roles and goals earlier to Nitch, and while that has been helpful to bring projects and actions into focus as needed, I still ended up too opften with projects that did not have a clear outcome.

The concept of a goal looks promising in this context, and I am adding more functionality to Nitch to have goals which in turn are made of projects. That allows to use goals for more longer term planning, and restrict projects to efforts which are not longer than a month.

Mottek/2009-08-14

2009-08-14T04:14:29Z

SourceForge improvements

SourceForge seems to be on a roll... even though things were a bit rocky due to their site redesign, I'm happy to see that the file release system now again allows direct links to packages for download, no more searching through dozens of packages! It also seems that it will soon be possible to use multiple Mercurial repositories per project, so that I can finally use a real version control system for the Newton packages.

Mottek/2009-07-26

2009-07-26T13:19:56Z

Year 2010 problem no more ...

After more testing by brave volunteers, I'm happy to announce that all NewtonOS 2.1 devices should be ready for year 2010 and beyond. In the patch collection, we now have:

Patch 71J059: Patch for the US MessagePad 2000/2100
Patch 73J186: Patch for the eMate 300
Patch 74J185: Patch for the German MessagePad 2100

And finally, a Patch Remover which removes all user applied patches on NewtonOS 2.1 devices (you should never need this, but I supplied it just in case).

All files are as usual on SourceForge, who have been busy with the download interface, but it's still not quite there yet, the patches are under the "Patches" section on the 40Hz download page.

Patch Testing

2009-07-26T13:10:53Z

Patch Testing

Prerequisites

The only way to recover a Newton which refuses to boot after installing the patch is with a German ROM board (an eMate ROM might work as well)

To verify the patch, three tools are needed:

The Y2010 Diagnostic tool
The Patch Remover
The actual patch

Test Procedure

Step A: Patch Remover Test

Open Extras and check the OS version in Memory info, it should indicate 717260 if the latest patch from Apple was applied
Install the Patch Remover.pkg
Reboot the Newton
Open Extras and check the OS version in Memory info, it should indicate 717260 or lower

If the Newton does not reboot, check under Recovery A below how to get it working again.

Step B: Patch Installation Test

Open Extras and check the OS version in Memory info, it should indicate 717260 or lower
Install the 71J059 patch
Reboot the Newton
Open Extras and check the OS version in Memory info, it should indicate 71J059
Open the Y2010 Diagnostic tool and check the first line in the output window, it should indicate a time base of 1/1/2008

If the Newton does not reboot, check under Recovery A below how to get it working again.

Step C: Rollback Test

This step only makes sense after step B

Open Extras and check the OS version in Memory info, it should indicate 71J059
Install the Patch Remover
Reboot the Newton
Open Extras and check the OS version in Memory info, it should indicate 717260 or lower
Open the Y2010 Diagnostic tool and check the first line in the output window, it should indicate a time base of 1/1/1993

Step D: Time Functions Test

Set time to Jan 4 2010 18.47 and set a meeting for 18.49 with an alarm. When 18.49 arrives, the alarm should go off
Edit meeting time to 18.50 with an alarm. Again the alarm should go off
Set time back to 18.47.
Set a recurring meeting daily to go at 18.48 and again the alarm should go off
Set date to Jan 6 2010 18.47. Alarm should go off at 18.48.
Set date to Jan 7 2010 18.47. Alarm should go off at 18.48.
Set date/time to Jan 5 2010, 18.00.
Created new person in Card and added a birthday for Jan 7 1989
Set date/time to Jan 6 2010, 08.58. Alarm should go off at 09.00 (note that in earlier testing, this was not the case, probably an issue with the test steps).

Recovery A:

If the Newton does not boot anymore, the patch has messed up the ROM. The fix alternatives are:

Open the Newton, take out the ROM board and replace it with an eMate or German MP2100 ROM board, reboot the Newton, wait until it indicates that it has erased all memory, swap the original ROM board back, and power up the Newton again
Send it to me so that I can perform the swap.

Patch 73J186

2009-07-26T13:09:02Z

This is the native system level patch version 73J186 for the eMate 300. The patch contains a fix for the Newton's 2010 problem.

Version: 73J186
Download via SourceForge

Compatibility

This patch is only compatible with eMate 300 models. The patch is not compatible with:

Fix2010: This fix changes some of the same time functions, and needs to be removed as well (see below). Fix2010 is not necessary anymore after patch 73J186 has been installed.

Files

The files in this patch are:

Patch 73J186.pkg - the actual patch.
Other .pkg files can be ignored.

Installation

The patch has however been applied by many people without problems so far.

The installation steps are:

For MP2000, freeze or uninstall all applications, and remove any memory cards to ensure that as much memory as possible is available
Create a backup of the Newton
If you have any year 2010 related fix such as the Fix2010 package, first use the diagostic tool to clear all alarms. Then, remove the Fix2010 package or any other related fixes from the Extras drawer
If you have patch 710031 installed (can be checked from "Extras/Memory Info") use the Patch Remover to remove this patch
Install the patch pkg file and reboot the Newton

The patch process does not modify or delete any data (such as a brain wipe), and the Newton is ready to be used after the patch was applied.

After the patch has been applied, it is permanently installed (it will stay in place even after a brain wipe), and can only be uninstalled with the Patch Remover.

Troubleshooting

If the Newton shows strange behaviour related to alarms and other time related functions, please contact support@40hz.org, or revert to the original system version using the Patch Remover.

If the Newton enters an endless alarm loop, it is possible to clear all alarms using the Y2010 Diagnostic application. Alarms have to be re-entered manually afterwards.

Known Bugs

After a soft reset (via the reset button, or a reset utility), the Newton will lose the current date and reset the date to 1.1.2008.

Credits

Thanks to Jonathan Kipling Knight for the disassembly of patch 717260 which is the basis for all other patches.

Thanks to Paul Guyot for fixing the reset to 2008 problem.

Thanks to the following people for testing:

Tony Kan
Don Zahniser
Ronnie Simon
William Ponciengel
Sonny Hung
Rhonda
Greg Goodwin
Stefan Hassenstein
Grant Hutchinson
Christian Kwoll
William Ove
Jan Stoltenhoff
Hans Lefeber
Andy Hill
Woody Smith