That would imply a dead man's switch for that kind of launch.

Did not enter the cancel code in the allotted time window? (Error:  Jan 
1, 1900 not within parameters) .... launch.

And if the systems are that old, that means U.S. forces in Hue, Danang, 
& Cam Ranh Bay will be relatively safe.  Even accounting for a few 
inches of continental drift.  If still using inertial guidance systems, 
targeting errors caused by drift of magnetic North since inception will 
be even greater.

On 7/31/2019 1:45 PM, Neil Armstrong wrote:
> Yep it will keep working no problem but the Beechglen patch will work to 2037-12-31.  I've made similar adjustments to our software at Robelle, as well as tested the Beechglen patch.
>
> I think it's fun as well, but it is important to remember context of what is in play here, of course some other hardware/OS have issues coming up in the 2030s. (
>
> Of course this makes you wonder what happens to various systems around the world that may involve launch codes. (
>
> Neil
>
> On 2019-07-31, 1:36 PM, "HP-3000 Systems Discussion on behalf of Johnson, Tracy" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>
>      If you ignore MPEX (sorry about that, I thought it was funny), just
>      based on the HOURGLAS simulation, it demonstrates the HP3000 will not
>      die, but roll over to 1900.
>      
>      Back to my previous suggestion of ignoring years, I you care about the
>      day of the week (MON, TUE, WED, THU, FRI, etc.) choose the year 2000 or
>      1972 as your fictional year.
>      
>      On 7/31/2019 1:23 PM, Neil Armstrong wrote:
>      > Hourglass IIRC will simulate what the HP 3000 will do, the other is just a straight up Date calculation and not related at all, so I am not sure what this demonstrates.
>      >
>      > Neil
>      >
>      > On 2019-07-31, 12:57 PM, "HP-3000 Systems Discussion on behalf of Johnson, Tracy" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>      >
>      >      I experimented with HOURGLAS and pushing the date forward and used the
>      >      following scheme in HOURGLAS' HGCONFIG file:
>      >
>      >      DELTA * 8 YEARS 153 DAYS
>      >
>      >      Gets me MON, JAN 1, 1900, 12:54 PM
>      >
>      >      Although in MPEX if I do a
>      >
>      >      CALC TODAY + (365*8 + 156)
>      >
>      >      I get
>      >
>      >      28/01/01
>      >
>      >
>      >      On 7/31/2019 11:42 AM, Donna Hofmeister wrote:
>      >      > On Wed, Jul 31, 2019 at 8:44 AM Johnson, Tracy <[log in to unmask]> wrote:
>      >      >
>      >      >> Only if you care about the date!  (Just set the clock back to some
>      >      >> fictional date.)
>      >      >>
>      >      >> Or you can get a 10-year patch from Beechglen.
>      >      >>
>      >      >> Or you can try the emulator from Stromasys, (I am not sure if they
>      >      >> incorporated a patch, but if they want to keep selling, they should).
>      >      >>
>      >      > <plug>
>      >      > Just like during Y2K times, you're encouraged to get a copy of Hourglass (
>      >      > https://www.allegro.com/?page_id=388) to aid in your 2027 testing!
>      >      > </plug>
>      >      >
>      >      >          - donna
>      >      >
>      >
>      >      * To join/leave the list, search archives, change list settings, *
>      >      * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>      >
>      >
>      >
>      
>      * To join/leave the list, search archives, change list settings, *
>      * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>      
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *