Subject: | |
From: | |
Reply To: | |
Date: | Fri, 15 Nov 1996 17:20:22 CST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Gregory Stigers writes (in private)-
>
>Caveat: As I said in my previous reply to this subject, dinking with
>your system clock can play havoc with anything that expires, and some
>things only expire once, so re-resetting the clock won't fix those.
>
As I mentioned in my post, this is a crach and burn machine, so
we don't have any expiring software on it.
>OK. You can set the clock to 2000. Be sure to check that this works for
>your time zone and for GMT / UTC; showclks.pubxl.telesup helps here, and
>thanks to Carl Hughes for pointing this out to me.
>
S925:/CCC/PUB->showclks.pubxl.telesup
SHOWCLKS/XL A.10.00
DEBUG/iX C.05.07
HPDEBUG Intrinsic at: 419.00007258 PROGRAM+$198
PRIV=$3 := $0
*************************************************************
*** ***
*** Greenwich Mean Time : SAT, JAN 1, 2000, 9:03 PM ***
*** GMT/MPE offset : -6:00:00 ***
*** MPE System Time : SAT, JAN 1, 2000, 3:03 PM ***
*** ***
*************************************************************
**** C Library Information ****
Current value of Time Zone(TZ) variable : NOT ASSIGNED
CTIME function return : Sat Jan 1 16:03:29 2000
>1) What happens if you SETCLOCK to 23:5# 12/31/1999 UTC, and let it
>rollover?
>
>2) What happens if you SETCLOCK to 23: 5# 12/31/1999, and perform a
>shutdown and power off so the 3K is down when the clock rolls rollover?
>>From http://www.year2000.com/archive/NFbelieveme.html: 'Powering off the
>machine during the roll-over makes all the difference.', although
>another platform is the focus there.
>
These are both very good tests and I'll post results here after we
do them. Thanks, Gregory.
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
|
|
|