Date   : Sun, 05 Nov 2006 23:38:00 +0000
From   : astravan@... (Alex Taylor)
Subject: Master ET

Sprow wrote:
> In article <454E6460.3070904@...>, Alex Taylor
> <astravan@...> wrote:
>> Ian Wolstenholme wrote:
>>> I have the same real-time clock problem with one of my FileStore
>>> 
>> Which one is the clock chip?
> 
> 146818.

Thanks.

>> It changed after I posted my first message. I'd left the machine
>> running a program which displayed the time in random positions on
>> the screen; when I next checked it, the time was frozen and
>> garbled. Now if I do a *TIME or PRINT TIME$, it locks the machine
>> up
> 
> Press Escape. Does it say "Escape"?

No, it seems to be a total lockup.

> If so, press CTRL-C. The problem is that the TIME$ string contains a
> CTRL-B, which enables the printer and the rest of the string fills
> the (tiny) printer buffer. Escape flushes the buffer and CTRL-C
> disables the printer.

I know this from setting the clock on my spare Master 128 yesterday, but
at least it would print something until the buffer fills up. The Master
ET prints nothing at all after entering *TIME.

>> Trying to set TIME$ doesn't seem to help.
> 
> Check syntax, including punctuation,

I had been using the output of the *TIME command itself to give me a
hint of the syntax. But without anything on the screen to go by, I've
been doing it from memory, thus:

TIME$="Sun,05 Nov 2006.23:34:00"

I'm starting to think the clock chip might be dead.


Alex Taylor