Duane writes:
>
>I was chatting yesterday with someone who received a letter from HP
>regarding their 925 system (they actually upgraded a number of years
>ago, but that's another issue...).
>
>In this letter HP advises them that the internal system clock will
>not work past 12/31/99. I did not see the letter so I'm assuming this
>is a correct summarization.
>
>This leads me to ask two questions:
>
>1) is this a 'guaranteed to not work' or is it a 'we haven't certified
>   it past 12/31/99, but it will probably work' issue.
>
   On our crash-and-burn 925:

   S925:/CCC/PUB->setclock date=01/01/2000;time=15:04;now
   S925:/CCC/PUB->showclock

   SYSTEM TIME: SAT, JAN  1, 2000,  3:04:12 PM
   CURRENT TIME CORRECTION:            0 SECONDS
   TIME ZONE:    6 HOURS  0 MINUTES WESTERN HEMISPHERE
   S925:/CCC/PUB->showme
   USER: #S10,MGR.CCC,PUB      (NOT IN BREAK)
   RELEASE: X.55.20   MPE/iX HP31900 C.05.07   USER VERSION: X.55.20
   CURRENT: SAT, JAN  1, 2000,  3:04 PM
   LOGON:   FRI, NOV 15, 1996, 11:11 AM
   CPU SECONDS: 31         CONNECT MINUTES: 1644713
   $STDIN LDEV: 4         $STDLIST LDEV: 4
   S925:/CCC/PUB->showvar hpcpuname
   HPCPUNAME = SERIES 925LX

   So that part seems to work.  I can also verify that ANSI labeled
   tapes with expiration dates past the year 2000 also AVR correctly
   on the 925 (on 5.0 and 5.5).

>2) what other systems (series 900 only) might have this issue.

   Can't help you there...

   cv

--
Craig Vespe [log in to unmask] Unison Software 811 Barton Springs, Austin Tx.78704
512-478-0611 http://www.unison.com NASDAQ UNSN disclaimer quote ANSI graphics