Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.hardware Subject: Re: A3000 notes... Message-ID: <19491@cbmvax.commodore.com> Date: 4 Mar 91 22:44:32 GMT References: Reply-To: daveh@cbmvax.commodore.com (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 33 In article jtravis@dworkin.Amber.COM (Jim, Sysop) writes: > Secondly - SETCPU. Someone asked about it working on the 3000. It >doesn't, but but doesn't HAVE to. There's a new command in your C: directory >called CPU. Use it the same way you used to use SETCPU. SetCPU V1.6 works just dandy on the A3000, or rather, under 2.0. OS releases prior to 2.00 had no cache control mechanism in the OS, so SetCPU could just modify the cache settings itself. Since 2.0's Exec manages the cache, SetCPU had to be modified to use the 2.0 Exec calls to effect cache parameters. A3000s are all essentially running FASTROM at this time, which is a result of booting via SuperKickStart as they all do now. So SetCPU's FASTROM/KICKROM option isn't really necessary. In either case, there is the CPU program, which was originally based on SetCPU and does the same job, now as a standard part of 2.0. So you don't need to hunt up SetCPU V1.6 if just just want to muck around with cache parameters. > Thirdly - SETRAMSEY. Has ANYONE been able to get this programme to >work? I run it and it tells me that my 6 Meg (using 1Mx4 SCRAMS, 70ns) has >it's static mode turned off. One More Time.... Don't use SetRAMSEY -- throw it away. It doesn't understand the RAMSEY chip properly, and what it calls "STATIC" mode isn't. Both BURST and PAGE-DETECT modes in RAMSEY are SCRAM modes. You want BURST on, PAGE-DETECT off. The OS does this for you. > Jim Trascapoulos -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy "What works for me might work for you" -Jimmy Buffett