Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!prls!pyramid!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga
Subject: Re: setcpu troubles
Message-ID: <10780@cbmvax.commodore.com>
Date: 11 Apr 90 07:56:30 GMT
References: <02650.AA02650@sosaria.imp.com>
Reply-To: daveh@cbmvax (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 27

In article <02650.AA02650@sosaria.imp.com> wizard@sosaria.imp.com (Chris Brand) writes:

>Well, since I installed an Imprimis Swift 170 megs harddisk in my system,
>setcpu fastrom won't work anymore. 

Which controller are you using?

The only thing I know that can be directly affected by FASTROM is, of
course, the speed of your code.  It's certainly possible that you've 
encountered some kind of software timing problem with your controller.
You've increased the speed of your hard disk drive, and the only thing
that's directly affected by that is the device driver software for your
controller.

Swifts and Wrens have worked just great around here with FASTROM, usually 
with a 2091 controller.

Just to be on the safe side, invoke SetCPU with the "NOPATCH" option, and
don't change the 1.3 boot-up cache settings, and don't use a CardROMFile.

>Chris Brand - wizard@sosaria.imp.com


-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
                    Too much of everything is just enough