Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.tech Subject: Re: What is setcpu? Message-ID: <15830@cbmvax.commodore.com> Date: 13 Nov 90 17:19:21 GMT References: <11121@ccncsu.ColoState.EDU> <15818@cbmvax.commodore.com> Reply-To: daveh@cbmvax.commodore.com (Dave Haynie) Distribution: usa Organization: Commodore, West Chester, PA Lines: 25 In article yorkw@stable.ecn.purdue.edu (Willis F York) writes: >daveh@cbmvax.commodore.com (Dave Haynie) writes: >>In article <11121@ccncsu.ColoState.EDU> whicker@handel.cs.colostate.edu (gary alan whicker) writes: >>into the capability to read in new KickStart images from either file or >>KickStart disk. The current version, SetCPU V1.6 on Fish Disk 400 (including >>source), will handle both 256K and 512K KickStart images, it'll set up its MMU >Does this mean i could actually use a 1.1 ks disk and get 1.1 on my amiga? If you have a 68030 hooked into your A500. SetCPU achieves its ROM mapping by way of the MMU. ROM code can only live at the location is was linked for. >actually i have a friend with a 500 and a new 3000 (He sold his car/soul) >and he was complainig that he coulden't get the best use out of his 500 >because it was using 1.2 so Could ya put 2.0 on a 500 this way? [1] You can't legally do that; A3000 ROM code is licensed only for that A3000. [2] You can't physically do that without an MMU in the A500. [3] You can't logically do that with the A3000 ROM image, its 3000-specific. -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Standing on the shoulders of giants leaves me cold -REM