csreid%brock.cdn%ubc.csnet@RELAY.CS.NET (Michael Reid) (10/04/87)
I've been running SCO Xenix 386 sysVr2.2 for the last 2 months on a Compaq 386. It seems to be quite stable...it has never panicked and the error messages I have gotten are explainable. My main annoyance has been that something in Xenix is corrupting the clock. On reboot under DOS or Xenix the clock will be incorrect and this is detected by the machine. This does not happen when the machine is used exclusively for DOS. I believe that the Xenix date command may be doing this. The tech ref guide mentions that when the clock is read the clock valid bit is reset. Has anyone else seen this? Any suggestions? TNX > advance. <EOF-1
donc@cognos.uucp (Don Campbell) (10/09/87)
In article <9614@brl-adm.ARPA> , Micheal Reid asks... > I've been running SCO Xenix 386 sysVr2.2 for the last 2 months >on a Compaq 386. It seems to be quite stable...it has never panicked and the >error messages I have gotten are explainable. My main annoyance has >been that something in Xenix is corrupting the clock. On reboot under >DOS or Xenix the clock will be incorrect and this is detected by the machine. >This does not happen when the machine is used exclusively for DOS. >I believe that the Xenix date command may be doing this. The tech >ref guide mentions that when the clock is read the clock valid bit is reset. >Has anyone else seen this? Any suggestions? This has happened with some of our 386's as well (my machine included). I called SCO about it and they said it was a known bug. They also said it has been reproduced on more than just the Compaqs. Next time I talk with them I'll try to find out more. I'll post any information they give me. -- Don Campbell uucp: decvax!utzoo!dciem!nrcaer!cognos!donc Cognos Incorporated mail: P.O. Box 9707, 3755 Riverside Drive, (613) 738-1440 Ottawa Ontario, Canada. K1G 3Z4