Xref: utzoo comp.sys.amiga.tech:15057 comp.sys.amiga.hardware:4018
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!decwrl!ogicse!unmvax!uokmax!slfields
From: slfields@uokmax.ecn.uoknor.edu (Scott L Fields)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga.hardware
Subject: Re: Possible E-Clock fixes
Message-ID: <1990Oct12.151207.10121@uokmax.ecn.uoknor.edu>
Date: 12 Oct 90 15:12:07 GMT
References: <1990Oct11.193142.13719@ecst.csuchico.edu>
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK
Lines: 23

In article <1990Oct11.193142.13719@ecst.csuchico.edu> mrush@csuchico.edu writes:
>
>	I was (as many people do) looking over the infamous 14Mhz hack for
>the Amiga and was wondering about the possibility of the following solution
>to the E-Clock problem.
>
>	Since the mod requires the acquisition of a 14Mhz CPU, you're obviously
>going to have an extra 7Mhz CPU sitting around.
>	Would it be possible to take that 7Mhz part, hook up the supply voltages,
>7Mhz input clock (and maybe a couple other things), and then run the E-Clock
>from that CPU into the Amiga's E-Clock input (leaving everything else
>unconnected).  Then you would just let the E-Clock from the 14Mhz CPU remain
>unconected.  Thus you should have a GENUINE 7Mhz based E-Clock signal ALL the
>time.
>
>	Will this work?
>
>	-- Matt
This is akin to the idea of just dividing the 14mhz clock by two to get the
normal E-clock. The problem is that the E-clock needs to be in sync with the 
68000 bus cycles. It gets a little complicated but a couple of extra chips
can substitute the E-clock. That extra 68000 will just have to sit on the shelf
by itself.