Xref: utzoo comp.sys.amiga.misc:3723 comp.sys.amiga.introduction:538 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!decwrl!pa.dec.com!bacchus!mwm From: mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.introduction Subject: Re: random A3000 questions Message-ID: Date: 17 May 91 15:05:01 GMT References: <8974@ucdavis.ucdavis.edu> Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 43 In-Reply-To: jms@vanth.UUCP's message of 16 May 91 16:02:54 GMT In article jms@vanth.UUCP (Jim Shaffer) writes: >>And why are there two sets of ROM >>sockets on the motherboard? > >It takes bigger ROMS. I don't mean two sockets, I mean two sets of sockets. In the picture in the June '90 AmigaWorld, there are *four* ROM sockets. Two have EPROMs in them, two are empty and labeled "alternate ROM sockets." Preproduction machines had EPROM sockets for testing. Production machines have ROMs, and there aren't even sockets in the EPROM (at least, that's what mine had last night). The space for the EPROMs is waste. There are two 16 bit wide ROMS/EPROMS so you get 32 bit wide ROM on the machine. >>And a question I don't think I've ever seen >>anywhere: Is it possible to plug in a 1.3 ROM to save RAM? > >Eeek. You don't want to do this. You really want the 2.0 ROM. I probably should've explained myself better. I didn't mean getting rid of the 2.0 ROM. I meant plugging a 1.3 ROM into one of the empty sockets. After all, even when the final version of 2.0 is in ROM, if I want to load 1.3 it'll still take up my fast RAM. (I am NOT being fearful of 2.0, just cautious!) You might be able to get 1.3 on EPROM, but why bother? If you're going to run 1.3, you'll need a 1.3 System partition. Just put a kickstart image on that, and run it from there. This is assuming someone comes out with a hack to let you do that (CBM probably won't do it for you). However, I can't see why you'd want to. I gave up on 1.3 months ago - the bugs in it were far more annoying than the incompatabilities in 2.0. Of course, I only had one critical application that had anything worse than cosmetic problems, and that was fixed by a free upgrade.