HP3000-L Archives

June 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Woods <[log in to unmask]>
Reply To:
Jeff Woods <[log in to unmask]>
Date:
Thu, 4 Jun 1998 01:15:07 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
At 09:54 AM 6/3/98 -0700, blue nova wrote:
>I was informed today by HP that the 925,935, & 949 will not work in
>the year 2000 even with 5.5 and
>the latest power patch because of the following issues:
>
>1. The FMTDATE intrinsic will not work
>2. The floating point co-processor will not work
>
>Can this be true? How can a floating point co-processor possibly be
>aware of the date? Is this just a lot of FUD?

While this is certainly not an official statement, and it's been quite a
while back, I have personally seen an HP3000/925 with MPE 5.5 roll over
from 12-31-1999 to 01-01-2000 and seen tests run which indicated that all
at least appeared to be properly behaving.  I believe HP's refusal to claim
Y2K compliance for the 925, 935 & 949 hardware is due strictly to the
published schedule that those systems will no longer be supported in any
way by the end of 1999, rather than any fundamental known flaw regarding
Y2K.  Basically, I think they are simply saying that the systems are
untested for Y2K and therefore unsupported, though they may or may not work
after 2000 gets here.

ATOM RSS1 RSS2