Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!pasteur!cory.Berkeley.EDU!c152-cb
From: c152-cb@cory.Berkeley.EDU (Vince Lee)
Newsgroups: comp.sys.amiga
Subject: Re: A1000 Hard Drive Controllers and Lucas
Message-ID: <14115@pasteur.Berkeley.EDU>
Date: 24 May 89 02:09:07 GMT
References: <SFT.89May22101247@ihlpa.ATT.COM>
Sender: news@pasteur.Berkeley.EDU
Reply-To: c152-cb@cory.Berkeley.EDU.UUCP (Vince Lee)
Distribution: comp
Organization: University of California, Berkeley
Lines: 27

In article <SFT.89May22101247@ihlpa.ATT.COM> sft@ihlpa.ATT.COM (Scott Thompson) writes:
>I am looking for any info on A1000 hard drive controllers that people
>are currently using with the Lucas board.  If you have a setup that
>works could you please e-mail me, let me know the controller you are
>using and any "tricks" you used to get it to work.  Thanks
>  Scott Thompson (IH 6W-207), AT&T Bell Labs, Naperville, Il. 60566

Surprisingly enough, I have a Stardrive/Starboard controller working with my
Lucas.  Surprising since the Starboard was one of the first units found to have
major problems with the Lucas board.  I got mine to work only after TONS of
hacks including:

1) Building the bus terminator.  I used 2.2k pullups instead of 4.7k.
2) Splitting the two gates of U9 into two separate chips, allowing more 
   combinations
3) Doing the DTACK latching fix posted by George Buce a few months back
4) Changing U8 to an LS? chip
5) Putting an F chip in half of U9 and an LS part in the other.

Note that this was a LOT of work.  A slower clock might help.  I've heard that
one of the faults of the Lucas board is that it doesn't keep the Address
Strobe up as long as the 68000, which causes problems with some memory boards.
(Alegra, for instance)  A friend had to go down to 12MHz to get his to work.

Hope this helps

-vince