Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!funic!santra!nntp!robin From: robin@vipunen.hut.fi (Jarto 'Robin' Tarpio) Newsgroups: comp.sys.amiga.misc Subject: Re: Few questions/observations about the A3000 Message-ID: Date: 29 Apr 91 08:50:54 GMT References: <1991Apr23.143421.17738@javelin.sim.es.com> <1991Apr24.172714.462@daffy.cs.wisc.edu> <1991Apr24.214121.4631@javelin.sim.es.com> <1991Apr25.154002.4471@daffy.cs.wisc.edu> <1991Apr26.202103.22105@javelin.sim.es.com> Sender: news@santra.uucp (Cnews - USENET news system) Organization: Helsinki University of Technology, Finland Lines: 16 In-Reply-To: caw@miroc.Chi.IL.US's message of 27 Apr 91 13:38:43 GMT In article caw@miroc.Chi.IL.US (Christopher A. Wichura) writes: > I'm pretty much sure that C= will > release 2.0 in ROM only for A3000 users. Why? Because the CPU command > found in 2.0's C: has a FastROM option, just like SetCPU. If you've got an > A3000 and want to run 2.0 from RAM you slap a CPU FastROM in your startup > sequence. Otherwise you run from ROM. So ? I have tried to figure out why the CPU-command would force the OS to be relesead on ROM only for A3000. That doesn't make sense. CPU FastROM only copies the ROM to RAM for some speedup. -=> CAW /robin