Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!uupsi!sunic!news.funet.fi!cc.tut.fi!cc.tut.fi!mt87692 From: mt87692@cc.tut.fi (Mikko Tsokkinen) Newsgroups: comp.sys.amiga.applications Subject: Re: WorkBench 2.0 Message-ID: Date: 17 Apr 91 20:43:18 GMT References: <1991Apr15.165156.19988@sbcs.sunysb.edu> <3375@trlluna.trl.oz> <1991Apr17.095042.10823@lth.se> Sender: mt87692@cc.tut.fi (Mikko Tsokkinen) Organization: Tampere University of Technology Lines: 21 In-Reply-To: e89fn@efd.lth.se's message of 17 Apr 91 09:50:42 GMT >Zkick requires that you have RAM that autoconfigures at 100000h, so it >must get first bite at the cherry. This means that it must be the first >autoconfigure device along from the coprocessor slot, so if you had your >Hdisk there, swap them. There is some problem with the GVP drives in >this regard, as is explained in the docos. This is not quite true. I have SupraWS controller in the first slot, A2090a in the second and Supra 8Meg board in the third and zkick works fine with this setup. I don't understand why there should be any problems with the order, all ROM boards will be configured to diffirent place than RAM boards, unless of course the program is too stupid to search the correct board from expansion and assumes it's the first one... MIT NB: Make sure you have at least version 2.30 of zkick if you want working autoboot... -- Bubble Bobble