Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ulowell!cbmvax!daveh From: daveh@cbmvax.UUCP (Dave Haynie) Newsgroups: comp.sys.amiga.tech Subject: Re: 32-bit LUCAS memory board Message-ID: <5349@cbmvax.UUCP> Date: 29 Nov 88 22:26:16 GMT References: <3414@utastro.UUCP> Organization: Commodore Technology, West Chester, PA Lines: 29 in article <3414@utastro.UUCP>, sjk@utastro.UUCP (Scot Kleinman) says: > Summary: autoconfig or not? > > 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. The ONLY kind of programs that create this kind of situation are poorly programmed video games. In such cases, there's probably not a real good chance that the program being loaded will work with any of FAST memory, 32 bit memory, or 68020 CPU. So you're probably better off not doing the configuration. Plus the fact that it may be impossible to do a legal autoconfiguration with this memory, since such autoconfiguration requires that all autolinked memory be DMAable as well. > ...and if you need to disable the memory, you can just boot-up with KS1.1, > thus avoiding the autoconfiguration process. There are many programs that won't operate under OS 1.1. 1.1 is not a supported operating system, and if you ever feel you need to use it, think again. Either you're not being properly supported by your software vendor, you're confused, or you're too cheap to pay for an upgrade. > Scot > sjk@astro.as.utexas.edu -- Dave Haynie "The 32 Bit Guy" Commodore-Amiga "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: D-DAVE H BIX: hazy Amiga -- It's not just a job, it's an obsession