Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!usc!rutgers!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A3000, Lattice
Message-ID: <13122@cbmvax.commodore.com>
Date: 10 Jul 90 02:33:19 GMT
References: <24893.2698602f@kuhub.cc.ukans.edu>
Reply-To: jesup@cbmvax (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 25

In article <24893.2698602f@kuhub.cc.ukans.edu> markv@kuhub.cc.ukans.edu writes:
>A couple questions and comments.  The first couple about the 3000 (having 
>just got one in at work and spent several hours getting it set up.)
>
>1.)  Where is the battery backed clock on the 3000?  SetClock doesn't work
>     under 1.3 or 2.0, and it seems silly to have to do a DATE ? on a new
>     several $1000 computer.

	Use the SetClock that comes with the system.  The new clock chip is
different, and old setclocks don't understand it.  Under 2.0, there are now
resources for supplying access to the clock in a hardware-independant manner.
Under 1.3 on a 3000, I think that the time gets set before the system boots,
so the "clock not found" message from 1.3 setclock actually doesn't matter.

>4.)  This ones about Lattice.  What's up with Lattice and Amiga products?

	See the message I posted last week.  Overall, this will probably be a
good thing once the inital confusion is over.  Every _registered_ owner will 
be getting info in the mail from SAS on exactly what's up (send in those
registration cards!)

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"