Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!bpa!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: OVR pin on GARY etc (PLEASE READ! SOMEONE AT C= FOR EXAMPLE)
Message-ID: <12301@cbmvax.commodore.com>
Date: 5 Jun 90 17:42:29 GMT
References: <1990Jun2.075504.13303@nada.kth.se>
Reply-To: daveh@cbmvax (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 30

In article <1990Jun2.075504.13303@nada.kth.se> nv89-rbi@nada.kth.se (Ron Birk) writes:

>1) I would like all information about the OVR (Override) pin on the GARY,
>   which are connected too pin 17 on the expansion bus.

If you assert OVR* in 60ns or less after receiving AS*, your expansion card
may directly drive the DTACK* signal.  OVR* and DTACK* are driven with open-
collector or open-drain devices.  That's all you need to know to use
OVR*.

>3) The memory clock bits! We know how to set the time and date but not all
>   bits. I mean the expansion clock at $DC0000.

The best thing to do is Execute the SetClock program if you want to actually
read or write the clock.  The A3000 uses a different clock chips than the 
A500/A2000, and there's no reason to assume a future Amiga might not use a
still different clock chip.  The 2.0 operating system will have a clock
resource for this, but currently, SetClock is you best bet.

>Please help us. My friend doesn't have access to this net so send me the mail.

It sound like you need the A500/A2000 Technical Reference Manual, which can
be ordered from Commodore Technical Support.

>Ron Birk and Per Hakan Sundell.

-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"I have been given the freedom to do as I see fit" -REM