Subj : Annoying date problem.
To   : Ian Moote
From : Leonard Erickson
Date : Fri Nov 10 2000 03:56 pm

 -=> Quoting Ian Moote to LEONARD ERICKSON <=-

 LE> So the eval expired 20 years ago... :-(

 IM> ROFL!

<sigh>

I can see the humor, even if I'm not exactly laughing about it.
 
 LE> BTW, that bit with the date is *annoying*. I've upgraded the BIOS of
 LE> the PC, it doesn't have a Y2K problem. And if I shut down the
 LE> server, the date is fine.
 LE>
 LE> But if it crashes, the date is set to Jan 1, 1980 when I reboot. And
 LE> the time isn't changed at all!

 IM> Reeeeaaally! One of my clients has an annoying date problem as well! 
 IM> Whenever he _boots_ the server, the date is reset back to 1 January 
 IM> 1980! No crash, just anything for which we have to reboot the server!

 IM> The problem happens somewhere in this area:
 IM> 
 IM> Initializing Transaction Tracking System
 IM> Time zone set to: EST5EDT
 IM> Daylight Savings Time Offset is set to: (APRIL SUNDAY FIRST 2:00:00
 IM> AM) End Of Daylight Savings Time is set to: (OCTOBER SUNDAY LAST
 IM> 2:00:00 AM) Default Time Server Type is set to: SINGLE
 IM> Bindery Context is set to: O = [omitted by ian]
 IM> File server name SERVER0
 IM> IPX internal network number 12CF8450

 IM> (I've omitted the bindery context as it reflects the name of my
 IM> client.) 

Well, on this, it's happening during the crash, because going into CMOS
setup on power up shows the 1-1-80 date. Once I correct it there
everything is fine. 

I've got to get around to adding a couple of lines to AUTOEXEC.BAT to
bypass starting Netware if the date is wrong. 


--- FMailX 1.59b/beta
 * Origin: Shadowshack (1:105/51)

.