Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!oakhill!dover!digital!digital.sps.mot.com!chen
From: chen@digital.sps.mot.com (Jinfu Chen)
Newsgroups: comp.sys.apollo
Subject: Re: problems with apollo's running mentor software
Message-ID: <4d46b3fd.12c9a@digital.sps.mot.com>
Date: 8 Oct 90 14:45:15 GMT
References: <1011@nikhefh.nikhef.nl> <649@tron.UUCP>
Sender: news@digital.sps.mot.com
Organization: Motorola, LICD, SPS, Mesa, AZ
Lines: 14

In article <649@tron.UUCP> kerr@tron.bwi.wec.com (Dave Kerr) writes:
>First, as you already no doubt know Mentor doesn't
>officially support 10.2. However I have seen this behavior
>on 10.1/7.0 mentor systems. I noticed it after using the
>date command to set the node's clock. I didn't persue the
>problem, and simply re-booted the node. The problem went
>away, ie I was now able to run the application. Did you change
>the time on the node before this happened? Does anybody know
>why using date should cause this problem? 

Mentor recommended NOT using /bin/date command to change system time, use
/sau?/calendar from the Mnemonic Debugger only. This was in some issue of
CSB (Customer Server Bulletin), the issue number escapes my mind. Call
Mentor's hotline for details.