Subj : Annoying date problem.
To   : LEONARD ERICKSON
From : Ian Moote
Date : Fri Nov 10 2000 02:37 am

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

ROFL!


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!

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

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

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

The problem appeared in January of 2000. I've applied all the latest 
Netware service packs, the special Y2K fixes, and even the one OS/2 Y2K 
fix even though it didn't seem to apply to my problem, but the problem 
just won't go away. I even double-checked the Network and Scsi drivers 
out of desperation. I'm running IntraNetware v4.11 for OS/2. The only 
thing that I haven't done is to apply fixpacks to OS/2. Time constraints 
have kept me from going in and doing that.

(Actually, FixPack 5 may be installed.)

Anyway, take care and TTYL.

---
 þþ Proverbs 3:5: ...and lean not unto thine own understanding.                        

--- AdeptXBBS v1.11y (FREEWare/2)
 * Origin: Moote Pointe (1:244/140)

.