Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!cs.utexas.edu!utastro!sjk From: sjk@utastro.UUCP (Scot Kleinman) Newsgroups: comp.sys.amiga.tech Subject: Re: 32-bit LUCAS memory board Summary: autoconfig or not? Message-ID: <3414@utastro.UUCP> Date: 28 Nov 88 16:34:39 GMT References: <1988Nov23.104910.15213@gpu.utcs.toronto.edu> <1988Nov25.122705.23087@gpu.utcs.toronto.edu> Organization: U. Texas, Astronomy, Austin, TX Lines: 20 In article <1988Nov25.122705.23087@gpu.utcs.toronto.edu>, anakin@gpu.utcs.toronto.edu (Anakin Research) writes: > In article <9987@watdragon.waterloo.edu> kgschlueter@violet.waterloo.edu (Kevin Schlueter) writes: > >The design for the LUCAS 32 bit memory board sounds good. In my opinion, > >having the extra memory autoconfig is probably not desirable if it adds > >alot to the complexity of the hardware (an addmem like utility is fine > >and would allow us to easily disable the 32 bit wide RAM if necessary). The only problem with not making the memory autoconfig would be when using it (or wanting to use it) with disks that need to be booted where you can't change the startup-sequence to allow the running of an addmem type program. If you autoconfig it, this problem should never occur, and if you need to disable the memory, you can just boot-up with KS1.1, thus avoiding the autoconfiguration process. That is of cours, assuming you don't put the kickstart in ROM, something I would avoid because of this kickstart switching routine which I have found quite handy. Keep up the great work, though Brad! Scot sjk@astro.as.utexas.edu