Cameron. Year 2097 and GPF. (2nd attempt) (OpenInsight Specific)
At 08 DEC 1997 06:23:42AM Oystein Reigem wrote:
Cameron,
Good news. A while ago I reported on a client of mine with a GPF problem: http://www.revelation.com/WebSite/discuss.nsf/09d90959a1a106db8525652c0042cb86/b5bad17ad953c615852565610033cbed?OpenDocument". He's now discovered his computer's system date was faulty - the year was 2097. When he fixed that the problem went away.
I see from this list he's not the only one that's had this problem. I.e, I don't know if the other developer reporting the problem on this list set the date on purpose, e.g, to check year 2000 compliance, and forgot to change it back. In my client's case I think the date must have been wrong from the manufacturer/distributor. My client's also discovered a friend of his got the system year set to 2097 on his computer. Is there a year 2097 virus around?
- Oystein -
At 08 DEC 1997 07:38AM Andrew Gebbett wrote:
I have no knowledge of a year 2097 virus. The reason we discovered the 2097 bug in OI was because one of our testers had an unrelated GPF. When he rebooted his system date had changed to 2097.
The time/date going out of synch seems to be a common occurence on our Win 95/NT 4 Workstations, but I know of no reason why.
Regards,
Andrew Gebbett
CSSP UK
At 08 DEC 1997 10:31AM John Duquette wrote:
Oystein,
This has been logged in the SPR system, here was my original posting:
John Revelation
At 08 DEC 1997 11:20AM Oystein Reigem wrote:
Andrew,
time/date going out of synch seems to be a common occurence on our Win 95/NT 4 Workstations…
So this is something that can happen again and again "by itself" and is not just the result of a faulty initial setting or a user blunder? Thanks for the warning.
…but I know of no reason why
Do you know if OI always GPFs when the year is 2097? Then it might be easier to narrow down the cause. But it probably doesn't. My client tried several times to reinstall Win95 and my app, and he managed to get OI to run locally the one time when he removed his network board first. When he put the board back in and reinstalled the network drivers OI failed again. I don't really know if the year was 2097 all the time, but I assume so.
…virus…
That was meant as a joke, really. (I 'ed, didn't I?) I've often had problems where I suspected a virus to be the cause, but I don't think I've ever I saw one. Exept for a macro virus once.
- Oystein -
At 08 DEC 1997 12:23PM glenn bryant wrote:
I've also had two occurences of this problem, a workstation all of a sudden showing dates in 2097, on a Win95 peer to peer network. Both were reset over a week ago and the problem has not reappeared.
At 08 DEC 1997 12:27PM Oystein Reigem wrote:
John R,
I saw your posting. I interpreted it as "(1) OI may GPF if the year for some reason has become (e.g) 2097, (2) we know about it and will look into it, and (3) there is no reason to suspect that OI itself changes the year".
- Oystein -