Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali!milton!uw-beaver!ssc-vax!uvicctr.UVic.CA!climber
From: climber@uvicctr.UVic.CA.UUCP (climber)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Help! 68030 hates HardFrame
Message-ID: <1012@uvicctr.UVic.CA.UUCP>
Date: 9 Apr 90 19:22:07 GMT
References: <1990Mar31.051128.15367@IRO.UMontreal.CA> <10528@cbmvax.commodore.com>
Reply-To: climber@uvicctr.UVic.CA.UUCP ()
Organization: University of Victoria, Victoria B.C. Canada
Lines: 25

In article <10528@cbmvax.commodore.com> daveh@cbmvax (Dave Haynie) writes:
>In article <1990Mar31.051128.15367@IRO.UMontreal.CA> martin@iros52.UUCP (Daniel Martin) writes:
>
>>   Until now I have been happily using my amiga 2000 system.  It contains a
>>microbotics 8up (with 2 meg), a microbotics hardframe with a mounted Quantum
>>40Meg drive, and a MicroWay flicker fixer.

>If you've had your Hardframe for awhile, it's most likely the problem.  The early
>Hardframes had a bus arbitration problem; technically put, they negated BGACK*
>before the end of a cycle.  While the 68000 system wasn't fast enough to react
>to this problem, any 68030 system with DMA-able memory will definitely have a 
>problem.  Microbotics fixed this around a year ago.

{ Much stuff deleted }

I tried the 2630 and really liked it (its a cool board, Dave :-) )
However, I also own a hardframe which is one of the older ones that,
while the system worked, I had to remove a memory card since the hardframe
did not like it.  So, the question is: can I affect a fix so that my 
older hardframe (which is nice and fast and I like it) works?  It is
true that the 1 meg agnus chip does NOT like the hardframe (from friends
with exactly the same setup) and I can't move up to the new chipset
until I deal with this problem.  Any suggestions?

Craig  climber@sol.UVic.ca