Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!manuel!ccadfa!prolix!dac
From: dac@prolix.pub.uu.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Clock and Lattice Compiler
Message-ID: <18d78eb0.ARN13b6@prolix.pub.uu.oz.au>
Date: 17 Mar 91 10:12:32 GMT
References: <27e31113.6632@petunia.CalPoly.EDU>
Reply-To: dac@prolix.pub.uu.oz.au
Followup-To: comp.sys.amiga.hardware
Organization: More like Mis~, really.
Lines: 22

In article <27e31113.6632@petunia.CalPoly.EDU>, Twinkie the Sponge Cake writes:

> 
> I just had something rather strange happen to me (at least I thought it was
> strange). I was compiling away with Lattice 5.04 and suddenly got a guru.
> After rebooting my setclock command was giving me an "<invalid> <invalid>
> <invalid>", trying the date command I received the same results. I tried 
> using the "setclock reset" to no avail (I've got a Rev 4.3 B2000 by the way).

I had this happen to me as well, a few months ago (different circumstances,
but same end result '<invalid> <invalid> <invalid>'.

I couldn't get setclock, or anything to make it work, so I eventually used
PREFERENCES to set the time, and that worked great.

So, if anyone else has a problem with their clock having <invalid> data,
try Preferences. It worked for me.

Dac
--
David Andrew Clayton. // _l _  _ dac@prolix.pub.uu.oz.au    *or*|I post.I am.
Canberra, Australia.\X/ (_](_l(_ ccadfa.cc.adfa.oz.au!prolix!dac@munnari.oz